Editorial content
Pages, posts, articles, custom types, publication state, dates, excerpts, and authors.
What the migration covers
The exact entity scope depends on the source and destination, but the migration plan accounts for both visible content and the relationships that make it usable.
Structure
Fields, taxonomies, categories, tags, relationships, references, and reusable content.
Assets and users
Images, documents, alt text, supported users, roles, and ownership.
SEO data
Slugs, titles, descriptions, canonicals, internal links, source URLs, and redirects.
What requires separate scope
Visual design, templates, application functionality, unsupported plugins, forms, checkout behavior, and destination development are not assumed to transfer automatically. They are documented and quoted separately when needed.
How we deliver it
- 1. Inventory: Crawl and query the source to establish entities, fields, assets, URLs, and exceptions.
- 2. Map: Approve destination types, fields, transformations, fallbacks, and URL rules.
- 3. Dry run: Transfer representative content and resolve systematic exceptions in staging.
- 4. Validate: Reconcile totals and inspect complex records, assets, metadata, links, and rendering.
- 5. Cut over: Run the approved production and delta plan with launch checks and rollback conditions.