November 10, 2026
Every MSP knows the feeling: a customer hands you a migration bigger than anything you’ve run before, and the end users expect to notice nothing. That’s exactly where Licencias OnLine found itself when a Chilean telecom provider needed to move 1,900 users from Google Workspace to Microsoft 365.
Licencias OnLine is one of Latin America’s leading value-added technology distributors, with 13 offices serving 40 countries, more than 4,000 channel partners, and over 25,000 end customers. Beyond licensing, its team delivers presales support, solution design, training, and migration services, and it has relied on MigrationWiz for years to move partners and their customers to the cloud.
We spoke with Henry Garcia and Daniel Yesuron, technical presales architects at Licencias OnLine, about how they used MigrationWiz to deliver their largest project yet, and what other MSPs can take from it. You can find the full Customer Spotlight here.
The challenge: one source tenant, two destinations, and 300 GB mailboxes
A major telecommunications provider in Chile, and a reseller partner of Licencias OnLine, needed to move all of its data from Google Workspace to Microsoft 365. The project covered roughly 1,900 licenses. The team even waited a full Google Workspace renewal cycle so they could plan it properly rather than rush it.
The scope was demanding:
- Tenant split: one Google Workspace tenant moving into two separate Microsoft 365 tenants, with some users needing to exist in both.
- Data volume: some mailboxes held more than 300 GB.
- Full lifecycle ownership: Licencias OnLine handled sizing, licensing, solution design, migration, and end-user enablement.
- New territory: their previous largest project was about 900 users, roughly half the size.
“The customer came to us with just the need: we have to move from here to here, and split it into two tenants. We had to do everything else.” — Henry Garcia, Licencias OnLine
| By the numbers | |
| Users migrated | ~1,900 |
| Destination tenants | 2 |
| Largest mailboxes | 300+ GB |
| Concurrent users in flight | ~80 |
| Data moved per user per day | ~20 GB |
| Mailbox projects | 6 |
| Project duration | Just under 3 months |
| End-user cutover | One weekend |
The approach: turn one big migration into many small ones
With a tight timeline and a huge volume of data, the team knew they needed an orchestration tool. Years of using MigrationWiz on smaller projects made the choice easy, and their BitTitan account manager, Ximena Giraldo, helped them fit the customer’s budget and close the deal.
Their biggest worry was whether Google and Microsoft could move that much data without interruption. The answer was to stop treating it as one massive job.
“Part of the solution is not to think of it as a huge project, but to divide it into multiple smaller projects, and MigrationWiz allows you to do that. We turned one huge migration into multiple little migrations running concurrently.” — Daniel Yesuron, Licencias OnLine
Here’s how they structured it in MigrationWiz:
- Map users to tenants. They worked with the customer to decide which Microsoft 365 tenant each user would land in.
- Split the work into projects. Using the MigrationWiz portal, they created separate projects, selected endpoints, and configured credentials. Documents got one project per destination tenant.
- Separate the heavy mailboxes. Standard users went into a single-pass project. Users with very large mailboxes were split into separate projects for their primary mailbox and their archive.
- Tune advanced settings. Each project’s settings controlled exactly what data moved and when.
- Validate with a pre-migration pass. Before scaling up, they confirmed data was flowing correctly from source to destination.
- Run in parallel. Because Google and Microsoft throttle transfers to roughly 1 GB per hour, concurrency was essential. The team ran about 80 users at a time, moving around 20 GB per user per day.
“One of the things I like most about BitTitan is that it lets you do a pre-migration step, so you can see if the data is actually going from origin to destination. Once that’s happening, you just run everything else concurrently.” — Daniel Yesuron
Solving challenges in real time
No migration this size goes exactly to plan. One surprise came from how differently Google and Microsoft organize email: Google labels become folders in Microsoft 365, so a message with several labels can appear in several folders. For some users, that duplication filled their Microsoft 365 mailbox storage much faster than expected.
The team had already planned to move only recent mail into the primary mailbox for the heaviest users, but some accounts were still too large. So they re-planned, created additional projects, and restarted those users. By the end, mailbox migration ran across six projects, isolating the largest users and their archives from everyone else.
“Google and Microsoft speak different languages, but the BitTitan services allowed us to solve for almost all of them. Nothing critical was lost along the way.” — Daniel Yesuron
Granular monitoring made those mid-flight adjustments possible. MigrationWiz reporting and email notifications let the team check the status of all 1,900 users at any time and pinpoint errors quickly. When questions came up, BitTitan’s documentation and 24/7 support filled the gaps.
“Something I love about BitTitan is the documentation. It’s accurate and step by step on how to configure both environments. When you have an issue, they have an answer for it.” — Henry Garcia
The result: a weekend cutover
The full project took just under three months. For end users, it took a weekend.
“They were working on Google on a Friday, and the next Monday they were in Microsoft with everything migrated.” — Daniel Yesuron
The customer’s earlier move to Google Workspace had been rough, so the team braced for chaos after the DNS cutover. Instead, the following week brought only routine questions about logins and new tools. No one reported lost data, and nothing was urgent.
“Part of what the customer told us was, ‘I can’t believe there’s nothing else to do here.'” — Daniel Yesuron
What MSPs can take from this project
Licencias OnLine’s experience offers a practical playbook for any MSP facing a migration larger than they’re used to:
- Break it up. Splitting one large migration into smaller, concurrent MigrationWiz projects makes scale manageable and keeps throttling limits from becoming bottlenecks.
- Isolate the outliers. Give very large mailboxes and archives their own projects so they don’t hold up everyone else.
- Validate before you scale. A pre-migration pass confirms data is flowing correctly before you commit the full user base.
- Plan for platform differences. Google labels becoming Microsoft 365 folders can inflate mailbox sizes, so size destination storage with that in mind.
- Watch it closely. Per-user reporting and notifications let you catch and fix issues mid-flight instead of after cutover.
- Keep users working until cutover. Users stay productive in the source system until you decide it’s time to switch.
“MigrationWiz allows you to do basically 99% of the work without impacting the end customer. Users keep working in their origin system until you tell MigrationWiz it’s time for the cutover.” — Daniel Yesuron
The team also found that MigrationWiz handles small, medium, and large migrations with essentially the same configuration, plus a few advanced settings learned along the way. As Henry put it, “Now I have different approaches for every kind of migration, from the simplest to a huge project.”
You can read the full story in the Customer Spotlight.
Take on your next migration with confidence
Whether you’re moving 50 users or 5,000, MigrationWiz gives MSPs the orchestration, monitoring, and support to deliver migrations their customers barely notice. Start a free trial or contact the BitTitan team to learn how MigrationWiz handles migrations of any size and complexity.