What you need to know
Make the assumptions explicit, ask for evidence and test the handover. A buying decision is easier to defend when the trade-offs are written down.
Data and files
Request a bulk export with relationships, attachments and history. Open it in another system. A successful download is not a successful migration.[1]
Logic and runtime
Ask which parts of the application remain readable and which can actually run elsewhere. Require a demonstration with your workflow, not a generic assurance.[1]
Dependencies and skills
List connectors, libraries and specialist knowledge. Record what a new team would need to operate and change the application.[1]
Contract and transition
Agree notice periods, assistance, export formats and data deletion before signing. Put the timing and cost of transition in writing.[1]
Your vendor checklist
- Record the metering unit and the maximum commitment.
- Test access, review and recovery with your own use case.
- Open the export in another environment.
- Get the transition obligations in writing.
- Agree a date to review the evidence again.
More field guides
Sources & assumptions
- App Build Index sample research model, 14 October 2026. Prices and scores illustrate the interface and are not verified vendor offers.
- European Commission · AI Act framework. Reviewed 14 October 2026. Apply the rules to your exact use case with qualified advice.