The cost of leaving your technology provider

Consider a supplier renewal where the proposed price increase is uncomfortable. Management would like to compare alternatives, but the current service connects to several systems and only a few people understand how it works.

The contract may provide a route to exit. Establishing whether the business could use it requires a closer look at its technical, operational and commercial dependencies.

Map what would have to move

Start with the business service the provider supports. Identify the data, configurations, integrations and working arrangements that would need to be transferred or replaced.

Being able to export data is useful, but the export must also be usable. Check the format, completeness and associated information needed to interpret it. Workflows, access permissions and historical records may need attention alongside the headline data set.

Ask the technical and operational teams to explain the main obstacles in plain language. Where important details are unknown, include the work needed to establish them in the assessment.

Find the knowledge the business depends on

Documentation can exist without providing enough information for another team to operate the service.

Understand which tasks depend on the incumbent supplier or particular individuals. Examine the availability of current configuration records, administrative access, operating procedures and people with the skills to use them.

A planned transfer of knowledge may be needed even when the technology itself is portable. Discuss the required support and contractual position with procurement, legal and other relevant specialists before relying on the supplier to provide it.

Estimate the whole transition

A replacement price is only part of the comparison. Allow for migration, integration, testing, training, temporary parallel running and the effort required from internal teams.

Explain how service would continue during the move and what evidence would be needed before switching. Include the consequences of delay and a realistic allowance for work that cannot yet be estimated precisely.

Some dependency may be worth accepting because the provider delivers valuable capability or reduces operating effort. Compare that benefit with the constraints and likely switching costs. Requiring complete independence can also add complexity and expense.

Keep the option credible over time

A review at renewal may arrive too late to create a meaningful alternative. Keep important dependencies and notice periods visible while there is time to act.

For a critical service, ask management to maintain a proportionate transition plan and test important assumptions, such as whether an export can be used elsewhere. Revisit the assessment when integrations, volumes or supplier arrangements change.

The board does not need to choose a replacement in order to understand its options. It needs a credible account of what leaving would involve, what staying would commit the business to and which uncertainties should be resolved before the next investment.

Further reading: UK Government guidance on managing technical lock-in in the cloud and the Digital, Data and Technology Playbook.