Szallas Group unifies domains through a Google Workspace to Google Workspace migration

As a long-term partner of Szallas Group, we supported their migration of the Romanian company Travelminit and its domains under the main szallas.hu domain. The company needed to unify 80 users and 2.7 TB of data across four domains, 24 groups, and three Shared Drives without disrupting daily work.

When a company needs to unify its digital environment — perhaps following an acquisition or rebrand — it often means moving everything from one Google Workspace environment to another.

Even though it’s still Google, moving between Google Workspace tenants isn’t straightforward. There’s no built‑in way to move data end-to-end, and it’s not a simple copy and paste either. The process requires expert planning, and Revolgy helped Szallas through the migration.

A staged plan with a defined scope and owners

As a Google Partner with the Work Transformation specialization and ISO/IEC 27001:2022 certification, Revolgy handled the full migration project governance and technical execution, breaking it into a staged plan followed by a post-migration phase for older data.

The scope covered four key service areas:

• Technical migration: Handling the raw data movement (emails, MyDrive, contacts, calendar events).
• Technical consultations: Configuring the new environment securely using Revolgy’s recommended best practices.
• Change management: Clear communication and guidance so 80 employees understood the why and the how.
• Project management & governance: Keeping the whole process structured, communicating status updates via Google Chat, and managing the project schedule and tasks.

How we executed the migration

The migration wasn’t done all at once. Revolgy used a staged approach:

• Setup: Configured Google Cloud Platform service accounts and Domain‑wide Delegation in both tenants; enforced 2‑Step Verification; set up initial mail routing.
• Pre‑migration data sync: The decision was made to first migrate the last year of data and leave the rest for post-migration, which helped accelerate the migration process.
• Migration phase: At week four, we released the primary domain from the source tenant, registered, and assigned domains in the target tenant. This was followed by a delta migration to catch all the recent data (emails and Drive files) created during the bulk move.
• Post-migration: After the primary migration, we ran a final phase to move historical data (emails older than one year) so all legacy information was in the new tenant.

“I’ve done a few of these Google Workspace to Google Workspace migrations now, and they’re never as simple as they sound. We spent a lot of time planning this one because we knew the size of the data and the number of domains could make things complicated. We broke it into clear phases, kept in close contact with the Szallas team, and delivered everything successfully.”

— David Formánek, Technical Engineer, Revolgy

Setting clear expectations for end users

Managing end‑user expectations is perhaps the most crucial part of any migration. Because Google Workspace to Google Workspace migrations have technical limits, some data could not be moved automatically, so we told users exactly what would and what would not transfer.

What did not migrate automatically:

• Google Drive links: URLs change after migration; update shared docs, wikis, and bookmarks that reference old links.
• Gmail filters and Chrome data: Personal filters, bookmarks, and history require manual export and import.
• Google Chat messages: At the time of our migration, Chat history could not be migrated; where retention policies allowed, we advised forwarding key messages to Gmail or exporting permitted data.
• Third‑party apps and SSO: Apps authorized with source‑tenant accounts require re‑authorization in the target tenant; this was handled by the customer.

What to avoid during pre‑migration: During the pre-migration phase, employees were specifically asked to avoid changing their Drive structure and modifying Gmail labels to prevent conflicts or duplicate work when the final data switch occurred.

“We needed to move 80 people from four domains into one Google Workspace. I was concerned about disruption to our teams, especially since we’re in the travel business, where email and calendar are really important. Revolgy kept it simple, told us what was happening at every stage, and the move was so smooth most people didn’t even notice.”

— Peter Kovacs, Senior IT Support Engineer, Szallas Group

About the customer

Szallas Group Zrt. is a multi‑product online travel platform operating across Central and Eastern Europe.

Headquartered in Miskolc, Hungary, the company works with 90,000 accommodation partners, processes about 1 million reservations a year, and serves 2.5 million guests across six countries (Hungary, Czech Republic, Romania, Poland, Croatia, and Slovakia).

Its annual Total Transaction Value (TTV) is approximately €250 million.

Conclusion

This project shows that even complex Google Workspace moves can go smoothly with good planning and clear updates.

Revolgy worked closely with the Szallas team throughout the process. As their Google Cloud partner, we continue to support their Google Workspace setup, helping them make the most of having everyone on one platform.