Sales material covers features and support plans. Checking what leaving would involve is up to you.
Before signing or renewing, ask for an export of a real campaign page with its images and linked content. Have your technical team show what it would take to publish that page elsewhere. Then check whether the agreement gives you the access and time that move needs.
For a marketing team, the risk is staying on a platform that no longer fits because leaving would stall campaigns. The checks below are for your vendor and for the team building your site.
What is CMS vendor lock-in?
CMS vendor lock-in is the cost and difficulty of moving content, templates, workflows and integrations from one platform to another. Some migration work is unavoidable. The avoidable part is tying those things to a particular system without a documented way to replace it.
A page can look complete in an export while depending on an image URL you will lose when the account closes. A content field can contain a layout instruction that only the old template understands. Finding those dependencies before a renewal gives you a basis for deciding whether to stay, renegotiate or move.
How does CMS lock-in happen?
Content storage is one source. If the text is mixed with layout markup or plugin-specific instructions, a new system needs a way to interpret or convert it. Test whether an exported article contains usable headings and paragraphs, and whether its links still identify the right pages.
Templates create another dependency. A template that calls the CMS directly for navigation, related articles and language variants needs changes when those calls change. Keep a list of those functions so that a migration quote covers more than the visible design.
Workflows need their own review. Approval roles, scheduled publishing and translation handoffs are requirements to recreate in the destination. Your team’s editorial judgement remains useful; the platform-specific steps need documentation and training. Ask editors to demonstrate a normal publishing task and a difficult exception before estimating that work.
Does open-source remove the dependency?
Open-source does not answer the export question. WordPress, for example, is released under GPLv2 or later, and its documented export produces a WXR XML file containing posts, pages, custom fields and other content data.
For any CMS, inspect how the destination will use that data. If a field contains a shortcode or a reference to a plugin feature, identify what will render it after the move. Access to code and access to an export are useful inputs; the test is whether your actual content works without the old runtime.
What should you ask about the CMS contract?
Before signing or renewing, put these questions to the vendor and ask them to point to the corresponding terms in the agreement. For an existing contract, record the clause beside each answer and raise the unanswered questions before agreeing to another term.
| Topic | Questions to put to the vendor |
|---|---|
| Content export | Which content and metadata can we export, in which formats, and with what documentation? Are drafts, revisions, relationships and language variants included? |
| Access after the term | When does editor and API access end? How long can we retrieve data after termination, and when is it deleted? Can we complete an export during that window, and what assistance or fees apply? |
| Renewal pricing | Can the price increase during the term or at renewal, by how much, and with what notice? Does that notice arrive before the deadline for declining renewal? |
| Media and uploaded files | Who owns the uploaded images, documents and other media? What rights do we retain to use them elsewhere? Can we download the originals and their metadata, and what happens to hosted file URLs when access ends? |
| Sale or shutdown | If the company is sold or the service closes, what happens to our agreement, data and account access? What notice, export access and assistance are specified for those events? |
| Term and auto-renewal | How long is the initial term? Does it renew automatically, for how long, and what notice must we give to stop renewal? Which dates and cancellation method apply to our account? |
Ask for any agreed change to be reflected in the documents you will sign. Give the renewal and access dates to whoever is scoping the migration, so the proposed schedule can be checked against them. An export trial and a written answer serve different purposes: the trial shows what transfers, and the answer records what access you have agreed.
When a client’s vendor is acquired, we talk through what might happen, including price increases, and discuss alternatives. We usually build so that switching stays fairly easy. For renewal questions after a specific acquisition, see the Salesforce acquisition of Contentful.
What architectural steps reduce CMS lock-in?
Make portability part of the build requirements. Ask the technical team to demonstrate the following with your content before accepting the work. Headless architecture separates content management from the site displaying it, as the HTTP Archive Web Almanac describes, but that separation still needs to be carried through the implementation.
-
Separate content from presentation. Store a product’s name, description and image reference in identifiable fields. Keep layout choices separate where possible. Ask for the content model in a document you control, including field types, required fields and relationships. This gives the next team a description of what each value means. The structured content guide develops that distinction.
-
Control the frontend and routing. Keep the website code, build instructions and URL rules accessible to your company. Ask the team to show where the CMS supplies data and where the website decides what to display. Trial replacing that data source for a page. Record the changes required for previews, images and language routes rather than assuming the whole frontend will stay unchanged.
-
Export the actual content and media. Require a repeatable, documented export that someone else can run. Check the original uploaded files as well as their references, captions and alt text. Store the output somewhere your company controls. Open a sample with access to the old media host disabled to reveal any remaining dependency on its URLs.
-
Keep business rules outside vendor templates. Put rules such as choosing a market’s product range or sending a form to the right team in code you can retain and change. Document where each rule runs. Ask what would need rewriting if the template system disappeared; a content export cannot substitute for executable code.
-
Control the connections to other tools. Ask for a documented interface between the CMS and your forms, search or customer database. Keep vendor-specific calls in a replaceable part of the integration code. Record who owns the accounts, how credentials are replaced and how a failed transfer is retried. Test a sample through the destination before calling the connection portable.
You still need to map content into the new model and test the result. These steps make the dependencies visible and give your team places to change them without rewriting every page. They do not make a CMS switch free or guarantee a fixed migration duration.

How do you compare headless CMS portability?
Use the same sample content and the same exit test for every shortlisted platform. Choose material that includes the difficult parts of your site: for example, a translated campaign page with linked products, an image and a downloadable document. Have an editor identify the content that must survive before a developer runs the export.
Record the evidence against these criteria:
| Criterion | What to demonstrate outside the original CMS |
|---|---|
| Content model | Field names, types and validation rules are documented well enough to recreate the model. |
| Relationships and languages | Links between entries and their translations resolve after import, with a record of any changed identifiers. |
| Rich text and layouts | Headings, links and embedded content render correctly; any conversion of layout instructions is identified. |
| Media | Original files open independently of the old host, and their captions, alt text and content references remain associated. |
| Frontend and integrations | The sample page renders from the new source and its form or other connected function works. |
| Editorial operation | An editor can preview, approve and publish the sample; anything requiring new configuration is listed. |
Mark each result as transferred, needs conversion or needs rebuilding. Keep the sample export and the steps used to import it with the comparison. A JSON or CSV label tells you the file format; it does not tell you whether the relationships have retained their meaning.
Include the required subscription plan and access permissions in the record, then compare them with the contract answers. A successful trial under a different plan does not establish what your own account can do. For the wider decision about editor experience and fit, use the 5-step plan for choosing a CMS.
What does CMS lock-in cost?
Start with the work your team can count. Add up the time spent re-entering content, fixing formatting or maintaining CMS workarounds. Multiply weekly hours by working weeks and the loaded hourly rate, which includes the employment costs you want to account for.
At ten hours a week, 52 weeks and € 50 an hour, the calculation is 10 × 52 × € 50 = € 26.000 a year. Use your own working weeks and rate. This measures time consumed; it is not automatically cash you would save by migrating.
Keep other costs separate. Record campaigns delayed by a platform constraint, the current renewal quote and the work needed to move. Avoid counting the same staff time once as a workaround and again as a campaign delay. The post on signs your CMS is holding your marketing team back helps identify the operational problems to investigate.
Adding content types and integrations can increase the work of a future migration. Waiting alone does not establish how much it will cost. A trial export gives you a more useful basis than assuming that every extra year makes leaving prohibitively expensive.
How do you get out, and what sets the timeline?
Begin with an inventory of content types, languages, media and connected systems. Compare it with the export, then list the data that needs conversion and the functions that need rebuilding. Include editorial approvals and training in the scope, since moving files does not complete the publishing workflow.
Trial a representative content type in the destination before setting the full schedule. A small set of pages with complex references can require more work than a large collection of consistently structured articles. Record what the trial exposes, who must decide how to handle it, and which tasks can proceed together.
Choose the rollout separately. For URL moves, Google recommends moving small or medium sites together, while allowing larger sites to move in sections. A trial import does not commit you to a public launch in stages. Plan the content freeze, testing and way back around the rollout your team can support.
Where URLs change, map old pages to their relevant destinations and test permanent server-side redirects. Keep useful existing URLs where possible. The redirect strategy guide covers that work, and the first 30 days after migration covers the follow-up checks.
What should you do before the next renewal?
Put the notice deadline on the calendar, get the contract answers in writing and commission the sample export. Ask the technical team for a list of what transfers, what needs conversion and what needs rebuilding, with enough detail to scope each item.
If you need help establishing that scope, start with a Headless Audit. Bring the export findings and the publishing tasks your team needs to keep running. They give the discussion a concrete starting point for deciding whether to improve the current setup or plan a move.