Portability and continuity
Separate the exit paths that exist in the product from the protections your team should put in the contract.
Shipped boundary
These are current product surfaces a technical team can inspect during evaluation.
Each published record version can be exported as CSV or JSON, with its structure defined by the same model that validates the data.
The platform exposes conventional interfaces a replacement can read or reproduce, instead of requiring a private client protocol.
Authentication, enterprise sign-on and directory synchronization use established identity standards.
Diligence boundary
A serious exit plan also needs commitments that cannot be delivered by a product screen. Agree these before the dependency becomes important.
Define the complete export scope, formats, delivery timing, retention period and verified deletion process.
Agree how long the service stays available after notice, what handover help is included and how additional work is priced.
If continuity escrow matters, define the independent agent, release triggers, deposited material and verification schedule in the deal.
Put renewal treatment and any price protection in the commercial terms rather than relying on a sales conversation.
Honest boundary
Do the work while you still have leverage: inventory, test, then contract.
List business records, files, identity links, workflow definitions, integration configuration and audit evidence.
Use a real record version to verify file shape, identifiers, relationships and the work a replacement would need.
Turn the remaining full-return, transition and continuity requirements into reviewed agreement language before purchase.
We will separate what you can test in the product from what belongs in the agreement.