Content inventory & decisions
Identify the source records and assets, then decide what to keep, transform, consolidate or exclude. The inventory becomes the reference for the migration.
01 / Migration scope
Move the site.
Keep the meaning.
A content-led migration from dotCMS to WordPress, planned around your information model, your users and the work your site needs to do.
Start with the system
The pages are only part of it.
A dotCMS site can combine structured content, page layouts, media, relationships and delivery logic. Copying visible pages alone can leave the supporting information behind.
We review the source as a system, then define a WordPress model for what needs to be retained. The scope is explicit: content transfer, destination build, integrations and launch are agreed as separate, connected workstreams.
- Content types, fields and publishing status
- Images, documents, metadata and references
- Taxonomies and relationships between records
- URLs, language variants and internal links
- Templates, forms and external dependencies
- Editorial roles and handover requirements
The scope, made concrete
What we plan with you.
WordPress content architecture
Map source fields into pages, posts, custom content types and taxonomies as appropriate. Define relationships and editorial controls before committing to a build.
Controlled transfer & reconciliation
Prepare repeatable imports with source identifiers, clear transformation rules and exception reporting. Check record counts and connections against the agreed scope.
Destination build & release
Agree the design and templates, rebuild the necessary functionality, and test the site with stakeholders. Plan a content freeze or final update so the live source is not left behind.
Decide deliberately
Migration, redesign or both?
A platform move can preserve the existing experience, or accompany a redesign. Those choices affect templates, content transformation, review time and launch coordination.
We separate the decisions so the project has a clear purpose and a usable acceptance plan.
In the assessment
We clarify the source and destination, content scope, available exports, integration dependencies, responsibilities and release constraints. Pricing and timing follow that understanding.
Delivery, with visibility
Know what moved. Know what needs attention.
The migration should leave you with more than a populated website. We agree the evidence needed to review the result and support your next step.
| Deliverable | What it helps you review |
|---|---|
| Content & asset inventory | The source baseline and the agreed inclusion rules |
| Field & relationship mapping | How source information becomes usable WordPress content |
| URL decision map | Retained paths, new destinations and required redirects |
| Import & exception report | Transferred records, unresolved items and decisions required |
| QA & release checklist | The agreed functional checks, launch sequence and rollback steps |
| Editorial handover | How your team edits, publishes and maintains the destination |
Start with a conversation
Your next CMS.
A clearer way forward.
Bring us the site you have and the challenges you want to leave behind. We’ll start with the right questions.