TitanBeam · hosting migrations
A new home.
For everything
you’ve built.
Your site, your data, your mail. Start with the number of sites you’re bringing. We’ll review the details with you before the move.
What will you need from me?How many sites are coming?
Start with a site count. We’ll confirm the scope and price before any work begins.
Next: choose your hosting. Your site count comes with you. No payment or transfer starts here.
Your move,
one step at a time.
Use these stages to scope the move. The source host, destination, access and application behavior determine the exact work.
- 01
Inventory
List the sites, databases, mailboxes, jobs and domains that need to move.
- 02
Stage
Agree how a destination copy will be prepared and how the source will keep serving.
- 03
Verify
Plan checks for the site, data, mail, redirects, TLS and scheduled work.
- 04
Agree the cutover
Set the DNS change, final data sync, acceptance checks and recovery path.
What to bring to the conversation.+
Names, counts, sizes and versions are enough to start. Credentials and private account information belong in an agreed secure channel.
| Part of the account | Record before the move | Check at the destination |
|---|---|---|
| Sites & applications | Domains, aliases, software versions, extensions, files and upload sizes. | Key pages, sign-in, forms, redirects and application functions. |
| Databases | Engine/version, sizes, connections and how frequently data changes. | Data completeness, application connections and the final sync plan. |
| Provider, mailbox count, aliases, forwarding and stored mail. | Sending, receiving, authentication records and client settings. | |
| Scheduled work | Cron jobs, queues, workers, external calls and timing requirements. | Jobs run in the right place without duplicate processing. |
| DNS & TLS | Registrar, DNS provider, records, TTLs and certificate requirements. | The destination addresses, certificates and cutover authority. |
| Recovery & acceptance | Source retention, backup access, acceptable interruption and who signs off. | The recovery path and the conditions for considering the move complete. |
Know the scope.
Then agree the move.
The published migration rate is $20 per site. Use the estimate to frame your request; it is not a quote for every source account or dependency.
Mail volume, inaccessible exports, unusual software, large data sets and application repair can change what work is needed. Confirm what is included, what needs separate work and the final price before proceeding.
A transfer does not automatically include redesign, new application features or fixing existing code problems.
The public change
Decide what cutover and recovery will mean.
Agree who changes DNS, when changing data will be synchronized, what tests must pass and who can authorize the move. Stores, forums and mail may need a specific plan for activity during the transition.
Before canceling the old host, confirm how long the source should remain available and what you would do if a destination check fails. Source preservation and recovery depend on the access and retention arrangements agreed for the move.
No fixed migration sequence can promise zero downtime for every application.
Common migration questions
Can I move from a different control panel?
Describe the current host and panel, the applications and the export or access options you have. Compatibility must be checked; the destination does not need to copy the source’s product name or plan size.
Can my email stay with its current provider?
Include that preference in the inventory. Website hosting and mail can have separate destinations, so the DNS plan must preserve the intended mail routing and authentication records.
When should I cancel my old hosting?
Wait until the cutover and acceptance plan has been agreed and completed, including the required retention or recovery window. Do not assume the old account is no longer needed because files have been copied.
How do I start?
Choose a destination plan and include the number of sites and migration details in a hosting request, or ask Dart about a compatibility question first. The public request reviews the move; it does not start a transfer.