Planned website, hosting & server migrations

Move the Workload— Not the Old Failure

Migrate WordPress, cPanel accounts, websites, databases, email, VPS workloads, ecommerce stores, or WHMCS systems with dependencies mapped, a controlled cutover, and post-move validation.

Included when you move to eligible HostAccent hostingCustomers moving an eligible website or hosting account to a HostAccent hosting plan pay no separate migration charge. Moves between third-party providers, or to infrastructure not hosted by HostAccent, are scoped and quoted as paid migration projects.
Check Migration EligibilitySee the investigation process
  • Eligible HostAccent inbound migration included
  • Independent migrations quoted before work
  • Cutover and rollback criteria defined
  • Business workflows tested after move

Tell us the source and destination providers, whether the destination is HostAccent, the platforms, approximate data size, domains, email usage, required timing, access available, and any known compatibility or downtime constraints.

evidence-console controlled scope
$ plan migration --inventory-to-cutover
01
InventorySites, data, DNS, email, jobs, integrations
02
CompatibilityOS, PHP, database, panel, licences
03
Transfer and syncFiles, databases, mail, configuration
04
Cutover and verifyDNS, SSL, workflows, rollback decision
MethodEvidence first
ChangesApproved only
OutputVerified report
Website migrationWordPress, ecommerce, and custom sites
Server migrationVPS, workloads, services, and accounts
Data & emailDatabases, mailboxes, queues, and files
DNS & cutoverTraffic, SSL, validation, and rollback
Migration change discipline

A copied website is not yet a completed migration.

Production workloads depend on DNS, SSL, email, databases, scheduled jobs, storage, permissions, APIs, webhooks, licences, and provider-specific settings. We map those dependencies before traffic is switched.

Production remains yoursYou approve the migration scope and cutover. Included and billable work is identified before access is used, source data is preserved until validation, and destructive cleanup is outside the migration unless separately approved.
01

Inventory before transfer

Domains, sites, databases, mailboxes, DNS records, certificates, cron jobs, integrations, IP dependencies, and storage are recorded first.

02

Check destination compatibility

Operating system, control panel, PHP, database, web server, extensions, licences, limits, and architecture are compared.

03

Separate bulk copy and final sync

Where the workload permits, large data moves first and changed data is synchronised closer to cutover.

04

Define the cutover decision

DNS TTL, maintenance needs, data freeze, stakeholders, monitoring, validation checks, and rollback thresholds are agreed.

05

Test the business, not just the homepage

Login, forms, checkout, payments, cron, email, APIs, admin tasks, redirects, and SSL are validated as relevant.

Migration services

Move websites, accounts, services, and business workflows

We design the migration around the workload’s actual dependencies and data-change pattern rather than treating every project as a one-click transfer.

01

WordPress and website migration

Move sites between providers, servers, control panels, domains, or environments while preserving application behaviour.

  • WordPress and WooCommerce
  • Files and database transfer
  • Serialized URL replacement
  • Permissions and web-server rules
  • Staging and post-move testing
02

cPanel and server migration

Transfer accounts or rebuild workloads on a compatible destination with service and account boundaries mapped.

  • cPanel account transfers
  • VPS and dedicated workloads
  • Web, PHP, and database services
  • Users, permissions, and scheduled jobs
  • Storage and resource planning
03

Email, DNS and certificates

Protect the quiet dependencies most likely to be missed when the website itself appears online.

  • Mailboxes and mail data
  • MX, SPF, DKIM, and DMARC
  • Complete DNS-zone inventory
  • SSL and service certificates
  • TTL and propagation planning
04

Ecommerce, WHMCS and integrations

Plan around stateful systems where orders, invoices, callbacks, queues, and automation continue changing.

  • Store orders and customer data
  • Payment callback endpoints
  • WHMCS database and attachments
  • Cron, queues, and webhooks
  • API and licence dependencies
Cutover safety

Define what success looks like—and when traffic should return to the source.

A practical rollback option depends on data direction, DNS, transaction activity, source availability, and the changes permitted after cutover. We document the decision points rather than promising impossible zero risk.

Controlled troubleshooting

Inventory, transfer, cut over, and validate

We turn the migration into a controlled sequence with ownership, evidence, dependency checks, data synchronisation, and a clear acceptance point.

  1. 01

    Describe the requirement

    Tell us what is moving, where from and to, the size and technology involved, and any deadline or downtime constraint. You do not need to plan the migration requirement yourself.

  2. 02

    Confirm the investigation scope

    We agree the inventory—sites, databases, mailboxes, DNS zones, certificates, cron jobs—and the access needed on both the source and the destination.

  3. 03

    Trace the dependencies

    We check PHP and MySQL versions on both ends, mail routing, hard-coded paths and URLs, and TTL values, so the cutover does not surface surprises after DNS moves.

  4. 04

    Review findings and proposal

    You receive the migration plan: sequence, expected downtime window, rollback position, DNS timing, and a quote where the scope goes beyond a standard move.

  5. 05

    Approve, migrate, and verify

    After approval we copy, sync deltas, cut over, and verify the live site, email flow, SSL, and scheduled jobs on the new host before the source is retired.

Clear approval boundary. Investigation and repair are separated where applicable. Broader changes, added scope, and material risk are explained before you authorise the work.

Start a scoped request
Anonymised migration case pattern

The website moved successfully—but checkout callbacks still used the old server

Pages and products worked on the destination, yet paid orders remained pending after DNS cutover.

Root causeThe payment gateway callback used a hostname and firewall path omitted from the migration inventory, so transactions continued reaching the retired origin.
  • Gateway, webhook, cron, email, and DNS dependencies were mapped.
  • The callback endpoint and firewall path were corrected on the destination.
  • A controlled transaction verified payment-to-order state.
  • The old server remained available until transaction evidence matched.
cutover-validation.logdiagnostic record

storefrontdestination healthy

paymentcallback reached old origin

inventorysecondary hostname missing

repairDNS and firewall path updated

testcontrolled order completed

acceptworkflows verified; source retained

Website and transaction path migratedSource retired only after workflow acceptance
Engagement options

Included HostAccent migration or paid independent project

The destination determines the commercial path. Eligible moves into HostAccent hosting are included; migrations that do not use HostAccent hosting are scoped and quoted before work begins.

Included for eligible hosting

Migration Into HostAccent

For a website or compatible hosting account moving from another provider to an eligible HostAccent hosting plan, with no separate migration charge.

Best for
  • Source and destination assessment
  • Data and configuration transfer
  • DNS and SSL cutover
  • Application and email checks
Check included migration eligibility
Quoted professional service

Independent & Third-Party Migration

For migrations between third-party providers, to customer-owned infrastructure, or for complex multi-system projects that do not use HostAccent hosting.

Best for
  • Workload and compatibility inventory
  • Written scope and migration quote
  • Cutover and rollback criteria
  • Post-move operational validation
Request an independent migration quote
Why Hostaccent

Migration quality depends on infrastructure and application context

Hostaccent understands Linux, cPanel, WordPress, ecommerce, WHMCS, DNS, email, SSL, Cloudflare, databases, and hosting operations. That lets us plan for the dependencies that a file-copy tool cannot see.

Application-and-infrastructure inventory
Stateful data and transaction awareness
DNS, mail, SSL, and cutover experience
Evidence-based acceptance and rollback planning
Common migration environmentsCommon platforms and layers
WordPressWooCommercecPanel / WHMWHMCSLinux VPSDedicated ServersApacheNginxPHP-FPMMySQL / MariaDBDNSEmailSSL/TLSCloudflare

Included HostAccent migration covers the agreed compatible inbound move; independent destinations and work outside that scope are quoted separately. Downtime, transfer time, rollback feasibility, and compatibility depend on workload size, data-change rate, source and destination access, DNS control, provider limits, licences, network speed, and application architecture.

The Hostaccent support ecosystem

One technical partner. Ten specialist paths.

A migration is rarely just a file copy: databases, DNS records, mail routing, SSL certificates, and cron jobs all have to land correctly before the old host is switched off. Explore every specialist service without losing the wider production context.

Not sure which service matches?Tell us what needs to move and by when—we will plan the cutover around it.
Request technical support
Questions before access

Scope, credentials, approval, and practical expectations

These answers explain how the investigation works before you share access or approve a production change.

Ask about your environment
01When is migration free, and when is it a paid service?

If you have purchased an eligible HostAccent hosting plan and are moving a compatible website or hosting account from another provider into HostAccent, the agreed migration is included with no separate migration charge. A migration between two third-party providers, to customer-owned infrastructure, or to any destination that does not use HostAccent hosting is a paid professional service. We confirm eligibility, included scope, and any quote before work begins.

02Can you migrate a WordPress website to another host?

Yes. We can assess the source and destination, transfer files and database, handle URLs and permissions, configure the web stack, plan DNS and SSL, and test the relevant visitor and administrator workflows.

03Can you migrate WooCommerce without losing orders?

We plan around changing order and customer data using an agreed maintenance, data-freeze, or final-sync approach. The appropriate method depends on store activity, database access, tooling, and acceptable risk. A controlled transaction should be tested after cutover.

04Can you migrate cPanel accounts or a full cPanel server?

Yes. We can review account compatibility, versions, packages, databases, email, DNS, SSL, dedicated IPs, quotas, transfer tools, third-party plugins, and destination capacity before the migration window.

05Can you migrate a VPS or dedicated server?

Yes. We first determine whether the workload should be transferred, replicated, rebuilt, or upgraded. Operating system, architecture, services, users, data, networking, firewall, jobs, storage, and provider features all affect the plan.

06Will there be downtime during a migration to HostAccent?

For eligible migrations into HostAccent, our standard cutover is planned to avoid visitor-visible downtime: we prepare and test the destination before DNS changes and use a final synchronisation where the application permits it. Source access, DNS control, live orders or other stateful writes, email, provider restrictions, and software compatibility can still require a short maintenance window. Any expected interruption is explained before the cutover; we do not apply an unconditional zero-downtime guarantee to every workload.

07Will you migrate email and DNS as well?

Yes, when included in scope. We inventory mailboxes, mail data, MX, SPF, DKIM, DMARC, forwarding, service records, verification records, and third-party destinations before changing DNS or mail routing.

08Can you migrate WHMCS?

Yes. WHMCS migrations require version, PHP, database, licence, attachments, cron, templates, hooks, modules, email, callback, and provisioning dependencies to be mapped and tested. A staging validation is preferred where practical.

09Do you delete the old server after migration?

Not as part of the default cutover. The source is normally retained as a recovery point for an agreed period where access and billing permit. Destructive cleanup requires separate, explicit approval after acceptance and backup decisions.

10What information is needed for a migration quote?

Provide source and destination providers, platforms, domains, approximate site, database, and mailbox sizes, number of accounts, required timing, access available, business-critical workflows, and known version or licence constraints.

11Can you migrate services hosted outside Hostaccent?

Yes. We support authorised migrations between compatible third-party providers and Hostaccent or between third-party environments. Provider restrictions, missing access, unsupported software, or export limitations may change the available method.

Send the symptoms, not a guess

Planning a website, cPanel, ecommerce, WHMCS, or server migration?

Send the source, destination, workload, timing, and business constraints. We will confirm whether the move is included with eligible HostAccent hosting or provide a written quote for an independent migration before work begins.

Check Migration EligibilityRequest an Independent Migration QuoteNo broader changes before scope and approval