Client Stories
Specific accounts of migration advisory, planning workshops, and readiness work with teams in Thailand.
Voices from recent work
The readiness assessment stopped us from forcing a March cutover when our payment service still had an undocumented batch job. We moved two quieter systems first and used the report in the board pack.
Siriporn L. — CTO, hospitality group, Phuket
Workshop days were dense. We spent the first morning arguing about VPC layout, which was uncomfortable, but the decision log kept us from reopening the same fight three weeks later.
Anawat P. — lead architect, fintech subsidiary, Bangkok
They stayed with our weekend cutover until the last DNS flip. The runbook they left behind is still taped to the ops board. I would have preferred clearer Thai-language summaries for our NOC; we translated the hot sections ourselves.
Nattapong K. — infrastructure lead, regional logistics firm
We hired them after a vendor migration stalled at 40%. Amberpoint did not restart the whole programme; they re-sequenced the remaining waves and named which systems should stay on-prem for another year.
Helen M. — programme manager, manufacturing JV
Extended story: regional logistics cutover
A logistics operator with depots across southern Thailand needed to leave an ageing colocation cage before the lease expired. The estate mixed custom fleet software, a shared database, and vendor SaaS connectors. System Amberpoint ran a four-week discovery, then an eight-week migration advisory.
Constraints were concrete: no downtime during Friday night dispatch peaks, limited VPN capacity to the new region, and two engineers on parental leave during the original target weekend. The wave plan moved reporting first, then the less-coupled services, and parked the shared database until a read-replica strategy was proven in rehearsal.
On cutover night, advisory counsel sat with the ops lead on video while local staff ran the checklist. One rollback was exercised for a messaging worker; the rest of the wave stayed. The lease exit completed on schedule with a shorter list of residual risks than the first plan had claimed.
Extended story: planning before procurement
A Bangkok product company asked for an infrastructure planning workshop before signing a multi-year cloud commit. Three half-day sessions produced a landing-zone sketch, identity boundary decisions, and a capacity model tied to their seasonal traffic. Procurement used the one-page summary to negotiate reserved capacity against a plan rather than a blank slide. No migration had started; the workshop’s job was to prevent an expensive default.