When a CMS has become a custom application
Over time, a content platform may accumulate business logic, custom fields, roles, imports and integrations. Replacing the CMS without understanding these additions can leave important work outside the new system.
We examine how editors, administrators and other users depend on the current platform. That helps separate standard publishing requirements from features that need a custom application or integration.
Choose a platform around the work
The target might be Drupal, WordPress, a headless CMS or a custom application with a content layer. The decision depends on content structure, editor experience, permissions, integrations and the team maintaining the result.
We can evaluate an existing platform choice or compare alternatives. A simpler publishing site and a platform with complex approval workflows should not inherit the same architecture by default.
Content, redirects and launch checks
A migration plan can include a content inventory, field mappings, media transfer, metadata preservation and checks for missing or changed content. URL mapping and redirects help visitors and crawlers reach the relevant replacement pages.
Before launch, we verify templates, navigation, forms, canonical URLs and indexability. Search performance can change during a migration, so we plan monitoring and follow-up corrections rather than promising unchanged rankings.
What to bring to the assessment
Share the current website, CMS version if known, the reason for moving and a list of features editors or customers rely on. Content volume, languages, integrations and any planned launch date are useful context.
The initial assessment outlines a direction and the main unknowns. Detailed discovery may be needed for heavily customized platforms. Implementation scope can cover migration scripts, content models, platform configuration, custom features, testing and handover.
Work directly with senior engineers
LegacyRefit offers remote consulting for teams in the United States, Canada, the United Kingdom, Australia and other markets. Meet the engineers and share your time zone when arranging a call.
An engineer will reply within 2 business days. Once we have enough context, we normally provide the initial assessment within 2 business days.
Get a free technical assessment