KINTO migrated a hosting agency’s sites in waves: dozens of domains reconciled and classified, every active site on the new platform, and publishing time cut from nearly an hour to a few minutes.
Problem
An agency’s client sites were spread and duplicated across legacy infrastructure. Nobody had a complete domain inventory or knew which version of each site was the live one.
Signals
- Market: Market demand was not measured in this engagement: the problem was infrastructure and continuity.
- Business: Continuity risk for the agency and its clients, with a service cost that had to stay low.
- User experience: With sites duplicated, it was unclear which version visitors were seeing.
- Support: Each client’s email had to be preserved at every step.
How we understood it
- Automatic inventory and classification of every domain: dynamic, static, empty, orphaned.
- DNS and registrar reconciliation.
What we built and why
- Wave-by-wave migration to a new server plus static hosting: dynamic sites as full WordPress; static ones exported, with a private WordPress for editing and a “one-click” publisher.
- Central panel for every WordPress site, onboarding for new sites and external forms.
- Backups and a runbook for operating the new platform.
Why this way: Dynamic sites run as full WordPress and static ones are exported: no server where none is needed, and editing stays possible through the private WordPress.
Transformation
-
Every active site on the new platform after reconciling dozens of domains; every WordPress site under one central panel.
-
Publishing time cut from nearly an hour to a few minutes.
-
No active site remains on the original servers.
-
domains reconciled and classified: dozens (all of them) (measured)
-
active sites still on the original servers: none (measured)
-
time to publish changes: from nearly an hour to minutes (measured)
What we don’t know yet
- Commercial impact on the agency: no evidence.
