SOLVED

Migrate Domain and email to new tenant.

%3CLINGO-SUB%20id%3D%22lingo-sub-201277%22%20slang%3D%22en-US%22%3EMigrate%20Domain%20and%20email%20to%20new%20tenant.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-201277%22%20slang%3D%22en-US%22%3E%3CP%3EHi.%3C%2FP%3E%3CP%3EI%20need%20a%20easy%20and%20good%20solution%20for%20migrating%20a%20domain%20and%20mails%20to%20new%20tenant.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20tryed%20to%20do%20it%20with%20SysTools%20%2C%20but%20from%20what%20i%20can%20see%20%2C%20it%20don't%20fix%20the%20problem%20with%20domain%20already%20taken.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20also%20asked%20Microsoft%20for%20a%20solution%20to%20this%20case%20%2C%20but%20they%20say%20they%20dont%20have%20a%20solution%20for%20this%20yet.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20problem%20is%20that%20when%20the%20domain%20is%20registered%20with%20one%20tennant%20%2C%20there%20is%20no%20way%20to%20create%20a%20new%20tennant%20with%20the%20same%20domain.%20If%20i%20then%20create%20a%20tenant%20with%20a%20temp%20domain%20%2C%20i'm%20not%20able%20to%20sync%20mail%20to%20mailboxes%20with%26nbsp%3Btemp%20domain%20%2C%20but%20same%20name%20in%20front%20of%20the%26nbsp%3B%40.%26nbsp%3B%20I%20end%20up%20with%20doing%20this%20by%20configure%20each%20mail.%20Do%20an%20export%20%2C%20Configure%20the%20temp%20mail%20%2C%20then%20import.%20Then%20delete%20the%20domain%20from%20old%20tenant%20%2C%20takes%20one%20day%20before%20I'm%20able%20to%20add%20the%20domain%20to%20new%20tenant.%20Then%20change%20all%20mail%20accounts%20to%20the%20right%20domain%20name.%20Then%20change%20DNS.%20In%20this%20time%20%2C%20there%20are%20mails%20that%20entered%20the%20old%20tenant%20%2C%20that%20is%20not%20in%20the%20new%20mailbox.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20found%20a%20solution%5Ctool%20to%20do%20this%20%2C%20without%20to%20much%20downtime%20on%20the%20mail%20accounts%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20understand%20why%20it%20can%20be%20so%20hard%20for%20MS%20to%20make%20a%20solution%20for%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreeting.%3C%2FP%3E%3CP%3EJorgen%20Gjerdrum%3C%2FP%3E%3CP%3EComtech%20AS%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-201277%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-201302%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20Domain%20and%20email%20to%20new%20tenant.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-201302%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Matthias%20and%20thank%20you%20for%20your%20answer.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20the%20reason%20that%20you%20use%20BitTitan%20for%20synkronizing%20%2C%20instead%20of%20just%20using%20migration%20option%20in%20office%20365%20Exchange%20Administration%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreeting%20Jorgen.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-201281%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20Domain%20and%20email%20to%20new%20tenant.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-201281%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20we%20do%20it%20in%20this%20way%20normally%20for%20our%20customers%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EDefine%20migration-date%20(day%20x)%3C%2FLI%3E%3CLI%3Eold-tenant%3A%20old.onmicrosoft.com%2C%20new%20tenant%3A%20new.onmicrosoft.com%2C%20default-domain%3A%20contoso.com%20(set%20up%20on%20old.onmicrosoft.com)%3C%2FLI%3E%3CLI%3ESetup%20new%20mailboxes%20on%20new.onmicrosoft.com%3C%2FLI%3E%3CLI%3EPre-migrate%20content%20older%20then%2090days%20from%20old.onmicrosoft.com%20to%20new.onmicrosoft.com%20(by%20migrationwiz.com)%3C%2FLI%3E%3CLI%3Eset%20TTL%20of%20contoso.com%20to%205min%20(day%20x%20-72h)%3C%2FLI%3E%3CLI%3Eon%20day%20x%2C%20remove%20contoso.com%20from%20old.onmicrosoft.com%20(by%20script%20remove%20it%20from%20everywhere%20(mailboxes%2C%20alias%2C%20groups%20etc.)%3C%2FLI%3E%3CLI%3Eadd%20domain%20contoso.com%20to%20new.onmicrosoft.com%3C%2FLI%3E%3CLI%3Emake%20the%20domain%20verification%3C%2FLI%3E%3CLI%3Eadd%20by%20script%20the%20domain%20to%20mailboxes%2C%20alias%2C%20groups%20etc.%3C%2FLI%3E%3CLI%3EFinalize%20the%20migration%20(full-migration)%20trough%20migrationwiz.com%20to%20get%20the%20rest%20of%20the%20content%20(newer%20tan%20the%2090days%20of%20the%20past)%3C%2FLI%3E%3CLI%3EAttach%20security%20permissions%20of%20mailboxes%20and%20so%20on%3C%2FLI%3E%3C%2FUL%3E%3CP%3EI%20hope%20these%20will%20help.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EMatthias%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Deleted
Not applicable

Hi.

I need a easy and good solution for migrating a domain and mails to new tenant.

 

I have tryed to do it with SysTools , but from what i can see , it don't fix the problem with domain already taken.

 

I have also asked Microsoft for a solution to this case , but they say they dont have a solution for this yet.

 

The problem is that when the domain is registered with one tennant , there is no way to create a new tennant with the same domain. If i then create a tenant with a temp domain , i'm not able to sync mail to mailboxes with temp domain , but same name in front of the @.  I end up with doing this by configure each mail. Do an export , Configure the temp mail , then import. Then delete the domain from old tenant , takes one day before I'm able to add the domain to new tenant. Then change all mail accounts to the right domain name. Then change DNS. In this time , there are mails that entered the old tenant , that is not in the new mailbox.

 

Anyone found a solution\tool to do this , without to much downtime on the mail accounts ?

 

I don't understand why it can be so hard for MS to make a solution for this.

 

Greeting.

Jorgen Gjerdrum

Comtech AS

 

 

2 Replies
Highlighted
Solution

Hi, we do it in this way normally for our customers:

 

  • Define migration-date (day x)
  • old-tenant: old.onmicrosoft.com, new tenant: new.onmicrosoft.com, default-domain: contoso.com (set up on old.onmicrosoft.com)
  • Setup new mailboxes on new.onmicrosoft.com
  • Pre-migrate content older then 90days from old.onmicrosoft.com to new.onmicrosoft.com (by migrationwiz.com)
  • set TTL of contoso.com to 5min (day x -72h)
  • on day x, remove contoso.com from old.onmicrosoft.com (by script remove it from everywhere (mailboxes, alias, groups etc.)
  • add domain contoso.com to new.onmicrosoft.com
  • make the domain verification
  • add by script the domain to mailboxes, alias, groups etc.
  • Finalize the migration (full-migration) trough migrationwiz.com to get the rest of the content (newer tan the 90days of the past)
  • Attach security permissions of mailboxes and so on

I hope these will help.

 

Regards,

Matthias

Highlighted

Hi Matthias and thank you for your answer.

 

What is the reason that you use BitTitan for synkronizing , instead of just using migration option in office 365 Exchange Administration ?

 

Greeting Jorgen.