To mark progress: use the small status drop-down under each site name (migrated or later turns the row green). To decide a site: pick from the decision drop-down in its row (kinsta / own-server / drop / elsewhere). It saves instantly to sites.csv. Tick several rows to set them at once. Click a site name for the full picture.
Decision: kinsta own-server drop (3-month notice) elsewhere (client moves) already-gone / skip undecided. Edits save straight to sites.csv (a backup is kept in data/backups/ and every change is logged in data/changelog.csv). Click a site name for everything known about it.
One row per paying client from the 2025 FreshBooks export. accounts = the cPanel account(s) that client pays for (space-separated). Fix the ones marked auto-low / unmatched: editing accounts marks the match confirmed (so rebuilds keep your answer) and refreshes the Sites tab immediately. Unassigned accounts are listed below the table.
for someone who pays you but isn't in the 2025 billing export
cPanel accounts with no paying client
Kinsta hand-off
Writes export/kinsta-handoff.csv (rows with decision = kinsta, migration columns + credentials, no billing data), export/kinsta-handoff.md (narrative for the migration team), export/root-tasks.csv (for the root-server Claude) and export/dns-zones-to-recreate.txt.
Files
Root-server Claude
Give the root Claude ROOT-CLAUDE-BRIEF.md plus export/root-tasks.csv. It creates fresh migration credentials and writes them to raw/from-root/credentials.csv. Then merge them here:
cd /Users/canton/websites/sandbox/kinsta python3 build/build_sites_csv.py --merge-root raw/from-root/credentials.csv
Only empty credential cells are filled; add --overwrite to replace existing ones.
Rebuilding
Generated columns (sizes, DNS, mail, suggestions, client) are recomputed from raw/ by build/build_sites_csv.py. Your columns (decision, credentials, status, notes…) are carried across by site_id. Run after you fix client ↔ account matches on the Clients tab.
Source reports
- Sizing report viewer (every account, site, DB; 2026-10-08) · markdown · DB consolidation addendum
- Mail & DNS audit summary (2026-10-14) · mail-domains.csv · dns-zones.csv · non-default DNS records · zones.tgz
- Anonymised billing report · confidential billing profile · expenses-for-2025.csv
- README.md · ROOT-CLAUDE-BRIEF.md · changelog.csv
How to work this
- Who pays: either click a site name and pick the client in the drawer, or edit accounts on the Clients tab. Both mark the match confirmed and refresh the Sites tab right away.
- Sites tab, Decide columns: set a decision per site (or Accept all suggestions and then override). Use the Money columns to see what each client pays versus the Kinsta cost.
- Attention filter shows what is still missing for the sites you are moving.
- Export tab: generate root-tasks.csv, hand it to the root Claude, merge credentials back, then generate the Kinsta hand-off.
- Progress columns: track each site from creds-ready → migrated → dns-cut-over → verified → decommissioned.
Big facts from the audits
- 176 websites in 77 cPanel accounts (95 WordPress). 58 are empty placeholders, 31 old/staging copies.
- Everything live is about 291 GiB; mail (28 GiB) does not move.
- 109 DNS zones are served only by ns1/ns2.w3code.com (this box, no secondary). They must exist at the new DNS host before cutover. ns1/ns2 glue lives in the w3code.com zone at name-services.com (eNom).
- Nobody reads mail with a client on this server. 3 Gmail-fetched mailboxes (keithalanmitchell.com, moeserlane.com), 18 forward-only domains, myfutureself.com's inbound mail pipe, and 75 sites sending PHP mail without an SMTP plugin.
- 10 WordPress sites use a second non-WP database (custom CMS / MachForm / SlideShowPro) that needs merging before Kinsta.