↑
← All articles

Technology decisions

Plan how your data leaves before choosing a platform.

Test the practical exit route for business data before committing to a new platform or supplier.

A hypothetical service business is comparing two new platforms. Both can import its customer records and demonstrate the everyday workflow. Neither presentation shows what the business would receive if it needed to move away three years later. An exit plan is not a prediction that the relationship will fail. It is a practical test of ownership, continuity and future choice. Ask how useful data leaves before deciding how easily it enters.

Define what must come back

Start with the information needed to serve customers, meet obligations and continue operations. Include attachments, notes, status history, relationships between records and the configuration that gives the data meaning. A spreadsheet of names and email addresses may technically be an export while leaving most of the working record behind.

Separate data the business owns from supplier-generated logs, derived fields and proprietary configuration. Record any uncertainty as a decision point rather than assuming the contract or demonstration has resolved it.

Ask for the exit to be demonstrated

Use a small synthetic dataset that includes ordinary records, attachments, linked items, custom fields and a closed case. Ask each shortlisted supplier to export it, then inspect whether another competent team could understand and reuse the result.

Check format, field definitions, relationships and character encoding. Ask how long an export takes, who can request it, whether self-service access changes after notice is given and what help or charges apply.

  • Which records, files and history are included?
  • Which relationships are preserved?
  • What knowledge is needed to interpret the export?
  • How long is access retained after the agreement ends?

Connect the contract to the operating plan

Contract wording matters, but the business also needs a workable route. Name who would authorise an export, where it could be stored securely and which team could validate it. Set a time expectation that reflects the service's tolerance for interruption.

Identify dependencies that an export alone will not solve, such as integrations, automated messages, identity access and retained documents. These items belong in the transition plan even when a new supplier will eventually replace them.

Keep the route current

Review the exit assumptions when the platform gains a major data type, integration or business-critical process. A route tested at purchase can become incomplete as the organisation's use expands.

This does not mean building a full migration every year. Maintain an accurate inventory, preserve key definitions and occasionally test a representative export. The result is better evidence for the buying decision and less uncertainty if circumstances change.

Rethink's technology second opinions can provide an independent check on product claims, delivery assumptions and the practical choices surrounding a platform decision.

Explore a technology second opinion →

Work with Rethink

Discuss your
project.

Talk to Rethink