Zevonix Cloud
Menu

Move Your Website with a Clear Cutover Plan

A scoped move with testing, final sync and a recovery route.

Website copied from its source to a reviewed destination.

A move should account for the website, its data and the services connected to it. We review the current setup, agree the work and test the copied site before planning the public cutover.

Hosting plans from $49.99/month

These are monthly hosting prices. Migration and onboarding coverage, any fee and exceptional work are confirmed in the quote or Service Summary before work starts.

The source website, a test copy and an approved destination in sequence.
A move with three clear decisions

Inventory the current service, test the copied site and approve the cutover with a recovery route agreed in advance.

  • Review the source
  • Test the copy
  • Approve the move

The migration process

  1. Discover the dependencies. Identify the platform, versions, domain and DNS ownership, licences, forms, email delivery, integrations and important URLs.
  2. Capture a recoverable source. Agree which files and databases are copied and which backup or export can be used if the move needs to be retried.
  3. Import into a test environment. Confirm compatibility and access restrictions before testing the copy.
  4. Check the business functions. Review pages, media, forms, logins and integrations with the people who use them.
  5. Plan the final sync. Decide how new orders, posts, comments and submissions are handled while the move is under way.
  6. Agree the cutover. Coordinate DNS, SSL and any external services, then check the intended public routes.
  7. Keep a recovery route. Confirm what can be rolled back and how long the previous host must remain available.

Confirm coverage and costs first

The quote or Service Summary identifies the migration and onboarding work covered. Large data transfers, unsupported software upgrades, custom integrations or rebuilding a site can require additional work. We confirm the scope and any fee before starting.

Domains and email need their own review

Moving a website does not automatically move inbound business email. We review DNS records and the existing email provider to avoid treating mail as part of a routine website-file transfer. Domain ownership and renewal arrangements remain important after cutover.

Define success using the site

Agree the pages and functions to check, who can approve them and which test messages or transactions are permitted. A successful copy or an HTTP 200 response alone does not establish that every business workflow works.

Migration questions

Is migration always free?

No blanket free-migration promise applies here. Coverage and any fee are confirmed for the specific move before work starts.

Can existing URLs be preserved?

We review routes and links before moving. Preserve working URLs wherever possible and agree redirects for intentional changes.

Will the move have zero downtime?

That should not be assumed. DNS behaviour, data sync and external services affect cutover; the plan sets expectations for the workload.

What should I provide first?

The public site URL and an outline of its platform and dependencies are enough to begin assessment. Access is arranged through an agreed secure process later.

WordPress, Joomla, Laravel and static hosting have different compatibility and deployment considerations.

Read the website migration checklist.

Discuss your website migration

Share the site URL, current host and any store, membership, email or integration requirements. Do not send credentials in the inquiry form.

Ask about your site