From the first decision to reliable operation.

List applications, users, normal load and peaks. Separate production, staging and development.

Choose a service, then specify CPU, RAM, storage, networking and backup. Add desired operational options.

Review the cart before requesting a quote. Confirm availability, final price, location, licences and responsibilities with your contact.

Start with memory use, data volume and process count. Allow headroom for updates and peaks.

Prepare SSH access, updates and firewall rules before publicly exposing the application.

Choose extra IPv4 addresses, backup and on-call coverage if needed. Validate recovery and measure load after startup.

Compare processors, cores, RAM and disks by family. Match the workload: compute, databases or storage.

Check compatible disk, RAM and bandwidth options. RAID improves tolerance to disk failures; it does not replace backup.

Specify operating system, licences, IPs and private networking. Confirm available hardware, installation and interventions before activation.

Build a non-overlapping address plan for applications, databases, administration and backup.

For each flow, define source, destination, port, protocol and purpose. Restrict administrative interfaces to intended access.

Verify private-network compatibility, public bandwidth, IPv4 and routing. The map provides geographic context, not evidence of customer traffic.

Inventory files, databases, configuration and secrets needed for recovery. Identify what requires a consistent backup.

Set RPO/RTO objectives, frequency and retention with business owners. Plan capacity and storage location.

Restore in an isolated environment, verify data and application startup, then record results and corrections.

Identify included servers, applications, APIs, networks and accounts. State exclusions and sensitive environments.

Define written authorisation, testing window, emergency contacts and stop conditions before any intervention.

Plan reporting, remediation priorities and retesting. Selected modules define the quote; they do not launch tests.

List countries, currencies, volume, methods and flows: one-off payment, subscription, refund or marketplace.

Prepare idempotent event handling, signature verification, retry recovery and reconciliation with orders.

Confirm APIs, acquirer, merchant onboarding and applicable fees. Reference material and sandbox screens are distinct from an activated production API.

Inventory data, dependencies, certificates, DNS and integrations. Prepare a usable backup before changes.

Test the destination, define a cutover window and rollback criteria. Assign an owner to every check.

After cutover, check access, data consistency, scheduled jobs, logs and backups before closing the migration.