What the service includes
Migration involves more than copying files. A website uses databases, email, certificates, DNS and often external integrations. We define what will move, prepare the destination environment and check the project before changing how its services are addressed.
Inventory before the move
We review domains, mailboxes, application versions, scheduled tasks and external connections. Current access and a list of critical components are needed. For a shop, we also consider how orders will be handled during the change. This information helps establish a schedule and any necessary interruption.
Tests in the new environment
We prepare copies of files and databases and check important functions such as forms, sign-in, checkout, payments and email. Some integrations cannot operate in a test environment, so we agree how they will be verified. Compatibility issues may require additional application updates before switching to the new server.
DNS changes and post-launch checks
We plan the switch around DNS caching and a final data synchronisation. Keeping the previous environment until verification finishes can help. After the change, we check the website, HTTPS and email. We also agree on conditions for returning to the previous configuration if a problem requires further work.
Communication during the move
Migration also involves organising people’s work. The team should know when to pause publishing and who confirms correct operation after switching. We help prepare a project-specific checklist. Larger websites should have someone responsible for business tests: server availability alone does not confirm that every process, integration or user journey works correctly in the new environment.
Information for the migration plan
Provide service addresses, mailboxes and approximate data volumes. Describe the current hosting and application requirements. Mention campaigns or periods when interruption would be especially disruptive. Include backup information and people with DNS access. Required credentials will use an agreed channel, and the test scope will be recorded before transferring data.