Migration
30 TopicsMigrating from Google Workspace to Microsoft 365 with to have two separate Mailboxes per User + SSO
Context and Requirements: My company (abc.com) is being acquired by another org (xyz.com). We’re currently on Google Workspace (G Suite) for abc.com email and want to migrate everything (email, calendar, contacts) into Microsoft 365 — specifically into the xyz.com tenant. After migration, each user must have two fully separate mailboxes: Mailbox A: email address removed for privacy reasons (data migrated from G Suite) Mailbox B: email address removed for privacy reasons (new mailbox in the xyz.com tenant) We need true single sign-on (SSO) so users can log in once and access both mailboxes (not just alias addresses) within the same tenant. We want to minimize complexity. FYI we will set up abc.com as an Accepted Domain in xyz.com Microsoft Exchange tenant. What I’ve Investigated So Far: Migration Tools: The Exchange Admin Center has a built-in G Suite migration wizard, but it mainly migrates mail to one mailbox. Third-party tools like BitTitan MigrationWiz can also handle G Suite → M365 migrations. Two-Mailbox Setup Approaches: One licensed mailbox + one shared mailbox: For example, the user’s main mailbox would be email address removed for privacy reasons (fully licensed with migrated data), while email address removed for privacy reasons is a shared mailbox to keep it separate. The email address removed for privacy reasons account gets Full Access and Send As permissions on the xyz.com mailbox. Pros: Single sign-on, one set of creds, minimal extra licensing. The data stays separate (two distinct mail stores). Cons: Shared mailboxes are limited to 50GB if unlicensed, and some compliance features may require a license. Two fully licensed user mailboxes (two Azure AD user accounts, e.g. email address removed for privacy reasons and email address removed for privacy reasons): Each mailbox is completely independent, but typically requires two sign-ins unless there’s advanced identity federation to unify credentials. Also doubles the licensing. Pros: Full feature set in both mailboxes, no shared mailbox constraints. Cons: Additional license costs, and not a straightforward “one-click” SSO for both. Questions Which approach is best for maintaining two discrete mailboxes per user without forcing them to manage multiple logins? Are there any best practices for migrating from Google Workspace into Exchange 365(specific tenaant) maintaining the same email address? Have you run into compliance or eDiscovery issues with a shared mailbox approach? Any caveats or special steps needed to ensure calendars and contacts migrate correctly from Google Workspace into the new environment?30Views0likes0CommentsHelp with 365 migration please
Can anyone help me with this Migration please. The tenancy has existed for some time and all users have had a business standard license to enable them to use Teams and Office 365 for some time. This means that mailboxes were created automatically but these have never been used. AD Sync was in place. I am trying to migrate from Exchange 2016 to 365. I have: Checked each user has an e-mail alias in Exchange @leonardgray.onmicrosoft.com. Configured Outlook Anywhere on my on-premises Exchange Server. Enabled MRS Proxy on your on-premises Exchange Server. Use the Microsoft Exchange Remote Connectivity Analyzer to test your connection settings. Used the Outlook Anywhere (RPC over HTTP) or Outlook Autodiscover tests - it is showing no issues. Checked the permissions on the account I'm using to migrate (domain admin and has FullAccess and assigned WriteProperty permissions). We're not on Exchange server 2007 so no need to worry about unified messaging. The domains are verified. The users are created licensed. I have the CSV with the list of users. I've created a variety of migration endpoints and it verified as it saved and saved successfully. I initially tried to use a cutover migration as it is what I have used successfully in the past. This failed, when I researched the error the articles suggested that it was because AD sync was in place. So I turned off AD sync. The cutover migration continued to fail. The articles suggested that a Staged migration was a better option for this scenario. This failed with this error: Error: MigrationTransientException: Failed to update the on-premises mailbox with the target address (SMTP:email address removed for privacy reasons). The mail sent to the user will not reach user's hosted mailbox. The error might be due to account credentials used for migration not having enough permission to write data back into the on-premise AD. Please ensure that the account credential has Domain Admin privilege. --] We weren't able to connect to the remote server. Please verify that the migration endpoint settings are correct and your certificate is valid, and then try again. Consider using the Exchange Remote Connectivity Analyzer (https://testexchangeconnectivity.com) to diagnose the connectivity issues. I did some more reading and found an article that suggested that Staged migrations can only be used from Server 2003 and 2007. So I decided to try a Remote Migration. This one failed with the error: Error: TargetUserAlreadyHasPrimaryMailboxException: Target user '902b455c-5986-47c7-9988-bb7282df52b5' already has a primary mailbox. The articles about this suggest I need to delete the data in homeMDB and homeMTA. The data in homeMDB looks like a pretty important link between Exchange on prem and Active Directory. I'm not particularly comfortable with just deleting this. Can anyone tell me what I'm missing?41Views0likes0CommentsCuales son los pasos para migrar mi correo que tengo en Godaddy a Microsoft 365
Tengo una cuenta de correo en Godaddy con mi dominio personal, quiero comprar una licencia de Microsoft 365 y migrar mi correo hacia Microsoft 365 así poder aprovechas todos los servicios que ofrece Microsoft Mi licencia actual vence el 1 de enero del 2025 He tratado de comprar una licencia con la cuenta de correo, pero me da error porque me indica que está asociado a un proveedor externo que Godaddy. Intente migrarlo con la gente de Godaddy, me dice que debo tener un plan de licencia y el correo creado en Microsoft para que hagan la migración. Todo me indica que en Godaddy están haciendo lo imposible para entorpecer la migración. Quedo atento a su respuesta20Views0likes0CommentsTenant to tenant mail migration from large to small organization
According to Microsoft sales team the answer in this thread is most likely wrong! Can you confirm that? (commenting is not possible anymore) We are a small group in a very large organization now established as an independent company. A very common situation. New licenses for Office365 including everything and all premium have been acquired for our small independent group. The very reason to continue using Office365 is to ensure a smooth migration of Outlook mail including calendar, and only spending a minimum of time on related tasks. MS sales team advice that you can do a migration as in these guides, but you require "Cross Tenant User Data Migration", which only is available to "Enterprise Agreement" customers - and of course not for our small group. How can we quickly and smoothly do the migration? In case of a work-around like exporting data to a PST-file, then please observe that this task must be completed in the web app, and we cannot achieve admin privileges in the large organization. The question has been migrated from here.423Views1like2CommentsYou are not eligible for FastTrack assistance.
After purchasing E3 and E5 licenses after how many days we are eligible to request for FastTrack assistances? For me license purchased 2 days before but in Admin portal still we are getting "You are not eligible for FastTrack assistance." Any idea?229Views0likes0CommentsInactive Users PST Migration from Tenant to Tenant M365
Is there a way I can migrate an inactive PST to another Office 365 tenant? Any suggestions on how I can move PST files to another tenant using eDiscovery? Is there any PowerShell script that can upload the PST directly into another Tenant data life cycle management Import job for PST. can AZ copy -copy the data from eDiscovery Export Key to Target Tenant SAS URL.336Views0likes0CommentsMigration of Inactive Users
Hi Team, We recently received a new request for Migration of Inactive Users from Source Microsoft365 tenant to Destination Microsoft 365 tenant we need to automate this migration can anybody recommend the best way to achieve this. Need to Migrate the Mailbox Data and OneDrive Data of Users307Views0likes0CommentsHow Domain migration will happen in Google Workspace to Microsoft 365?
Hi, We are planning to migrate from Google workspace to microsoft 365, during this migration how we will handle below scenarios, How the domain migration will happen without business impact? How to keep both google workspace & Microsoft 365 setup in parallel? How to redirect the domain from google to Microsoft?541Views0likes0CommentsExchange Hybrid DNS and Certificate
Hi, I am currently planning Exchange Hybrid (Exchange2019) in a test domain. The current configuration is Internal Exchange 2019 servers are load balanced through a third party load balancer and a DNS entry of mail.domain.com is used for all https services such as ews, auto discover etc. There is no external access to Exchange A single Internally generated certificate with multiple SANs is used which includes mail.mydomain.com, imap.mydomain.com, pop.mydomain.com etc. It is bound to the IMAP, POP, IIS and SMTP services There are no edge servers and incoming and outgoing email is delivered through a third party appliance. I will however introduce an edge server to be used for secure email between Exchange and Exchange Online. I'm a bit confused about what the externally supplied certificate required for Exchange Hybrid and DNS entries should be in order to configure the HCW. 1) Does the external certificate required for the Transport certificate replace the existing internal certificate already on the Exchange servers. i.e. I would need to create a new external certificate with all the SANS I have already and use this certificate on the same Exchange Servers and for the same Exchange services as well as installing it on the new Edge server? If the certificate does replace the existing certificate I presume that I would need to keep the same DNS name i.e. mail.mydomain.com and configure this on the external DNS server If the certificate does not replace the existing certificate would it only be installed on the edge server? If the certificate is only installed on the Edge server I presume I can create a DNS entry called say mailhybrid.mydomain.com and a certificate to match. This cert will only be installed on the edge server and has no bearing on the internal Exchange servers and I will not need to replace the certificate on them. 2) The HCW asks for the organization FQDN which I believe is used to configure the outbound connector from EOP to on-premises. I presume this would be configured on the Edge server. Would the FQDN be what I am already using internally i.e. mail.mydomain.com or would it be mydomain.com or does it relate to the transport certificate selected earlier and could be anything such as mailhybrid.mydomain.com. Sorry for all the questions and I hope they make sense.4.5KViews0likes1Commentmigration from google drive to onedrive
hello, im trying to migrate from Gdrive to onedrive. 35 users. i dont need download zip and then upload . im trying to use migration from new exchange admin center, but the service like not working . cant scan drives and than migrate. getting error but log dont show anything. any suggess?1.5KViews1like1Comment