Opening an Office in Thailand: A Practical IT Readiness Checklist
A practical IT checklist for HQ and regional leads opening an office in Thailand: owners, network, identity, devices, integrations, restores and handover.
By UNIXDEV Team · 5 min read
Published
A new office in Thailand usually opens with a lease, a hiring plan and a target date. The IT risk sits in the gaps: who decides, who owns each system and who staff call on the first morning.
This checklist covers IT operations practice for HQ, regional IT and operations leads. Legal, data-protection and other regulatory obligations should be confirmed with the company's legal advisers.
Start with decisions and owners
Before buying anything, agree who approves IT spending in Thailand, who signs vendor contracts and which HQ standards apply. Then list every system the office will use and give each one an owner, accountable for access, configuration and changes.
Some systems stay with HQ IT; others, such as the office network, may be owned locally. Write the split down. An unclear HQ and local boundary can cause simple requests to stall.
Prepare each area
Internet and network
Order internet lines early. Check which providers already serve the building, whether riser and cabling access is available, and what landlord approval installation needs. Decide whether the office needs a second line from a different provider; redundancy is a business decision, not a default. Plan Wi-Fi for the real floor layout and keep guest devices on a separate network.
Identity and MFA
Join the new office to the HQ identity system rather than creating separate local accounts. Require multi-factor authentication from the first sign-in and keep the list of local administrators short and recorded. Agree who can reset MFA or unlock an account during Thai office hours, and where emergency (break-glass) administrator access is held.
Endpoints
Decide whether laptops are bought locally or shipped from HQ, comparing lead time and warranty support. Either way, enrol devices in the company's device management before handing them out, so the company's encryption, update and remote-wipe policies apply from day one.
Collaboration tools
Email, chat, file sharing and calendars should be ready before the first employee arrives, with the Thailand team in the directory and calendars set to the correct time zone. Thailand is UTC+7 with no daylight saving, so if HQ changes its clocks, the overlap shifts by an hour twice a year; recheck recurring meeting slots when it does.
Software integration
Local accounting, HR, e-invoicing or partner systems may need to exchange data with HQ systems such as the ERP or CRM. List what moves, in which direction and how often. Agree who builds and maintains each connection, and how a failed transfer will be noticed.
Backup and restore
A scheduled backup job does not prove data can be recovered. For every system the office relies on, including cloud and SaaS services, name who owns the restore check, run a restore test and record what was restored, where, by whom and how long it took.
Vendor coordination
Internet providers, the hardware supplier, the landlord or building management and any local IT partner belong on one list of contacts, contracts, support hours and escalation routes that HQ and the local lead can both find.
Support and escalation
Staff need to know who to contact on day one and how to raise a request. Local office hours and HQ support hours may not overlap, so define which issues the local team or partner handles directly and which wait for, or escalate to, HQ. For what follows, see IT support between HQ and Thailand after go-live.
Handover
Whoever sets up the office should hand documentation, network diagrams and runbooks to the system owners named at the start. Administrator credentials must belong to the company, stored in a company-controlled password manager or vault, not in a contractor's personal account.
Office IT readiness checklist
Owners are suggested roles to assign.
| Area | What to prepare | Owner | Evidence it is ready |
|---|---|---|---|
| Decisions | Approvers, budget holder, system owner list | HQ IT and Thailand lead | Signed-off owner list for every system |
| Internet | Primary line; decision on a second line | Thailand lead | Line installed and tested; redundancy decision recorded |
| Network and Wi-Fi | Coverage plan, guest network separation | Thailand lead or local partner | Coverage checked on site; guest network cannot reach internal systems |
| Identity and MFA | Accounts, MFA, admin roles, reset process | HQ IT | Test user signs in with MFA; admin list reviewed |
| Endpoints | Purchase route, device enrolment | HQ IT | Every device shows as managed and encrypted |
| Collaboration | Email, chat, files, calendars, time zones | HQ IT | Test meeting scheduled across both time zones; file shared with HQ |
| Integration | Data flows between local systems and HQ ERP/CRM | System owners | Test transfer succeeds; failure alert reaches an owner |
| Backup and restore | Backup scope, restore procedure | System owners | Dated restore test record |
| Vendors | Contacts, contracts, support hours | Thailand lead | One shared vendor list, reviewed |
| Support | Request channel, escalation path, hours | HQ IT and local partner | Staff guide issued; test request resolved |
| Handover | Documentation, runbooks, credentials | Setup lead (HQ IT or local partner) | Credentials held by the company; runbooks reviewed by system owners |
A suggested preparation order
This order is a starting point that adapts to the office size, the building and HQ standards. It is not a fixed timeline or a guarantee of any duration.
- Decide: name approvers and system owners; agree the HQ and local boundary.
- Order long-lead items: internet lines and laptops, once the purchase route is chosen.
- Build the foundations: identity, MFA, device management and the office network.
- Connect the work: collaboration tools and any integrations with HQ systems.
- Prove recovery and support: restore tests, the vendor list and a test support request.
- Hand over: documentation, runbooks and credential ownership, before staff start.
Getting a second view
UNIXDEV can help review the plan, particularly the cloud setup, how local collaboration tools connect with HQ identity, and any integration between local systems and HQ.
Discuss your Thailand project
Tell us where your team is based in Thailand, your timing, the systems you use today and the help you need. You do not need a finished specification.
Discuss your Thailand project →