Website support and improvements
Website migration
We move websites to new hosting or a different CMS with attention to data, functionality and search URLs. Dependencies are inventoried before a trial migration is checked ahead of the switch.
Discuss the task
Pre-migration inventory
We collect pages, files, database requirements, forms, integrations and environment settings. We identify what changes with the platform and what must be preserved. For active websites, we agree how to synchronise changes between the trial migration and launch.
URLs and search structure
Old and new URLs, metadata and internal links are mapped. Useful addresses are preserved, while changed URLs redirect to equivalent pages. Canonicals, sitemaps and indexing restrictions left over from testing are checked.
Switch and verification
The project moves into a prepared environment where key journeys and the backup are checked. Switch timing and rollback conditions are agreed. After launch, we verify page availability, forms, data exchange and links that might still point to the old environment.
Cost and scope
Cost depends on data volume, platform changes, integrations and switch requirements. A detailed estimate follows an inventory of the current project.
Discuss the taskFrequently asked questions
How does hosting migration differ from changing CMS?
A hosting move generally keeps the application and changes its environment. A CMS change affects data structure, templates and features, and may require development and a separate content migration.
Can existing URLs remain unchanged?
Often, if the new platform supports the required structure. We check the URL map before development. Where an address must change, it is mapped and redirected to an equivalent page.