Change Hosts Without Losing a Day of Business

Yes. We copy files, databases and email, stand the site up on the new server, verify it works before any DNS change, and only then switch over. If the old host restricts access, we tell you what that means for the migration before we start.

We build the site on the new server first and test it there, then lower the DNS TTL in advance and schedule the switch for the small hours of Bangladesh Standard Time when your traffic is lowest. Email is planned separately since it is where most migrations actually go wrong.

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.

Yes. We assess both ends, transfer the files and database, sort out URLs and permissions, configure the web stack, plan DNS and SSL, and test the visitor and administrator journeys that matter to you.

We plan around order and customer data that keeps changing, using an agreed maintenance window, a data freeze or a final sync. Which one suits depends on how busy the store is, what database access exists, the tooling available and how much risk is acceptable. A controlled test transaction should always follow the cutover.

Yes. Account compatibility, versions, packages, databases, email, DNS, SSL, dedicated IPs, quotas, the transfer tooling, third-party plugins and capacity at the destination all get reviewed before the migration window opens.

Yes. The first question is whether the workload should be transferred as-is, replicated, rebuilt cleanly or upgraded on the way. Operating system, architecture, services, users, data, networking, firewall, jobs, storage and provider-specific features all shape that plan.

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.

Email moves as well when it is in scope. Mailboxes, mail data, MX, SPF, DKIM, DMARC, forwarding rules, service records, verification records and any third-party destination get inventoried before DNS or mail routing is touched.

Yes. A WHMCS move needs the version, PHP, database, licence, attachments, cron, templates, hooks, modules, email, callbacks and provisioning dependencies mapped and then tested. We prefer to validate on staging first where that is practical.

Not by default. The source is normally kept as a recovery point for an agreed period, as long as access and billing allow it. Anything destructive needs your separate, explicit approval after acceptance and backup decisions have been made.

The current and destination providers, the platforms, the domains, rough site, database and mailbox sizes, how many accounts, the timing you need, what access you can give, the workflows the business cannot afford to break, and any version or licence constraint you know of.

Yes. We handle authorised migrations between compatible third-party providers, as well as moves into HostAccent. Provider restrictions, missing access, unsupported software or export limits can change which method is available.