Website Content Migration Plan (2026): CMS Field Mapping & Import Checklist

CMS Content Migration vs. SEO Website Migration

A CMS content migration focuses on transferring structured information between content management systems. An SEO website migration focuses on preserving the accessibility and search signals of public URLs when a website changes.

These processes are related, but they require different deliverables.

This guide focuses on the CMS content workstream.

If your migration also changes domains, public URLs, canonical settings or hosting infrastructure, use our separate SEO Website Migration Checklist.

What Should a CMS Content Migration Plan Include?

A practical migration plan needs four connected documents:

1. Content inventory: Every approved record that needs to move.

2. Field mapping: How information is converted from source fields to destination fields.

3. Relationship mapping: How authors, categories and related content remain connected.

4. Import and QA tracker: Whether each record was imported, checked and approved.

Together, these documents help developers and editors answer three questions: What should move? Where should it go? How will we know it arrived correctly?

Define your migration boundaries

Before exporting anything, identify which collections are in scope.

For a SaaS marketing website, these might include Articles, Authors, Categories, Case Studies and Resource Downloads.

Also document exclusions. For example, product application data, billing records and customer credentials may belong to systems outside the marketing CMS.

A content migration should not silently expand into a complete software application migration.

Step 1: Audit the Source CMS Collections and Records

Start with the source CMS rather than the destination website design.

Every CMS collection has a set of fields, records and relationships. You need to understand that structure before deciding how it should be recreated.

Build a source content inventory

All values in this example are illustrative.

Compare records from multiple sources

A CMS export may contain published articles, drafts and archived records.

An XML sitemap generally represents only certain public URLs.

Compare the source CMS with available website inventories so you understand which records should be transferred, but don't confuse a sitemap with a complete CMS database export.

Assign each record an action

Use the following statuses:

• Migrate: Transfer the record while preserving its intended content.

• Migrate and Update: Transfer it with explicitly approved corrections.

• Archive: Preserve the record without publishing it.

• Consolidate: Handle overlapping records through a separately approved editorial decision.

• Exclude: Keep the record outside the destination CMS.

Do not automatically delete or rewrite content merely because the website is moving platforms.

Step 2: Build a Source-to-Destination CMS Field Mapping Template

Field mapping is the most important technical document in a content migration.

A field called Author might be a text string in one CMS and a collection reference in another. A rich-text field might export as HTML but require conversion before being inserted into the destination editor.

Matching field names alone does not ensure that data will transfer correctly.

CMS Field Mapping Template

Decide how to handle missing fields

If the destination CMS does not have an equivalent field, do not silently drop its data.

Record whether the field should be:

1. Added as a new destination field.

2. Converted to a compatible type.

3. Merged into another field.

4. Preserved in a separate archive.

5. Excluded with an approved reason.

For example, an older CMS may store a short author biography inside every article. The destination could instead use a central Authors collection and reference it from each article.

That change improves maintainability, but it requires a deliberate relationship-migration step.

Define stable record identifiers

Keep source identifiers in your migration workbook even if the new CMS generates different internal IDs.

You need a way to match the original record to its destination record when imports fail or when content has to be corrected.

A consistent slug can help with matching, but slugs are not always permanent or unique across collections. Record identifiers and collection context are more reliable for reconciliation.

Step 3: Back Up Content, Media and Related Records

Before changing the source data, create a backup that you can actually restore or inspect.

A single CSV file is not always a complete backup of a website.

It may contain article field values without the underlying images, layout templates, custom components, integrations or collection relationships.

Recommended backup checklist

• 
  

  Original CMS collection exports are saved.

• 
  

  Authors, categories and related collections are included.

• 
  

  Rich-text content is preserved in a readable representation.

• 
  

  Featured and embedded media are backed up.

• 
  

  Publication dates and content status are recorded.

• 
  

  Custom SEO metadata is retained.

• 
  

  Source record identifiers are preserved.

• 
  

  Original site access remains available during QA.

• 
  

  The backup files can be opened and checked successfully.

Understand platform-specific export behavior

Webflow: Webflow's CMS exports use CSV. Its documentation explains that rich-text content is exported as HTML, while many other fields are exported as text or URLs. Source-hosted asset URLs need special attention when the original site may be deleted.

Framer: Framer offers CMS import workflows and an official CMS Export marketplace plugin for transferring collection data as CSV.

The supported import behavior is not identical between platforms. Verify image, rich-text and relationship handling for your specific source and destination before beginning a large transfer.

Protect the source environment

Keep the original CMS accessible until the new content and assets have passed verification.

Exporting a row containing an image URL does not prove that the destination owns a permanent copy of that image.

For important assets, confirm that the destination can continue serving them independently of the old project.

Step 4: Design the Destination CMS Collections

Before importing records, establish a maintainable destination structure.

A typical technology publication may use separate collections for articles, authors and categories.

Example destination architecture

The structure should match real editorial needs. A small site does not need additional collections merely to appear technically sophisticated.

Why separate author records?

Suppose one writer is responsible for dozens of articles.

Copying the same portrait, biography and LinkedIn URL into every article creates unnecessary duplication.

A shared Author reference allows the visible author card to use one profile record.

However, the author reference still needs to resolve correctly in the destination CMS and, where applicable, in the site's structured data.

Confirm required fields before import

Define which fields must be populated.

For Articles, common required values include the title, slug, main content and author reference.

Other fields, such as an optional external source link or secondary CTA, may be allowed to remain empty.

Make those rules explicit before the import rather than discovering incomplete records after publication.

Step 5: Migrate Authors, Categories and Reference Relationships

References must be transferred as relationships, not treated only as labels.

An article containing the plain text author-001 is not necessarily connected to the matching author record.

Recommended migration order

1. Create the destination collection schemas.

2. Import or create author records.

3. Import or create categories and other shared records.

4. Generate a source-ID-to-destination-ID mapping.

5. Import article records.

6. Populate the article reference fields.

7. Verify the visible output and relationships.

The order may differ depending on the destination CMS and its import capabilities.

Relationship Mapping Template

This is an illustrative worksheet, not a record of a completed migration.

Webflow reference import considerations

Webflow's August 2026 CMS import documentation supports mapping text or slugs to reference fields, provided the referenced records can be matched correctly.

Its separate collection-to-collection migration guide also describes a fallback workflow: import reference data into temporary plain-text fields, recreate the reference fields, and then populate the relationships.

Which method works depends on the source values and how the target collections are configured.

Always validate references after importing. Do not assume a successful CSV upload guarantees every relationship has been restored.

Test author changes centrally

After migration, update a test author's biography in the Authors collection.

Then confirm that every associated article displays the updated profile correctly.

This is a practical way to confirm that the website uses an actual shared reference instead of duplicated static text.

Step 6: Migrate Rich Text, Tables, Lists and Embedded Content

Article bodies are more complicated than plain text.

An exported document might contain headings, paragraphs, inline links, images, tables, lists and embedded components. Different CMS editors represent these elements differently.

Rich-Text Migration QA Matrix

Choose representative test articles

Test at least one example of each important content pattern.

A useful pilot might include a long technical guide, a software comparison with tables, an article containing many internal links, and a post with several embedded images.

If the destination cannot represent a specific formatting element, document the conversion method before importing the complete library.

Don't paste unsupported HTML blindly

HTML exported from the source platform is not necessarily compatible with every rich-text editor.

For example, Webflow's importer may sanitize unsupported HTML content, embeds, classes and attributes.

Validate the supported representation and rebuild special components where necessary.

The goal is to preserve the article's meaning, structure and usability, not to carry obsolete markup into a new platform.

Avoid unnecessary content rewrites

A platform move already introduces technical risk.

If a well-performing article needs only formatting conversion, retain its approved copy.

Record substantial editorial revisions separately from migration transformations so the team can identify why any content changed.

Step 7: Transfer Images and Other Media Assets

CMS image fields and images embedded inside rich-text bodies may require different transfer procedures.

Do not assume that importing a featured-image field also transfers every illustration or screenshot within an article.

Asset Migration Checklist

• 
  

  The original file has been backed up.

• 
  

  The file is licensed or otherwise authorized for use.

• 
  

  The destination uses the intended image.

• 
  

  The file does not depend unexpectedly on a deleted source project.

• 
  

  Descriptive alternative text is restored where supported.

• 
  

  Cropping and aspect ratios are appropriate.

• 
  

  Embedded images remain in the correct article positions.

• 
  

  Important screenshots remain readable on mobile.

• 
  

  Any broken or outdated assets are flagged for review.

Media verification example

A destination article might display a featured image successfully but contain three embedded screenshots that still load from the original CMS.

If the source system is deleted later, the screenshots may disappear.

Therefore, verify featured images and rich-text media separately.

Similarly, a source image URL copied into a destination field may remain externally hosted instead of being imported as a new managed asset.

The correct result depends on the platform's import behavior and the migration requirements.

Step 8: Preserve SEO Fields, Dates and Publication Status

Content migration must preserve accurate editorial metadata.

That does not mean turning this guide into a complete SEO redirect tutorial.

The objective here is to ensure that the destination CMS record contains the correct information for its page template.

Metadata Acceptance Table

Don't mistake import dates for publication dates

A destination CMS record may be created today even if its article was originally published months or years ago.

Record creation and publication are not necessarily the same event.

Preserve the original publication date when migrating existing public content. Use a separate editorial update date where appropriate.

Check the final CMS template

A correct record can still display incorrectly if the destination template uses the wrong field.

For example, an article may reference the right author but its custom JSON-LD could point to an incomplete profile URL.

After content QA, verify representative published output against the article record. Google's Article structured-data guidance identifies author profile URLs, relevant images and accurate publication dates as useful properties.

For the broader canonical, indexing and URL-move implications, consult the SEO Website Migration Checklist.

Step 9: Run a Controlled Pilot CMS Import

Never make the first test a complete production import of hundreds of articles.

Instead, choose a small set of records representing the main content types and difficult formatting cases.

Recommended Pilot Sample

Pilot workflow

1. Create the destination collections and required fields.

2. Import the representative records into a safe test state.

3. Verify each field against the source export.

4. Preview the detail pages.

5. Inspect references, images, tables and inline links.

6. Record any failures and the transformation needed to fix them.

7. Repeat the test until the agreed acceptance criteria are met.

Define a rollback or recovery path

Keep the source records and original exports available.

If a pilot import duplicates records or corrupts formatting, you need a way to identify and reverse only the affected changes.

Avoid repeatedly importing the same file without understanding whether the destination creates new records or updates existing ones.

A repeatable import process should use stable matching identifiers whenever the platform supports them.

Step 10: Import the Full Dataset and Reconcile Records

After the pilot succeeds, import the approved dataset using the tested procedure.

The most important step now is reconciliation: confirming that the source and destination contain the expected records and values.

CMS Import Reconciliation Template

All records and statuses here are illustrative.

Compare counts by meaningful status

Do not compare only one total number.

Separate the count of approved published articles, drafts, archived records, and deliberately excluded entries.

For example, if 100 source records include 80 published items, 15 drafts and five exclusions, a destination with 95 entries might be correct only if the 80 published and 15 draft items all exist and are properly classified.

Matching totals alone do not prove a successful migration.

Investigate duplicates and failed rows

A failed import may result from a missing required field, invalid reference, unsupported formatting or a field-value mismatch.

Record the specific error, correct the underlying value or mapping, and rerun the affected records through the supported update workflow.

Check that repeating an import does not create unintended duplicate articles.

Step 11: Perform CMS Content and Template QA

Record validation and visible-page validation must both pass.

A correct article entry may still render incorrectly if the template uses an outdated field or unsupported layout.

Final CMS QA Tracker

Test shared templates separately

If 100 articles share a single blog detail template, a binding error may affect all 100.

Check representative articles with different title lengths, authors, image ratios, rich-text structures and publication dates.

Make sure that the template can handle missing optional fields without displaying confusing placeholders.

Don't overlook the editor workflow

Ask a nontechnical editor to perform routine tasks in the destination CMS:

1. Create a draft.

2. Select the correct author.

3. Choose a category.

4. Add formatted content.

5. Set SEO metadata.

6. Preview the article.

7. Save it without publishing.

If this workflow is difficult or repeatedly damages content, the migration may be technically complete but operationally unsuccessful.

Step 12: Complete the CMS Migration Handoff

A final migration handoff should give the website owner enough information to maintain the destination CMS.

Essential handoff documents

• Approved source-to-destination collection map.

• Final field mapping spreadsheet.

• Author and category reference map.

• Asset inventory and storage details.

• Import reconciliation results.

• Outstanding issues and exceptions.

• Editorial publishing instructions.

• Backup and recovery information.

• Administrative access and ownership responsibilities.

When is the content migration complete?

Consider the CMS content workstream complete when all approved records have been reconciled, critical fields and references are accurate, representative content renders properly, and editors can safely maintain it.

If the project also changes public URLs or hosting, the SEO migration workstream has its own validation and sign-off requirements.

Content migration and search migration can share a project plan without duplicating the same audit process in two documents.

Example: Moving a SaaS Publication into Framer CMS

Consider an illustrative technology publication with a collection of articles, a shared author profile and several editorial categories.

The company wants to move its content to Framer while preserving author information, metadata and rich-text formatting.

Source content model

The old CMS stores article titles, slugs, HTML bodies, SEO metadata and author IDs.

Destination content model

Framer contains an Articles collection and a separate Authors collection. Each article has an Author reference, a rich-text Content field, SEO metadata fields, an Image field and a Date field.

Migration sequence

First, the team inventories all source records and exports its CMS data.

Next, it builds an explicit field mapping and creates the Authors collection.

The team imports the author records, transfers representative articles, and checks reference relationships.

It then verifies tables, lists, images, titles, dates and author information in the page template.

After correcting any pilot issues, it imports the approved dataset and reconciles records by stable source identifiers.

Finally, an editor reviews representative articles and confirms that the destination CMS is safe for routine publishing.

The critical success measure is not the number of records uploaded. It is the accuracy and maintainability of the resulting content system.

This example is a workflow demonstration, not a claim about a completed client project.

Common CMS Content Migration Mistakes

Importing author names without actual references

The correct author name may appear in a text field while the Author relationship remains empty.

Verify the destination reference, not just the visible label.

Assuming an imported image URL means the image is transferred

The image may still depend on the original platform's hosting.

Validate asset ownership and availability separately.

Overwriting original publication dates

A new CMS record creation date does not necessarily represent when the article was first published.

Preserve historical dates where they can be verified.

Migrating only simple articles

A basic paragraph test does not prove that long technical articles, comparison tables or embeds will survive.

Include edge cases in the pilot.

Reimporting failed records without deduplication

Repeated imports can accidentally create multiple versions of the same article.

Use a reliable matching and reconciliation process.

Treating the CMS import as a complete SEO migration

A correct content database does not automatically confirm redirects, domain settings, canonical URLs or Google indexing.

Those belong to the SEO website migration workstream.

Final CMS Content Migration Checklist

• 
  

  Source CMS collections and records are inventoried.

• 
  

  Every required destination field has an approved mapping.

• 
  

  Source and destination record identifiers are tracked.

• 
  

  Content and media backups are verified.

• 
  

  Author and category records are prepared.

• 
  

  References are mapped and tested.

• 
  

  Rich-text conversion is validated.

• 
  

  Embedded images and featured assets are checked.

• 
  

  Original publication dates are preserved.

• 
  

  Draft and archive states are handled correctly.

• 
  

  A representative pilot import has passed.

• 
  

  Failed and duplicate records are resolved.

• 
  

  Source and destination counts are reconciled.

• 
  

  Important CMS templates render properly.

• 
  

  Desktop and mobile content is usable.

• 
  

  SEO metadata and schema fields are checked.

• 
  

  Editors can safely maintain the new CMS.

• 
  

  Final documentation and access are handed over.

Final Recommendation: Validate the Data, Not Just the Import

A successful CMS migration preserves more than the words in a blog post.

It preserves the relationships, media, metadata, publication history and editorial processes that make the content useful and maintainable.

Start with a complete inventory and an explicit field mapping. Build the destination structure before importing large amounts of content. Test difficult records first, then reconcile the full dataset and verify the visible pages.

If public URLs or domain settings also change, manage those risks through a separate SEO migration plan.

A CMS content migration is complete when the destination records are accurate, the page templates work correctly, and the content team can confidently publish and maintain the website.

Official Sources and Further Reading

• Webflow — Import Content into the CMS

• Webflow — Migrate CMS Collection Content Between Projects

• Framer — CMS Export Plugin

• Framer — Add CMS Content with Framer Agents

• Google Search Central — Article Structured Data

• Google Search Central — Site Moves with URL Changes