Migration involves the source, destination and the services connected to them. Review those dependencies before deciding when to switch.
01
Review what you run
Tell SDH about the current hosting platform, websites, databases, email and data size. We review the environment and the access available before recommending the next step.
02
Agree the destination and plan
Choose a suitable SDH service, then agree the included work, responsibilities, schedule and any charges. Identify who approves the move and how secure access will be arranged.
03
Move and prepare the switch
The accepted plan identifies what will be copied, how recent changes will be handled and when to switch traffic. DNS and email changes follow the agreed cutover steps.
04
Validate and hand over
Check the agreed websites, data and email functions on the destination. Review any outstanding issues and recovery options before deciding when to retire the old service.
Make the first review useful
Gather the essentials before you enquire.
A public overview is enough to start. These details help SDH understand the work and identify what needs a closer review.
Website files and databases
List the websites, database types and versions, uploads and other data that need to move. Note any content that changes frequently.
Email and related services
Identify the mail provider, mailbox count, approximate mailbox sizes and how users connect. Confirm whether email is part of the requested move.
Domain and DNS control
Know who manages the domain, nameservers and DNS records. Note services that must keep working, including email and third-party connections.
Application stack and licences
Share the control panel, operating system, runtime versions, scheduled jobs and required extensions. Flag paid licences and external integrations.
Data size and backups
Provide an approximate total size and the date of your latest independent backup. Keep a usable copy outside the source hosting account.
Change window and approval
Explain busy periods, deadlines and who can approve decisions. Identify who will check the website and business functions after the switch.
Choose the right starting point
Where should your environment move?
Match the hosting and administration requirements to the destination. The service page explains its packages; the migration review confirms the work around the move.
A website moving to Shared Hosting
Explore hosting for your websites and business email. Request a review so compatibility, the migration schedule and any charges can be agreed before the move.
Migration scope and charges are agreed after review.
Choose dedicated hardware with the included managed Linux package. Free migration up to 500 GB is included; discuss the current environment and access needed with SDH.
The 500 GB migration benefit applies to SDH Managed Servers.
For multiple systems, complex applications or an existing server environment, discuss the work through Migration Services. The proposal defines the accepted transfer, validation and recovery steps.
Specialist migration work follows a separate agreed scope.
Your migration plan identifies the work SDH accepts, the decisions your team approves and the checks needed before handover.
Agree the scope and access
SDH and your authorized contact identify the systems, accepted tasks and required access. Share only a public overview in the initial enquiry; secure access follows the agreed onboarding process.
Protect the source and backup
Keep the existing hosting active and retain an independent backup until the move is verified. Agree which backup and recovery options will be available before making changes.
Approve the cutover
The plan identifies who changes DNS or related settings, when the switch can happen and how new content or mail will be handled. Review the effect on connected services before approval.
Check the result together
SDH checks the agreed technical items. Your team verifies the business functions it relies on, such as forms, email and application workflows. Review any follow-up work before closing the migration.
Before you move
Your migration questions, answered.
The accepted plan confirms compatibility, timing, included work and any charges. Ask SDH to review anything your application or business depends on.
Plan the switch before changing DNS
Keep your old hosting and an independent backup until the agreed checks pass. A registrar transfer is separate from moving a website or email.
What can SDH review for migration?
SDH can review website files, databases, email, DNS and the supporting hosting or server environment. The review establishes compatibility and the work to include. Do not assume every connected service will move automatically; the accepted scope identifies what is covered.
Is migration included or charged separately?
SDH Managed Servers includes free migration up to 500 GB. Discuss the source environment and access needed with SDH. For Shared Hosting and other migration requests, the scope, schedule and any charges are agreed after review. The managed-server benefit does not make every migration free.
Will my website stay online throughout the move?
Continuity depends on the source, destination, application behaviour and cutover plan. SDH reviews the change window and validation steps with you; uninterrupted service is not guaranteed. Plan how to handle new content, transactions and email while the move is in progress.
Should I cancel my old hosting before migrating?
Keep the old service active and an independent backup available until the agreed migration checks pass. Review any outstanding issues, recovery requirements and renewal dates before deciding when to cancel the source hosting.
Do I have to transfer my domain registration too?
Moving website files or email and transferring a domain registration are separate tasks. A registrar transfer does not copy the website or mailboxes. Domain and DNS arrangements should be reviewed as part of the migration plan; use the Domain Transfer service if you also want to move registration.
How long will the migration take?
Timing depends on data size, platform compatibility, available access, how often the source changes and the approved change window. SDH reviews these details before agreeing a schedule. This page does not promise a fixed completion time.
What should I include in my first enquiry?
Share the public website address, current hosting platform, approximate data size, whether email needs to move and any deadline. Do not put passwords, private keys or private customer data into the ordinary enquiry. SDH agrees the appropriate secure access process after reviewing the scope.
What should be checked after the move?
The accepted plan defines the checks. They may include page loading, HTTPS, database connections, forms, email, scheduled jobs and external integrations relevant to the work. Your authorized contact should also verify the business workflows the website or application supports before approving completion.
Let’s plan your move to SDH.
Share your public website address, current platform, approximate data size and what you want to move. We can review the next step with you.