Migration Scenarios

The actual method depends on the source host, application, database, access available, and current licensing. These are assessment patterns, not promises that every workload can be transferred unchanged.

Control-Panel Hosting

Examples include cPanel or Plesk environments. A migration may use control-panel exports, file transfer, and database dumps. Confirm PHP or runtime versions, cron jobs, mailboxes, DNS zones, certificates, redirects, and any provider-specific features before assuming compatibility.

Managed Application Platforms

Examples include deployment platforms connected to a Git repository. Gather the repository, build settings, environment variables, domains, redirects, serverless or edge functions, databases, storage, scheduled jobs, and provider integrations. Some proprietary platform features must be replaced or cannot be reproduced directly.

File-Transfer-Only Hosting

FTP or SFTP access may provide website files but not databases, DNS, mail, scheduled jobs, configuration, or hidden provider services. Additional access or cooperation from the former provider may be required.

Static Sites

Static HTML, CSS, and JavaScript can often be deployed with a simple web server, but forms, search, redirects, analytics, build pipelines, and external APIs still need to be identified and tested.

Custom Applications

Custom runtimes require source code or deployable artifacts, dependency information, environment configuration, database and storage details, network requirements, and a documented start or build process. Unsupported or end-of-life software may require remediation before it can be hosted.

E-commerce and Frequently Changing Data

Orders, customers, inventory, subscriptions, accounts, or other changing records may require a final synchronization or temporary write restriction. The migration plan must identify the system of record, cutover rules, validation owner, and the risk of data created during the transition.

Migration fees and timing are quoted after the source environment and acceptance criteria are understood. See the Migration Checklist.