A website migration succeeds when data, traffic, and business functions arrive together. Copying files to a new server is only one part of that process.
Make an inventory
List the application, database, uploaded files, email services, DNS records, certificates, background jobs, and external integrations. Identify which services are moving and which remain where they are.
Record the existing setup and prepare a rollback decision. Decide who can authorize the cutover and what evidence would trigger a rollback.
Test the destination first
Restore a recent copy in a restricted environment. Check runtime versions, extensions, file permissions, redirects, and database connectivity. Prevent test jobs from sending real messages or processing live payments.
Verify the intended hostname and HTTPS behavior using an appropriate controlled test method. A temporary preview address may behave differently from the production domain.
Handle changing data
For an active store or membership site, a copy made yesterday may miss today's orders or registrations. Plan a final synchronization or maintenance window. Avoid allowing two independent servers to accept writes without a deliberate synchronization design.
Change traffic deliberately
Update the necessary DNS records and monitor both environments during the transition. Keep the previous server available for the planned overlap period.
Check login, forms, checkout, media, redirects, and background jobs after cutover. Verify email separately because website traffic moving successfully does not prove mail delivery works.
Define completion
Document the final configuration and ownership. Retire the old service only after the migration and retention requirements are satisfied.
Published for Alif Host. The exact migration process depends on the application and services involved.
Example: moving a store with new orders arriving
Consider a store that accepts orders throughout the day. A database copy taken in the morning will not include orders placed afterward. If the destination goes live from that copy in the evening, those later records may appear to vanish.
The migration plan needs a deliberate answer. A maintenance window can stop writes while the final copy is taken, or a carefully designed synchronization process can move later changes. The appropriate method depends on the application and available tools. Do not improvise a database merge during the cutover.
Remember uploaded files as well as database records. A new product image or customer attachment can be missing even when the relevant database row exists. Check whether the application stores files locally or in an external service.
Create a migration checklist with owners
Assign responsibility for backups, destination setup, application testing, DNS changes, email checks, and rollback decisions. Record when each item is complete and what evidence supports it.
Keep access available to both providers during the transition. Confirm account ownership and renewal dates before changing anything. Losing access to the old environment too early can make the final synchronization or recovery harder.
Document any differences between the old and new environment, including runtime versions, database settings, file paths, cron schedules, and security rules. A successful file transfer does not establish that those dependencies match.
Observe the overlap period
During DNS cache overlap, some requests may reach the previous destination. Decide how that server should behave and how to prevent conflicting writes. Check both access logs where available and use a consistent source of truth for transactions.
Monitor error rates, response times, certificate behavior, and application functions after the change. Ask the team to report the exact address, time, and symptom when a problem appears. This is more useful than a message saying that the site feels different.
Common questions
Can the old hosting be cancelled immediately?
Keep it for the agreed overlap and recovery period. Confirm data completeness and retention requirements before ending the service.
Does changing hosting require moving email?
No. The services can remain separate. Preserve the email provider's DNS requirements when moving website traffic.
Should the destination use newer software?
A migration and a major runtime upgrade are separate changes. Test compatibility and choose a change scope that the team can troubleshoot. Combining several changes without testing increases uncertainty.
Related Alif Host resources
For the platform specific steps, see How to Use cPanel File Manager to Upload, Edit, and Manage Files.
To review the relevant service scope and plan details, visit Alif Host shared hosting. Confirm the features you need before choosing a plan.
Top comments (0)