Files and application
The inventory includes website files, uploaded images, the PHP version in use, application dependencies and scheduled tasks.
Website migration, step by step.
Moving a website involves more than copying files. Orders, forms, email and domain records need to be considered together. Let's review your current setup to clarify the migration scope and transition steps.
Let's agree on the details before migration begins.
The scope, timing and any service fee depend on the current control panel, data size, application and access conditions.
Database and new records
The database size, character set, user permissions and final synchronisation method are defined. Websites that accept orders or registrations need a specific plan for write operations.
Email and DNS
Mailboxes, forwarding rules, MX and authentication records are assessed separately. Moving a website does not automatically move its mailboxes.
FINAL CHECK
Document every stage of the transition.
Check off completed items during preparation, launch and final checks. You can share the checked list with your team.
You can also start with a blank template.
Download the fillable text template for details before, during and after the transition. See the example of how a decision is made when a test fails before the DNS change.
A controlled transition in five steps
Each step distinguishes the information needed from you, the technical work to consider and the completion criteria. The parties carrying out the work are identified alongside the migration scope.
Inventory and scope
- What we need from you
- Domains, the current control panel, the application and a suitable transition time.
- What we address together
- Website and email transfer, required access and the parties carrying out the work.
- Completion criterion
- The scope, owners, schedule and any service fee are defined in writing.
Backup and rollback preparation
- What we need from you
- Critical data to protect and an acceptable data loss window.
- What we address together
- File and database copies, storage location and rollback method.
- Completion criterion
- The backup opens correctly and a copy is stored separately from the old server.
Testing in the new environment
- What we need from you
- Important pages, forms and workflows that must function.
- What we address together
- Version compatibility, login, form, email and any payment tests.
- Completion criterion
- Test results for critical operations are recorded before DNS changes.
Final synchronisation and DNS transition
- What we need from you
- Approval of the transition time and the authorised contact for domain records.
- What we address together
- Final transfer of new records, a maintenance window if needed, and the DNS change.
- Completion criterion
- New data is synchronised; destination DNS records and HTTPS are verified.
Final checks and closure
- What we need from you
- User checks and approval to close the old service.
- What we address together
- Website, form and email checks; temporary permissions and conditions for closing the old environment.
- Completion criterion
- Critical operations are verified, temporary access is removed and closure conditions are defined.
Information to share in a migration request
Enough for the first conversation
- Domains to migrate and the application in use
- Current control panel and approximate data size
- Mailbox count and email volume
- Target date, busy periods and special requirements
Include the application details
Payment integrations, external APIs, static IP allowlists, licences and custom DNS records can affect the transition. For e-commerce websites, a final synchronisation plan is especially important to prevent orders from being split between two environments.
Detailed migration checklist →FREQUENTLY ASKED QUESTIONS
Your questions answered
Will website migration be completely free of downtime?
A seamless transition can be the aim, but zero downtime cannot be guaranteed for every application and DNS setup. Websites with write operations may need a short maintenance window; potential impact and a rollback plan should be explained before the work begins.
Do I also need to transfer my domain?
No. Your domain can stay with its current registrar while DNS records point to the new hosting service. A domain transfer is a separate process subject to registrar rules.
Will my email migrate automatically?
No. Transferring existing messages, recreating mailboxes and changing MX records must be planned separately. If you use an external email provider, its relevant DNS records must be preserved.
Should I send my password through the form for migration?
No. Do not share passwords or private keys in your initial request. If technical access is needed, a secure sharing method will be agreed; temporary accounts with limited permissions are used where possible.
Let's build your migration schedule together.
Share your current website and your goal so we can define the technical scope, required access and verification steps.