Migrating Google Workspace isn't about moving data.It's about moving an organization.
I'm Sébastien Kusznier, an independent consultant and former company director. For more than ten years, I've migrated and administered Google Workspace environments ranging from a handful of accounts to several thousand users, for companies, groups, local governments and NGOs, in France and around the world. I handle the technical side, and above all everything around it.
What you can see
Copying emails, files and calendars from one account to another.
That's the visible part of a migration. Tools can do it, sometimes for free. It's also the smallest part of the job.
What you can't see
Everything that decides whether your organization works on Monday morning.
Business continuity
Everyone needs their messages, meetings and folders from the very first hour. A day of confusion costs more than the migration itself.
Sharing and access rights
Who can see what on Drive doesn't copy itself. A lost share means a client folder nobody can open. A badly restored one means a folder exposed to the wrong people.
Shared drives and orphaned files
Tens of thousands of files whose owners left long ago. They have to be found and reassigned before the cutover, not after.
Addresses, aliases and groups
Old addresses to keep, mailing lists, shared mailboxes: everything that gets the right message to the right person.
Identity and security
SSO, 2-step verification, rules per organizational unit. A migrated account has to sign in first time, without opening a gap.
Devices and applications
Outlook, IMAP, phones, business tools connected to Google: every use case has its traps, and they show up on cutover day.
Licenses
Mixed editions, duplicate accounts, people who have left: a migration is the right moment to pay only for what's used.
Scheduling
Several entities, sensitive periods, executives on the road. The order of cutovers is a management decision, not a technical detail.
People
Staff who are informed, prepared and supported adopt the new environment. The others put up with it, and let everyone know.
Governance afterwards
Structure, sharing rules, administration: the target environment has to stay clean two years from now, not just on day one.
A successful migration goes unnoticed. That's exactly what makes it hard.
An unusual profile, for a job that goes beyond technology
A migration affects management, staff, security and every line of business at once. It takes someone who can talk to each of them in their own terms.
A business leader before a technician
I have founded and run companies, including IT4LIFE, which integrated Google Workspace and Odoo for NGOs and social economy organizations, and now YULEK. I know what a day of downtime costs, what a board expects from a schedule, and how to trade off deadlines, budget and risk.
From a handful of accounts to several thousand users
I've migrated and administered organizations of every size: small teams, multi-agency groups, local government, an NGO operating in around ten countries. The rigor stays the same; the method adapts to the scale.
A broad range of skills
Google Workspace administration, identity and security, business software and ERP, user training, change management, project management. A migration calls on all of them at once, and you don't need three consultants to cover them.
International experience
I've lived in very different cultures and worked with teams spread across several continents. I know that a clear instruction in Paris isn't received the same way elsewhere, and that this is often where adoption is won or lost.
Very different professional worlds
Humanitarian aid, public sector, real estate, construction, car dealerships, e-commerce, creative agencies, social economy. Every trade has its habits and constraints, and I've seen them from the inside.
Why an independent consultant
One point of contact, from scoping to the last user question
No salesperson who sells and junior who delivers. I carry out the audit, the cutover plan, the migration and the support myself. What I tell you in a meeting is what gets done in the console.
Professional tools, used every day
CloudM Migrate to move large volumes reliably, GAM to administer at scale. Thousands of scripted operations that can be checked and repeated, rather than clicks by hand.
Overnight cutovers, without sleepless nights
I work between Paris and Costa Rica. Cutovers scheduled overnight in Europe happen in broad daylight for me: your teams start the morning on an environment that's ready and checked.
A five-step method
Audit and mapping
Users, groups, aliases, shared drives, volumes, licenses, SSO, connected apps. We measure before we promise.
Cutover plan
Order of entities, migration windows, DNS, staff communication, rollback plan. Agreed with you before anything is touched.
Pilot
A test group migrates first. We fix whatever needs fixing while the stakes are still low.
Migration and cutover
Data is copied in advance without disrupting work. At cutover, only the remaining changes are transferred and mail is redirected.
Support and clean-up
User support, checks, clean-up of accounts and licenses, documentation of the final environment.
Organizations that trusted me
- THE INDEPENDENTS
- SAFTI
- Conseil départemental des Alpes‑de‑Haute‑Provence
- ALIMA
- Léon Grosse
- Tressol Chabrier
- Private Sport Shop
- ORES Group
- Minlay
Two examples
THE INDEPENDENTS
Six agencies consolidated into a single Google Workspace environment: 564 mailboxes, around 34 TB of data, staggered cutovers agency by agency so production never stopped, and nearly 193,000 files reorganized across shared drives.
ALIMA
International medical NGO. As IT manager: moving 1,500 staff across around ten countries from basic email to Google Workspace, with the change management that goes with it.
Frequently asked questions
Will my teams lose access to their email during the migration?
No, not if it's properly prepared. Most of the data is copied in advance while everyone keeps working. The cutover itself happens in a quiet window, in the evening or over a weekend.
How long does a migration take?
It depends on volume, the number of entities and scheduling constraints. A few days for a small organization, several weeks for a group bringing together several companies. The initial audit gives you a precise timeline.
Can we migrate in stages?
Yes, and it's often the best option: entity by entity or department by department, with a pilot group first.
Do you work internationally?
Yes. I work in French, English and Spanish, with organizations and teams spread across several countries.
Google offers migration tools. Why hire an expert?
Those tools work for simple cases. As soon as there are shared drives, cross-sharing, several domains, SSO or a tight schedule, the cost of a mistake far outweighs the cost of expert support.
Let's talk about your migration before it starts.
A merger, a domain change, a spin-off or simply a clean-up: describe your situation in a few lines and I'll come back to you with a first view of what's at stake.
skusznier@yulek.net