Migrating from manual booking to managed infrastructure: a 48-hour roadmap
Why the migration feels risky (and isn't)
Every agency owner who has been running manual booking operations for more than a year has the same quiet fear: the stack works. It's flaky, it burns out staff, it loses slots — but it's running, and customers are getting visas. Changing anything while clients are in-flight feels like open-heart surgery on a patient who is technically still breathing.
The fear is reasonable and also mostly wrong. Migration is not a big-bang cutover. It's a corridor-by-corridor hand-off that leaves existing in-flight applications exactly where they were, and only sends new applications through the new system. At the end of 48 hours your agency is running dual-mode; at the end of four weeks the old mode is retired naturally as in-flight bookings complete.
This guide assumes a typical mid-sized agency: 150–300 applications a month, 2–5 operations staff, two or three portals in play (typically VFS + one other), and zero engineering headcount. If that's you, you can run this plan without writing a line of code.
The 48-hour plan, hour by hour
Week 2–4: add corridors, retire manual
With one corridor live, adding more is mechanical. Week 2 is your second corridor. Week 3 is your third. Week 4 is whatever tail corridors remain. By the end of week 4, all new applications flow through Opaige regardless of destination, and the old manual process naturally retires as its last in-flight application completes.
The one unavoidable step: retiring the shared-password spreadsheet and the WhatsApp "slot alerts" group. These are the emotional artefacts of the old model, and keeping them around confuses the team. Delete them publicly, announce the deletion, do not re-create them.
What to measure — and what to stop measuring
Old metrics stop being useful immediately — they were coping metrics, things you measured because you couldn't solve the underlying problem. The new metrics are operating metrics: they tell you how the system performs, not how hard the team is working around its failures.
Measure weekly for the first month, monthly after. Then you run the business on real numbers instead of inbox anxiety.