For most small businesses, the sensible order is: shared documents and email first, then everyday business applications such as sales, accounting or inventory, and only later anything custom. Moving to the cloud removes the burden of maintaining your own server, but it does not remove your responsibility for accounts, permissions and backups. Mistakes like deleting a folder or a hacked password are still yours to prevent and fix.
What "the cloud" actually changes for a small company
In plain terms, cloud computing means renting computing power, storage or ready-made software from a provider and using it over the internet, instead of owning and running the machines yourself. For a small company the practical change is that the old office server in the corner, with its noisy fan and its one person who knows the password, is no longer the heart of the business.
That change brings real benefits. Staff can open the same files from the office, the warehouse or home. Software updates arrive without anyone staying late. Hardware failures in the provider's data centre are their problem, and well-known providers keep several copies across machines so a single broken disk rarely matters.
What does not change is that your business still decides who can see what. A shared folder set to "anyone with the link" is just as exposed in the cloud as a USB stick left on a café table. An employee who leaves but keeps access can still download your customer list. The provider runs the building; you still hold the keys to your own rooms.
This split is often called the shared responsibility model. The provider secures the infrastructure; the customer secures accounts, data and settings. Most cloud incidents at small companies happen on the customer side.
Who is responsible for what after moving to the cloud
The exact split depends on the service type, but this is the usual pattern for ready-made business software and storage.
| Area | Provider usually handles | Your company still handles |
|---|---|---|
| Physical servers and data centres | Power, cooling, hardware replacement | Nothing |
| Software updates of the service | Patches and new versions | Testing changes that affect your workflows |
| User accounts | The login system itself | Who gets an account, strong passwords, two-factor authentication |
| Permissions and sharing | The settings available | Choosing who sees which folder or record |
| Accidental deletion | Sometimes a short recovery window | Noticing it, restoring it, keeping independent backups |
| Departing employees | Nothing | Removing access the same day |
| Legal duties about personal data | Their own obligations as a processor | Your obligations as the business holding the data |
If you are unsure about legal duties for customer data in Vietnam, check the current regulations or ask a lawyer; this article only covers the technical side.
A sensible migration order
Each step should be stable for a few weeks before the next one starts.
- List what you have. Files on each computer, the shared drive, email accounts, the accounting software, any spreadsheets that run the business. You cannot move what you have not found.
- Move email and calendars first. They are standard, well supported and give everyone an early, low-risk taste of the new way of working.
- Move shared documents next. Clean up before moving: delete duplicates, agree on a folder structure, and set permissions by team instead of by person.
- Turn on two-factor authentication for everyone. Do it before the important data arrives, not after the first incident.
- Move one business application at a time. Sales or accounting, then inventory, and so on. Run old and new side by side for a short overlap and compare results.
- Set up backups that do not depend on one provider. Export key data regularly to a separate service or a drive kept offline.
- Retire the old server deliberately. Keep a final archive copy, wipe the disks properly, and write down where everything now lives.
Practical traps that catch small companies
Thinking sync is backup. File sync copies deletions too. If a folder is deleted or encrypted by ransomware on one laptop, the change can spread to every synced device.
Personal accounts for company data. Files stored in an employee's personal cloud account leave with that employee.
One admin account shared by several people. Nobody knows who changed what, and the password ends up written on a sticky note.
"Anyone with the link" sharing. Convenient for sending one file, dangerous as a default. Links get forwarded far beyond their intended audience.
Forgetting the internet connection. If the whole business now depends on the cloud, one fibre line is a single point of failure. A mobile data backup is cheap insurance.
Uploading everything without cleaning. Years of duplicate and outdated files make search slow and permissions confusing from day one.
Ignoring storage growth. Photos, videos and scanned documents fill paid storage faster than expected. Agree on what is worth keeping.
No offboarding checklist. When someone leaves, accounts, shared links and devices must all be handled the same day, every time.
Keeping the business running when the internet goes down
Vietnam's cities generally have good fixed and mobile connections, but outages still happen: a cut cable, a storm, a problem at the provider. Before the cloud, an outage stopped email; after the cloud, it can stop sales, stock checks and invoicing all at once. That deserves a simple plan rather than hope.
The cheapest layer is a second connection. A mobile router or a phone hotspot with a data plan can keep the most important devices online for a few hours. Some routers can switch to a mobile connection automatically when the main line fails.
The second layer is knowing what works offline. Many cloud apps can keep a local copy of selected files or allow sales to be recorded and synced later. Test this before you need it, because offline features often need to be enabled in advance on each device.
The third layer is a paper fallback for truly critical tasks. A printed price list and a simple form to record orders by hand may feel old-fashioned, but a shop that can keep selling during a two-hour outage loses far less than one that closes its doors.
Frequently asked questions
Is the cloud safer than our own office server?
For physical failures and basic maintenance, usually yes, because large providers handle hardware and updates better than a small office can. For account security and sharing mistakes, it depends entirely on how you configure it.
Do we still need backups if our files are in the cloud?
Yes. Cloud services protect against their own hardware failures, not against your accidental deletions, ransomware spreading through sync, or losing access to an account. An independent copy is what lets you recover from those.
Will moving to the cloud save money?
Sometimes, but not automatically. You stop buying servers and paying for their upkeep, but subscriptions are ongoing and grow with users and storage. Compare a full multi-year cost, including the staff time you currently spend on the old system.
Where is our data physically stored?
In the provider's data centres, which may be in Vietnam or abroad depending on the service and the region you choose. If location matters for your contracts or for legal reasons, ask the provider in writing and check current regulations.
How fast do we need to remove access when someone leaves?
The same day, ideally at the moment their last working session ends. Change shared passwords they knew, transfer ownership of their files to a company account, and revoke any sharing links they created.
