Bits & Bytes

Google Migrations: Go With the EDU Expert

Ankur Garg

Updated: July 2021.

This feature spotlight provides an in-depth look at the process of migrating a Microsoft Teams instance to a new Microsoft 365 tenant with MigrationWiz. Learn more about the growing demand (and opportunity) to support Teams migration projects here, or watch a short demo video of a Teams migration with MigrationWiz.

While students and faculty are at home, it’s a good time for system upgrades that will enhance collaboration, access, and security. Many colleges, universities, and school systems are planning winter break migrations to move or consolidate tenants and even adopt new collaboration platforms.

If you’re using Google Workspace, MigrationWiz is the tool you need for migrating a wide variety of workloads: Mailboxes, documents, archives, and even collaboration platforms. You can take advantage of low education pricing to move from one Google instance to another, or from Google Workspace to Microsoft Teams. MigrationWiz handles all these workloads:

  • Gmail and Vault, including inbox, folders/labels, email, muted emails, contacts, calendars, and calendar notifications.
  • Drive, including files, folders, permissions, document history, comments, and more.
  • Shared Drives, including documents, permissions, versions, and metadata.

Great education pricing is one thing, but when you’re planning a migration, you should never skimp on experience, capabilities, and security. That’s why BitTitan has been the choice of educational institutions for more than 13 years.

Experienced experts are here to help

BitTitan has migrated thousands of students, faculty, and staff at hundreds of educational institutions all around the globe. While MigrationWiz is known for being intuitive and easy to use, you never have to go it alone, especially if your project is more complex. Our world-class Customer Success team are dedicated migration experts who can help you plan your project.

In fact, now is the perfect time to call so we can connect you with team members who have extensive experience in educational environments – including implementing complex Google Workspace migrations.

Fast, easy, and flexible

Educational institutions choose MigrationWiz because it’s fully automated and 100% SaaS. In fact, if you were expecting to sprint around campus in order to complete your migration, you may have to get your exercise some other way. With MigrationWiz you simply initiate your migration from one centralized dashboard, then use DeploymentPro – which is included – to automate Outlook configuration.

Don’t be fooled, though. Easy doesn’t mean basic. MigrationWiz is highly customizable with advanced options that give you full control over your migration. You’re always in charge of timing, testing, setup, and execution. You can also use project sharing to involve team members across departments for greater visibility and collaboration throughout the migration.

Top security with Azure datacenters

Security is top priority for every migration project, especially in educational settings. You’re responsible for protecting personal information from students and faculty, as well as proprietary documents and research. You must be able to ensure every bit of data is safe throughout the migration process. With MigrationWiz you get the extra security of Azure datacenters. And, your data is always encrypted and never stored.

With BitTitan by your side, you can get a lot done over winter break. So when faculty, staff, and students return, they might not even notice because they’ll be able to get started with the new semester without any disruptions.

Now’s the time to plan your migration

If you’re ready to implement a migration, there’s still time to put a plan in place. Contact us today to find out about education pricing for MigrationWiz and to learn how we can help make your migration a success.

As adoption of Microsoft’s new collaboration platform has grown, so too has the need to migrate the files and conversations as part of a broader tenant-to-tenant project. Lucky for managed service providers and IT teams around the globe, MigrationWiz supports the transition of users and data between Teams instances just like mail and other workloads.

This article will detail what components of a Teams instance we are able to migrate; how this new workload can be configured in the same familiar MigrationWiz flow as other workloads like mail or documents; and information about additional features and licensing information. For step-by-step migration guides and other technical information, visit the BitTitan Help Center.

What Components of a Teams Instance Can BitTitan Migrate?

MigrationWiz now supports the migration of the following components:

  • Teams: the top-level Groups comprised of a user base, file site, and Channels. There may be several Teams in the organization’s broader instance and users may belong to multiple Teams. Teams can be both public and private.
  • Channels: within each Team, Channels are individual sections that contain a threaded Conversation tab and file folders. Channels can be both public and private.
  • Conversation History: the central discussion threads specific to each channel. This does not include private or group chats between users in the same tenant or a federated tenant.
  • Private Chats: one-to-one, group, and meeting messages.
  • User Memberships: the governance behind the entire Teams instance, including access control for users to each Team.
  • Files: documents stored on a SharePoint site specific to each Team with subfolders for each Channel.
  • OneNote: associated notebooks with the Team site are migrated as part of the Files pass.
  • Planner: tasks, buckets, plans, and more within the popular task management application.
  • Team and Channel Settings: Team pictures and descriptions, member permissions to add, remove, or edit apps or messages, etc.

With MigrationWiz, the most recent 3,000 conversation threads from the Source tenant will migrate over and be rehydrated in the proper Channels on the Destination. This includes timestamps (in UTC) to preserve an audit trail for legal departments and the lighter elements of Teams messages such as emojis, GIFs, and more. MigrationWiz will also indicate which discussions migrated from the previous tenant.

Conversation History older than those most recent messages will also be migrated in HTML format for data retention. These threads will be made available in the corresponding Channels on the Destination with a tab at the top labeled “Files.”

Private Chats are actually stored within Exchange and migrated as part of a standard mailbox project. For more information, see this post: Feature Spotlight: How to Migrate Teams Private Chats.

What’s the Flow for Teams Migration in MigrationWiz?


Configuring the Project

Teams migration projects will follow the same simple setup process as other workloads in MigrationWiz. For Teams projects, we’ve created a new project option: “Create a Collaboration Project.” This will now be presented alongside mailbox, document, archive, and public folder options in the “Create a Project” window.

Here the traditional MigrationWiz flow takes over: select Microsoft Teams as your Source and Destination endpoints, provide credentials, and begin to import Teams


Add Teams to A Collaboration Project

Once the project has been created, it’s time to add Teams to your project. MigrationWiz offers three methods to accomplish this:

  • Autodiscover: automatically scan the Source tenant to identify all teams in the instance. Once autodiscover has completed, users will have the option to directly import all the Teams as line items into the project or download a CSV file of all the Teams to further manage the Teams. The same CSV file can also be uploaded via Bulk Add.
  • Bulk Add: A good option for larger projects with more sophisticated mapping, MigrationWiz offers a CSV template file to manage adding Teams, or the option to use the one created during Autodiscover.
  • Quick Add: For smaller projects or proof of concepts, Quick Add allows you to migrate specific Teams without the full CSV management.



Start Your Migration

Once Teams have been imported, it’s time to start your migration. Like other workloads such as mailboxes, MigrationWiz treats each Team as an individual line item, allowing you to select individual Teams to migrate or move them all.



Once you have verified credentials for the selected Teams, you are now able to kick off the migration itself. Similarly to a pre-stage approach for mailboxes, the first pass in a Teams project will establish the “scaffolding” for the Teams instance on the Destination – recreating Teams and Channels but not yet migrating data.



Once that creation process is complete, the second pass will move Teams Permissions, Documents, Conversation History, and Document Permissions to the Destination tenant. We migrate up to 30 Teams in parallel and are able to migrate over 500 Teams/day depending on the amount of data contained within each Team. For more granular information on this scenario, see our step-by-step guide here.


MigrationWiz in Action: Teams Demo

Learn more about Teams migrations with MigrationWiz in the short demo video below. Our technical experts walk through project setup, the new Teams assessment tool, and other best practices to ensure your first Teams migration is a success.


Watch the demo now!

Related Posts

  • MigrationWiz – Workloads Datasheet
    Accessible anytime from anywhere, MigrationWiz provides a single, centralized interface to streamline everything from simple mailbox moves to complex enterprise-scale migration projects that include all your workloads.

Register for a FREE BitTitan Account

Create an account now and start planning your project.