Purchase guide / portfolio migration

Before you commit
to a new host.

A checklist for the person responsible for the move. This is a proposed procedure, not a record of migrations we have performed.

1. Inventory the portfolio

For each site, collect disk use, monthly server and CDN bandwidth, database size, PHP version, scheduled tasks, email dependencies and plugin requirements. Keep peak months alongside averages. Distinguish active production sites from staging copies.

2. Get a written fit confirmation

Use the calculator with aggregate resources, then confirm per-site limits, peak concurrency, storage overages, backup retention and staging allowances with the vendor. Pricing alone does not establish fitness.

3. Budget the human work

Include audit, staging review, forms, checkout, login, redirects, DNS changes and a rollback rehearsal. Enter your own hours and hourly value; we have not measured migration time.

4. Prove one representative site first

1. Capture a backup and confirm a restore path.
2. Test a temporary copy without changing production DNS.
3. Verify forms, payments, search, cron jobs and outbound email.
4. Record results and unresolved incompatibilities.
5. Agree on a maintenance window, owner and rollback trigger before moving the rest.

5. Separate ownership from recommendations

The agency buying hosting for its own portfolio and a publisher referring a new buyer are different relationships. Check affiliate eligibility separately. Do not assume your own purchase or a managed client account earns a commission.

6. Recheck the invoice

Confirm billing cycle, taxes, add-ons, promotion expiry, renewal price and cancellation terms at checkout. The tool uses standard monthly rates and applies no introductory promotion.

Official plan data used

• Kinsta: Official plan source ↗
• Rocket.net: Official plan source ↗