Clarity before
commitment.

It is the transfer and adaptation of an agreed set of content, assets and functionality from a dotCMS installation to a WordPress destination. It can include a new content model, rebuilt templates, integration changes and a coordinated release.

That depends on the content model, publishing workflows, integrations and operational requirements. We review those requirements first and identify trade-offs before defining the destination.

It can be used as the brief for the WordPress build. Source templates and rendering logic may need rebuilding. A migration can also accompany a redesign, but that scope is agreed separately.

We review the source types and fields, then map them to appropriate WordPress content types, fields, taxonomies and relationships. A representative pilot checks the model before the full transfer.

They are included in the asset inventory when in scope. We map references, transfer the required files and check their destination links. External or restricted assets need an explicit access and ownership decision.

Language variants and their connections need a defined target model. We confirm the language workflow, URL structure and translation relationships, then include them in the import and QA plan.

We aim to retain suitable URLs and map changed ones to relevant destinations. Search rankings can fluctuate and cannot be guaranteed. The search workstream covers baseline data, redirects, metadata, indexing checks and post-launch monitoring.

We reconcile the agreed source and destination inventories, retain source identifiers where useful, and check fields, assets and relationships. Functional and editorial checks complement the data checks; exceptions are recorded for review.

Content volume is one factor. Source access, content complexity, languages, design, integrations and review requirements also affect the work. We establish the scope before proposing a timeframe or price.

Usually the destination can be built while the source remains in use, but the final content changes need an agreed plan. That may involve a short freeze or a final update process before release.

No. Start with a public URL and an overview of content, integrations, timing and constraints. We arrange any required access separately and securely.

The service is built and delivered by DigiSteer Ltd. The DigiSteer team is your contact for the initial conversation. Learn more about DigiSteer.

This is an independent DigiSteer service. It is not affiliated with or endorsed by dotCMS or WordPress.

We share named client material only where publication is authorised. In the initial conversation, we can explain our method and the evidence we would agree for your project.