Short answer: An AWS migration Brisbane project for a file server or on-premises app follows the same seven steps every time: list what’s on the server and who uses it, pick the right AWS target for each piece, build a secure AWS account first, copy the data while the old server keeps running, test with a small pilot group, cut over in a planned window with a rollback ready, then switch off the old server only after a settling-in period. For Queensland businesses, keeping the data in an Australian AWS region is usually part of the plan from day one.
This is the practical follow-on to our guide on what AWS migration is and the 7 Rs. That article explains the choices. This one walks through what actually happens when a business moves one server.
AWS migration Brisbane: what you’re actually moving
Most “file servers” do more than store files. Before anything moves, write down everything the server does:
| Item | What to record | Why it matters |
|---|---|---|
| Shared drives | Folder structure, total size, how fast it grows | Decides storage type and how long the copy takes |
| Permissions | Which groups and people can open which folders | Has to be mapped exactly, or staff lose access on day one |
| Users and sign-in | Whether it relies on Active Directory or another directory | AWS needs to know who’s who before it can enforce permissions |
| Apps on the server | Accounting, practice management or other line-of-business software | Each app may need a different approach to the files |
| Mapped drives and shortcuts | Drive letters and paths staff and apps use | Changing paths breaks shortcuts, macros and linked spreadsheets |
| Backups | What’s backed up today and how it’s restored | The new setup needs a tested backup before cutover |
| Who uses it, and when | Offices, remote staff, busy periods | Sets the cutover window and the network you’ll need |
Step 1: Assess the server and its users
Start with an inventory of the server and a conversation with the people who use it. Ask which folders really matter, which apps open files directly from the share, and when a short outage would hurt least. Check your internet connection too: staff will now reach files over it, so upload and download speed at each office matters more than it did before.
This is also when you decide what not to move. Old archives, duplicate folders and abandoned project files can be retired or moved to cheaper archive storage, which shortens the migration and lowers the ongoing bill.
Step 2: Choose the target for each piece
Using the 7 Rs, each part of the server gets its own decision. For a typical small business server, the common choices are:
- Shared drives: a managed Windows file share such as Amazon FSx for Windows File Server, which keeps the familiar folder and permission model, or Amazon S3 for archives that are rarely opened.
- Line-of-business apps: rehosted onto an Amazon EC2 virtual server as they are, replatformed onto managed AWS services, or replaced with the vendor’s cloud version if one exists.
- Old data: archived to low-cost storage, or retired once you’ve confirmed nobody needs it.
Sometimes the best answer for part of the server isn’t AWS at all. If most of your work happens in Microsoft 365, some shared folders may fit better in SharePoint or Teams, and some businesses run a mix of AWS and Azure. Our comparison of Azure vs AWS migration covers how to weigh that up.
Step 3: Build a secure AWS landing zone first
Nothing should move until the AWS environment is ready. A landing zone is the foundation: the account structure, identity and access controls, multi-factor authentication, logging, network setup and backup policies. For Queensland businesses, this is when you choose an Australian AWS region, such as Sydney or Melbourne, so your data stays onshore.
Connectivity comes next. Offices usually reach AWS over a secure VPN, and staff sign-in has to be connected so the same usernames and groups work against the new file share.
Step 4: Copy the data while the old server keeps running
The first full copy of the data runs in the background while staff keep working on the old server. Tools such as AWS DataSync are built for this. After the first copy, changes are synced again and again, so the final sync at cutover only has to move what changed in the last day or so.
Check permissions on the copied folders as you go. A file that arrives safely but can’t be opened by the right people isn’t migrated yet.
Step 5: Pilot with a small group
Before everyone moves, a small group of staff uses the new file share or app for real work. They open, save and share files, run the line-of-business app, print, and work from home. Problems found here, like a missing permission or a spreadsheet linked to an old drive path, are cheap to fix. Problems found after everyone has moved are not.
Step 6: Cut over, with a rollback ready
Cutover is the planned switch from the old server to AWS. A good cutover plan covers:
- A window outside business hours, agreed with the people who’ll be affected.
- A final sync of changes, then the old share set to read-only so nothing is saved in the wrong place.
- Mapped drives, shortcuts and app settings pointed at the new location.
- A checklist of tests staff run first thing the next morning.
- A rollback plan, agreed in advance, so you can go back to the old server if something important doesn’t work.
Keep the old server running, read-only, until the new setup has proven itself.
Step 7: Settle in, tidy up and switch off
In the weeks after cutover, watch performance and running costs, and fix any leftover access issues. Run a test restore from the new backups. Then review the AWS setup: right-size anything that’s bigger than it needs to be, check storage tiers and set budgets and alerts so the bill doesn’t drift. Only then should the old server be wiped and decommissioned.
Common mistakes to avoid
- Moving everything as is. Old, unused data costs money in AWS every month. Clean up first.
- Forgetting the internet link. If your office connection is slow, files will feel slow, no matter how fast AWS is.
- Skipping the permissions check. Most day-one complaints come from folders people can’t open.
- No rollback plan. If you can’t go back, a small problem becomes a business outage.
- Switching off the old server too early. Keep it until you’ve done a full week or month-end on the new setup.
- Treating backup as AWS’s job. Under the shared responsibility model, your configuration and backups are still yours to get right. See backup and disaster recovery.
How Loginet helps
Loginet is an AWS Partner and Microsoft Azure Partner, working with businesses across Queensland and the rest of Australia. Our AWS migration services cover each step above: discovery, a migration plan per workload with cost estimates, landing zone and security set up before anything moves, file server and data migration with permissions mapped and verified, cutovers that can be scheduled outside business hours with a rollback plan, and a post-migration optimisation review.
If you already run workloads in AWS, you can also move your AWS billing to Loginet as your AWS Partner. See our Amazon Web Services and cloud solutions pages for ongoing cloud management after the move, or server and storage solutions if part of your setup is staying on site.
Frequently asked questions
How do you move a file server to AWS?
List what’s on the server and who uses it, choose an AWS target such as a managed Windows file share, build a secure AWS account, copy the data while the old server keeps running, pilot with a small group, cut over outside business hours with a rollback plan, then switch off the old server once everything is proven.
How long does it take to move a file server to AWS?
It depends on how much data there is, your internet speed and how many apps rely on the server. A small file server move may take days, while a server with several business apps is planned in stages over weeks. You’ll get a timeline after the assessment.
Will staff still see their drive letters after moving to AWS?
They can. Mapped drives can be pointed at the new AWS file share during cutover, so staff keep working with familiar drive letters and folders.
Can our files stay in Australia if we move to AWS?
Yes. AWS has regions in Australia, and the environment can be set up so your data is stored in an Australian region.
Will there be downtime when we cut over?
Downtime can be kept short. Data is copied in advance, the final sync happens in an agreed window outside business hours, and a rollback plan is agreed before cutover.
Should our files go to AWS or Microsoft 365?
It depends on how you work. Files that apps open directly, or that need traditional Windows permissions, often suit an AWS file share. Everyday documents that staff share and edit together may suit SharePoint or Teams. Many businesses use both.
Plan your move
Book a free 30-minute strategy call and tell us what’s running on your server today. We’ll talk through the right path to AWS, step by step.


