CMS migration checklist for retail content

Plan a CMS migration with a content inventory and transfer matrix. Map records, media and URLs, then validate the new publishing flow and recovery route.

A CMS migration moves content into a new content management system through a supported export, field mapping and import, followed by checks on the published result. Retail teams must also repair references and preserve public URLs, or redirect them to the matching new pages.

Records transfer only where the two systems support compatible fields. Templates, permissions and integrations need separate rebuilding when the transfer method excludes them. A successful import can still leave a customer reading an old returns policy, so include every system that uses your content in the migration plan.

Establish what can transfer

Inventory the content before choosing an import method. Record each item’s owner, content type, publication state, locale and public URL. Include media files, alt text, internal references and reusable blocks. Note which fields hold approved policy text and which pages reuse that text.

Keep content records separate from presentation templates. A delivery-policy record holds the rules. A template decides how those rules appear on the storefront. Moving the record does not prove that its headings, links or layout will work in the new template.

Orders, payments and customer accounts belong in a separate commerce-data plan. A CMS content migration must not silently replace the systems that own those records.

Assign each inventory item one outcome: retain unchanged, revise with approval, combine with another record or retire. Preserve a copy of every approved source version before making revisions. If the current CMS already supports the required workflow, weigh the rebuilding effort against the reason for switching.

Build a transfer matrix

Use a transfer matrix to record what the chosen method actually supports. Each row needs a source object, destination, retained fields, exclusions and a named person responsible for manual work. Treat an untested mapping as work to validate before the full import.

The following is a fictional retailer’s planning example for moving content between two HubSpot accounts. It combines documented methods with explicitly assigned rebuilding work.

ItemSupported methodRetained contentOutside this transferManual action
Source page archiveExport pages and posts as HTMLExported HTML and template filesA ready-to-use destination siteKeep the archive and compare rebuilt pages
Website page structureScan the published source site with the destination’s website importURL slug, title and meta descriptionPage body contentChoose templates and rebuild the body
NavigationReview menus found by the website importImportable menu items and linksItems the scan cannot importRepair missing items and inspect destinations
Blog recordsPrepare and map a CSV to the blog importerMapped post fields, including post bodyAutomatic conversion of every source fieldTransform the source data into the required columns
Roles and integrationsSeparate configuration workOnly settings explicitly recreatedPermission and integration parity from a content importRecreate access and test each integration

HubSpot’s content export instructions describe HTML exports and the permissions required. Keep that archive independently of the destination import.

Its website import brings across page metadata and scanned navigation, but excludes page body content. Its blog CSV import is a different route that accepts mapped post bodies. A website scan and a blog import are separate migration tasks.

Map and move the approved content

Back up the source before exporting, then map the destination schema before importing records. A schema defines content types, their fields and the references between them. Record field conversions so the team can repeat the migration without guessing.

Use this order for the controlled transfer:

  1. Save source records, media and configuration backups using the source system’s supported methods. Confirm who can access and restore them.
  2. Set a content-change period. Either freeze routine edits or log every source change for a final repeat export. Keep a route for urgent policy corrections.
  3. Export the approved content set. Record counts by content type, locale and publication state, including deliberate exclusions.
  4. Map source fields to destination fields. Set rules for missing values, rich text, references and duplicate records. Preserve a table matching old record identifiers to new ones.
  5. Import a small representative batch into a private destination. Include a policy page, a media-heavy guide and a record with references.
  6. Repair media paths and record references, then inspect the rendered pages. Correct the mapping before importing the remaining approved records.
  7. Apply the final logged changes and reconcile counts. Prevent the old and new CMS from becoming two competing publishing sources.

For a HubSpot blog CSV, prepare the required URL, title, SEO title, author, meta description, publish date and post body columns. Map the columns and inspect the preview. Review the imported posts before publication, and deliberately decide whether existing matching content can be replaced.

Moving from a conventional CMS to headless

A conventional-to-headless migration changes who builds and previews the page. In a headless setup, the CMS supplies content to a separate rendering application. That application must implement page templates and resolve content references.

Assign preview access, draft handling and publication updates to named owners. A record that looks correct in the CMS can still render incorrectly on the storefront. Include navigation, metadata and links in the rendering work, then test how a content change reaches the public page.

Validate the storefront and answer sources

Validate both the imported records and the customer-facing result. Counts alone cannot prove that a delivery threshold, product-care warning or returns exception survived the move.

Record the expected results

CheckExpected resultInvestigate when
Record countsDestination totals match the approved source set after documented exclusionsRecords are missing or duplicated
Sampled fieldsApproved text, locales and publication states match the sourceFormatting changes meaning or a draft becomes public
References and mediaLinked records resolve and intended files loadLinks point to old identifiers or inaccessible media
Public URLsRetained URLs load and changed URLs reach the matching destinationA redirect loops, chains or lands on an unrelated page
Policy renderingThe storefront shows the approved policy version with its exceptionsThe CMS and visible page disagree
Publishing flowAn authorised change reaches the intended page and unauthorised users cannot publishOld permissions or update triggers remain active

For search engine optimisation (SEO), map every changed URL to its closest replacement. Update internal links, canonical URLs and the sitemap to use the new destinations. Google’s site-move guidance recommends direct permanent redirects and monitoring both old and new URLs. It also warns that rankings can fluctuate while pages are recrawled.

Check retrieval separately

A content move does not automatically update a search index or an AI assistant’s knowledge source. List every feed, crawler and document upload that can supply store answers. Change each connection to the intended new content, then complete its refresh or re-import process.

Use a private withdrawal test. Put a distinctive test rule into a test policy, confirm retrieval finds it, then withdraw it and refresh the source. The next test must use the replacement rule and stop retrieving the withdrawn text. Check the retrieved source record as well as the answer.

Repeat a delivery question and a returns question against the approved policy. Inspect caches and duplicated documents if an old rule survives. Release the new source only when the storefront and retrieval checks agree.

Cut over with a recovery plan

Cut over through a written sequence with one person authorised to proceed or stop. Assign CMS access, publishing permissions, notification recipients and integration credentials before the switch. Include the owner of redirects and anyone responsible for updating answer sources.

Record the change window, the last accepted source edit and the conditions that stop the cutover. Missing policy text, broken checkout-adjacent links or an unapproved version in retrieval require a correction before proceeding.

Retain the old records and backups through the agreed recovery period. If the platform supports restoring a snapshot or switching traffic back, rehearse that exact route privately. Record what it restores and what it leaves behind. A content export alone does not reverse new edits, changed URLs or integration activity.

If the recovery route is a manual rebuild from retained records, assign that work and its limits explicitly. Keep a log of changes made after cutover so a return to the old system does not discard approved updates.

After the switch, monitor broken links, failed publishing jobs and stale answers. Send each issue to the responsible content, development or platform-support owner with the affected record and expected result. Keep old subscriptions and source access until the team confirms that recovery no longer depends on them. Close the migration when the approved pages and answer sources pass their checks and support owners accept the handover.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup