A CMS export is not an email backup. A content management system stores website content, while mailboxes, marketing audiences, and message history usually live in separate systems. That distinction matters during a migration. The WordPress export creates a WXR XML file for posts, pages, comments, custom fields, taxonomies, and users, but it does not identify mailboxes or email messages among its contents.WordPress explains what its export contains.
Official resources:
- Explore the official data from FTC — Use this primary source to review the underlying data.
- Explore the official data from Cisa — Use this primary source to review the underlying data.
Table of Contents
- What a CMS export does—and does not preserve
- Which email records should be backed up?
- How should a migration checklist handle limitations?
- What compliance risks can appear after the move?
- Where should the backup live?
- Frequently Asked Questions
What a CMS export does—and does not preserve
A cms migration file usually covers the website itself: page content, media references, users, categories, tags, comments, and configuration supported by the migration tool. It does not prove that an organization has preserved its email system.
Email records may include employee mailboxes, shared inboxes, customer messages, attachments, headers, folders, labels, and account settings. Google's Gmail export separately includes message content, headers, attachments, labels, and settings, showing why mailbox data needs an email-system export.Google documents Gmail's separate export scope Treat these as separate workstreams:.
- CMS content: pages, posts, media, users, taxonomies, and custom fields
- Business email: individual mailboxes, shared mailboxes, messages, and attachments
- Marketing email: audiences, consent records, suppressions, campaigns, and reports
Which email records should be backed up?
Start with records that affect daily operations and business continuity. These may include current employee mailboxes, former employee mailboxes, shared addresses such as support@, and messages needed for customer service, contracts, or project history. Microsoft advises administrators preserving a former employee's mailbox to place it on hold or export it to a `.pst` file, which can later be imported into another email account.Microsoft's former-employee mailbox guidance Marketing records need their own inventory.
A Mailchimp audience export can preserve fields, marketing permissions, opt-in timestamps, opt-in IP addresses, confirmation timestamps, notes, and tags.Mailchimp lists the records included in an audience export That export is not complete history. Mailchimp says a standard audience export omits signup source, opens and clicks, purchase history, and a complete contact-update history. If those records matter, capture the relevant reports separately.
How should a migration checklist handle limitations?
Document each system, owner, export format, date, and verification result. A checklist should identify not only what was exported, but also what the export excludes.
For an email or marketing platform, check: Campaign reporting may require extra work. Mailchimp's aggregate campaign-report CSV excludes subscriber-specific opens and clicks, which require separate individual open and click reports.Mailchimp explains the limits of its campaign-report export After exporting, open representative files and test restoration. Confirm that messages, attachments, labels, permissions, and contact fields remain usable in the destination system.
- Mailboxes and shared inboxes
- Attachments, labels, folders, and settings
- Former employee accounts and required holds
- Subscriber permissions, unsubscribe records, and suppressions
- Campaign reports and subscriber-specific engagement data
What compliance risks can appear after the move?
Email migrations can create compliance problems when unsubscribe or suppression data gets lost. U.S. commercial-email senders must honor an opt-out request within 10 business days, according to the Federal Trade Commission.The FTC summarizes CAN-SPAM opt-out requirements Before launching new forms or campaigns, reconcile old and new suppression lists.
A contact who previously opted out should not become eligible again simply because the website, CRM, or email platform changed. Retention policies and backups also serve different purposes. Microsoft distinguishes retention from backup, and legal holds preserve email for export and eDiscovery rather than providing an efficient mass-restoration system. Do not treat a legal hold as the migration recovery copy.
Where should the backup live?
Keep the email export independent from the CMS migration package. Store it in a controlled location with restricted access, clear retention rules, and enough documentation for another administrator to understand what it contains.
Use a simple recovery test: CISA's practical backup guidance uses the 3-2-1 rule: three copies of important data, on two media types, with one copy offsite. Applied to a CMS migration, the separate email export should have its own independent copy and a tested restoration path.CISA describes the 3-2-1 backup approach.
- Identify a sample mailbox, message, attachment, contact, and campaign report.
- Restore or import each item into a safe test location.
- Confirm that dates, recipients, attachments, labels, permissions, and opt-out status remain usable.
- Record the result and keep the export until the migration has been accepted.
Frequently Asked Questions
Is exporting WordPress enough to protect business email?
No. WordPress's WXR export covers CMS content and related records, not a complete mailbox archive.
Should marketing contacts be exported separately?
Yes. Audience fields and permissions may be preserved, but signup sources, engagement history, and update history may require additional exports.
Can a legal hold replace an email backup?
No. A legal hold supports retention, export, and eDiscovery. It is not designed as a convenient mass-restoration backup.
You Might Also Like
- Why Old CMS Paths Keep Appearing in Logs After a Website Migration
- What Is New With CMS Migration and Web Development in August 2026? Latest release notes and search documentation and Key Takeaways
- How to Verify CMS Migration and Web Development Claims in 2026: release notes and search documentation, Evidence, and Red Flags
