nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Account migration from Gsuite to Microsoft

Fabio Polato

Hi all,

my company is scheduling to migrate mail accounts from Google Gsuite to Microsoft.

Our Jira, Jira Service Desk and Confluence Cloud applications are connected to Google Gsuite and our users login with google.

When Gsuite will be definitively abandoned what will happen to all users and ticket they have assigned and articles they have write?

Is there some kind of migration process for this users or the process is painless?

Thank you

Accepted answers

All comments

Luke Welden

Hi Fabio,

Did you get a response to this elsewhere? We're about to do the exact same thing.

Cheers,

Luke.

Daniel Eads

In a nutshell, the accounts in Jira will be re-associated with the login details from your Microsoft identity provider (presumably Azure AD). The process is a little more complicated than simply choosing a new identity provider.

We have an article here on Community that describes the process step-by-step, which I recommend following in order to easily change identity providers:

Migrating from G Suite to other Identity Providers (Okta, Azure AD, OneLogin etc)

Cheers,
Daniel

Shyamily Kuriakose

Hi Fabio,

Im also have the same concern,

At present, our Executive Director has initiated a standard JIRA plan with 18 users, all of whom were added through Google. Our organization is currently using Google products, but we will likely transition to Microsoft by October 2024. This means we are migrating from Google to Microsoft.

As the Digital Analyst, I have a few concerns regarding this transition:

Will our JIRA setup be affected by the migration from Google to Microsoft?

Are there any tasks I need to perform before the migration to ensure a smooth transition?

Will the migration result in the creation of a new, separate organization for all users?

Please advice on the basis your experience.

Shiv Gupta_14b82b

Kernel for Google Workspace to Office 365 offers a reliable, secure, and efficient solution for migrating G Suite (Google Workspace) data to Office 365. It ensures a seamless, hassle-free transfer of emails, contacts, calendars, Drive files, and other important data, with complete data integrity and no loss. Whether you're migrating in bulk or selecting specific data, the tool offers flexible migration options to suit your needs. With its intuitive, user-friendly interface, the Google Workspace to Office 365 migration tool simplifies the entire process, enabling a smooth, quick migration without requiring any technical expertise.

Harvey alex

I recently migrated from G Suite to Office 365, and I did research to find the best way to migrate the data. I read many blogs and forums and found a tool called Shoviv G Suite to Office 365 Migration. I saw that it is recommended by many people and also has very positive reviews.

Using the software, migration has become very easy and efficient for me. It can transfer all kinds of Google Workspace data, including emails, calendars, contacts, and Drive data. The G Suite migration tool performs well with large data volumes and multiple accounts.

ZelinaSmith

If you want to move the account from G Suite to Microsoft then in this situation I suggest you try this professional tool like OSTtoPSTAPP IMAP to IMAP Migration Tool is a great way to move emails safely and automatically. You can use this tool to connect G Suite and Microsoft 365 accounts using IMAP and move emails in groups or one at a time. The software can sync data in real time, handle massive amounts of data, and keep the folder structure and attachments safe. It's perfect for all users who want to switch platforms without losing data or having to wait.

rishi giri

Thats a great answer that really clear my doubt

Cheers

luke

Joseph Miller_qvgcl1

Hi Fabio,

Good question — this is a common concern when moving from G Suite (Google Workspace) to Microsoft.

Your Jira, Jira Service Desk, and Confluence data (users, tickets, articles) won’t be deleted just because you stop using G Suite. However, the authentication method is the key issue.

Since your users currently log in via Google, once G Suite is decommissioned:

Users may lose access unless you switch authentication (e.g., to Microsoft Azure AD or Atlassian accounts)
You’ll need to update user identities in Atlassian (email matching is critical)
Tickets, assignments, and content remain intact as long as user accounts are mapped correctly

What you should do:

Set up Microsoft 365 accounts for all users
Ensure email addresses remain the same (this preserves mappings in Jira/Confluence)
Switch authentication from Google to:
Atlassian native login, or
Azure AD (recommended for SSO)
Test login and permissions before fully disabling G Suite

About migrating mailbox data

For email migration from G Suite to Microsoft 365, you can use tools like EdbMails G Suite Migration Tool, which helps with:

Secure migration of emails, contacts, calendars, tasks, many more.
Automatic mailbox mapping
Incremental migration (avoids duplicates)
Migration using a single admin account (no need for individual user email IDs and passwords)
Zero downtime

Steps to perform G Suite to Office 365 Migration

Important tip

Before shutting down G Suite, make sure:

All users can log in with the new method
No accounts are left unmapped
Admin access is verified

migration expert

For the actual heavy lifting of moving the mailbox and drive data over to Microsoft, I highly recommend using the SysTools Google Workspace to Office 365 Migration Tool. Moving enterprise data requires a dedicated migration solution—not just a basic sync utility—to ensure complete data integrity across both platforms.

As an administrator, you can use the SysTools software to securely automate the entire process. Key benefits include:

Complete Data Transfer: Migrates Emails, Contacts, Calendars, and Google Drive documents directly into their Microsoft 365 counterparts.

Automated User Mapping: You can map multiple accounts in bulk using a simple CSV file, which speeds up the process significantly.

Concurrent Migration: It handles multiple mailboxes simultaneously without throttling, ensuring zero downtime for your users.

Data Integrity: It strictly maintains folder hierarchies, metadata, and read/unread status without creating duplicates.

It handles the complexities of tenant migration exceptionally well, making the transition completely painless for the end-users.

Rowan Fletcher_gyfh6a

Yes, there is a migration process, and if it's planned properly, your Jira users, assigned tickets, and Confluence pages should remain intact. The critical part isn't the email migration itself, it's migrating your user identities correctly.

Before you decommission Google Workspace:

Set up Microsoft Entra ID (Azure AD) or another supported identity provider for Atlassian.
Map each existing Google Workspace user to the corresponding Microsoft 365 account (using the same email address makes this much easier).
Test the sign-in process with a few users before switching everyone.
Verify that Jira issue assignments, comments, watchers, and Confluence page ownership are still linked to the correct accounts.

I have done a similar migration from Google Workspace to Microsoft 365. In our case, we migrated the mailboxes individually using TrustVare IMAP Migration Tool, whereas we had already completed the identity migration for Atlassian. Since the mapping of the user accounts was correct before we disabled Google Workspace, users did not need to recreate any of their projects, tickets or Confluence.

My advice: Don't disable Google Workspace until you've confirmed that Microsoft 365 authentication is working and a few pilot users can access all of their Atlassian data correctly. That small test can prevent most migration issues.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-desk-cloud

jira-software-cloud

confluence-cloud