Transferring Office 365 hosted by GoDaddy to Office 365 hosted by Microsoft

%3CLINGO-SUB%20id%3D%22lingo-sub-302473%22%20slang%3D%22en-US%22%3ETransferring%20Office%20365%20hosted%20by%20GoDaddy%20to%20Office%20365%20hosted%20by%20Microsoft%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-302473%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EHow%20do%20I%20transfer%20my%20domain%20from%20my%20old%20Office%20365%20account%20hosted%20by%20GoDaddy%20to%20a%20new%20Office%20365%26nbsp%3B%20hosted%20by%20Microsoft%3F%20Everytime%20I%20try%20to%20setup%20the%20new%20Office%20365%20I%20get%20following%20errormessage%3A%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%22domain.at%22%20has%20already%20been%20added%20to%20another%20Office%20365%20mandate%20(Netorgft123456.onmicrosoft.com)%20managed%20by%20GoDaddy.%20To%20add%20this%20domain%20to%20this%20tenant%2C%20you%20must%20contact%20GoDaddy%20support%20and%20have%20the%20domain%20removed%20from%20Netorgft123456.onmicrosoft.com.%20After%20this%20is%20done%2C%20you%20can%20come%20back%20and%20continue%20this%20step.%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EGoDaddy%20isnt%20verry%20supportive%20so%20I%20try%20to%20seek%20help%20here%20%3A%3D)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-302473%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-302482%22%20slang%3D%22en-US%22%3ERe%3A%20Transferring%20Office%20365%20hosted%20by%20GoDaddy%20to%20Office%20365%20hosted%20by%20Microsoft%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-302482%22%20slang%3D%22en-US%22%3EHi%20Emeraldo%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20done%20several%20migrations%20from%20GoDaddy%20to%20Office%20365%20in%20the%20past.%20The%20way%20that%20GoDaddy%E2%80%99s%20control%20panel%20is%20deeply%20integrated%20with%20Office%20365%20tenants%20for%20their%20customers%20make%20it%20almost%20impossible%20to%20remove%20the%20domain%20without%20GoDaddy%E2%80%99s%20support%20as%20well%20as%20do%20advanced%20admin%20actions%20you%20would%20usually%20do%20when%20managing%20365.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20you%20have%20a%20different%20solution%20currently%20and%20not%20actively%20using%20Office%20365%20with%20Godaddy%20just%20raise%20a%20support%20call%20and%20ask%20them%20to%20strip%20the%20custom%20domain%20out%20of%20the%20office%20365%20tenant%20and%20cancel%20any%20associated%20Office%20365%20service.%20After%20you%20can%20set%20up%20in%20the%20new%20tenant%20and%20change%20DNS%20when%20required.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20you%20are%20migrating%20from%20their%20Office%20365%20and%20are%20actually%20using%20their%20service%20my%20recommendation%20is%20to%20set%20up%20the%20new%20365%20environment%20on%20the%20name.onmicrosoft.com%20domain%2C%20get%20a%20copy%20of%20the%20data%20via%20PST%20or%20migrate%20it%20with%20something%20like%20BitTitan%2C%20arrange%20a%20call%20with%20them%20and%20get%20an%20agreed%20time%20to%20remove%20the%20domain%2C%20remove%20services%20and%20cancel%20the%20subscription%20so%20you%20can%20coordinate%20the%20setup%2C%20DNS%20changes%20and%20reimport%20of%20the%20data.%20There%20will%20be%20an%20outage%20during%20this%20scenario%20but%20you%20can%20workaround%20this%20by%20setting%20up%20a%20server%20to%20queue%20the%20mail%20if%20you%20know%20how%20to%20do%20this.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20that%20helps%2C%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-302478%22%20slang%3D%22en-US%22%3ERe%3A%20Transferring%20Office%20365%20hosted%20by%20GoDaddy%20to%20Office%20365%20hosted%20by%20Microsoft%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-302478%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20not%20a%20support%20forum%20though%2C%20and%20we%20can%20only%20assist%20you%20with%20advice.%20You%20can%20always%20try%20to%20open%20a%20support%20case%20with%20%22regular%22%20O365%20if%20the%20GoDaddy%20folks%20are%20giving%20you%20trouble%2C%20but%20at%20the%20end%20the%20domain%20needs%20to%20be%20released%20on%20their%20side.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2442684%22%20slang%3D%22en-US%22%3ERe%3A%20Transferring%20Office%20365%20hosted%20by%20GoDaddy%20to%20Office%20365%20hosted%20by%20Microsoft%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2442684%22%20slang%3D%22en-US%22%3EChris%3A%3CBR%20%2F%3ECan%20you%20help%20me%20think%20through%20this%20one%3F%3CBR%20%2F%3E%3CBR%20%2F%3E1.%20Domain%20is%20with%20GoDaddy%3CBR%20%2F%3E2.%20When%20did%20the%20domain%2C%20of%20course%20made%20the%20mistake%20to%20do%20the%20office365%20there%20too.%3CBR%20%2F%3E3.%20Web%20hosting%20is%20with%20a%20different%20provider...that%20email%20is%20hosted%20with%20too.%3CBR%20%2F%3E4.%20People%20log%20in%20to%20email%20with%20the%20hosting%20provider...%20with%20their%20%40ABC.com%20email%20account%3CBR%20%2F%3E5.%20Other%20services%20that%20GoDaddy%20didn't%20give%20use%20(business%20central%2C%20visio%2C%20azure%2C%20etc)%2C%20users%20login%20with%20%40abc.onmicrosoft.com%20account%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20...%20how%20specifically%20do%20we%20deal%20with%20this%20one%3F%20Everyone%20seems%20to%20be%20scratching%20their%20heads%3F%3CBR%20%2F%3E%3CBR%20%2F%3EI%20think%20what%20I%20need%20to%20do%20is%3A%3CBR%20%2F%3E%3CBR%20%2F%3EA.%20Move%20the%20web%20and%20email%20hosting%20back%20to%20go%20daddy%20and%20get%20rid%20of%20the%20third%20party%20involved.%3CBR%20%2F%3EB.%20Subscribe%20to%20Office%20365%20through%20the%20Azure%20account%20logged%20in%20as%20.onmicrosoft.com%20account%3CBR%20%2F%3EC.%20Download%20all%20files%20and%20such%20from%20Teams%20(that%20are%20at%20GoDaddy)%3CBR%20%2F%3ED.%20Download%20all%20emails%20(that%20are%20at%20GoDaddy)%3CBR%20%2F%3EE.%20Download%20files%20from%20OneDrive%20(that%20are%20at%20GoDaddy)%3CBR%20%2F%3EF.%20Cancel%20the%20Office365%20from%20GoDaddy...%3CBR%20%2F%3EF.%20Move%2FTransfer%20the%20core%20domain%20from%20GoDaddy%20to%20MS%20and%20associate%20into%20the%20current%20(.onmicrosoft.com)%20account%3CBR%20%2F%3EG.%20Change%20the%20primary%20domain%20to%20ABC.com%20instead%20of%20ABC.onmicrosoft.com%20%5Bor%20is%20this%20step%20even%20needed%5D%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20goal%20is%20to%20get%20everything%20into%20the%20current%20.onmicrosoft.com%20Azure%20account%2Ftenant%2C%20users%20then%20could%20use%20their%20ABC.com%20account%20to%20get%20their%20email%20and%20sign%20in%20to%20all%20of%20the%20applications%20and%20services%20at%20that%20point%20(email%2C%20business%20central%2C%20visio%2C%20etc).%20I%20need%20to%20make%20sure%20we%20do%20not%20lose%20email%20access%20for%20more%20than%20a%20day%20or%20few%20hours%20through%20this%20process....%3CBR%20%2F%3E%3CBR%20%2F%3EThoughts%3F%3F%3F%3C%2FLINGO-BODY%3E
Deleted
Not applicable

How do I transfer my domain from my old Office 365 account hosted by GoDaddy to a new Office 365  hosted by Microsoft? Everytime I try to setup the new Office 365 I get following errormessage: 

"domain.at" has already been added to another Office 365 mandate (Netorgft123456.onmicrosoft.com) managed by GoDaddy. To add this domain to this tenant, you must contact GoDaddy support and have the domain removed from Netorgft123456.onmicrosoft.com. After this is done, you can come back and continue this step. 

GoDaddy isnt verry supportive so I try to seek help here :=)

3 Replies

This is not a support forum though, and we can only assist you with advice. You can always try to open a support case with "regular" O365 if the GoDaddy folks are giving you trouble, but at the end the domain needs to be released on their side.

Hi Emeraldo,

I have done several migrations from GoDaddy to Office 365 in the past. The way that GoDaddy’s control panel is deeply integrated with Office 365 tenants for their customers make it almost impossible to remove the domain without GoDaddy’s support as well as do advanced admin actions you would usually do when managing 365.

If you have a different solution currently and not actively using Office 365 with Godaddy just raise a support call and ask them to strip the custom domain out of the office 365 tenant and cancel any associated Office 365 service. After you can set up in the new tenant and change DNS when required.

If you are migrating from their Office 365 and are actually using their service my recommendation is to set up the new 365 environment on the name.onmicrosoft.com domain, get a copy of the data via PST or migrate it with something like BitTitan, arrange a call with them and get an agreed time to remove the domain, remove services and cancel the subscription so you can coordinate the setup, DNS changes and reimport of the data. There will be an outage during this scenario but you can workaround this by setting up a server to queue the mail if you know how to do this.

Hope that helps,

Best, Chris
Chris:
Can you help me think through this one?

1. Domain is with GoDaddy
2. When did the domain, of course made the mistake to do the office365 there too.
3. Web hosting is with a different provider...that email is hosted with too.
4. People log in to email with the hosting provider... with their @ABC.com email account
5. Other services that GoDaddy didn't give use (business central, visio, azure, etc), users login with @abc.onmicrosoft.com account

So ... how specifically do we deal with this one? Everyone seems to be scratching their heads?

I think what I need to do is:

A. Move the web and email hosting back to go daddy and get rid of the third party involved.
B. Subscribe to Office 365 through the Azure account logged in as .onmicrosoft.com account
C. Download all files and such from Teams (that are at GoDaddy)
D. Download all emails (that are at GoDaddy)
E. Download files from OneDrive (that are at GoDaddy)
F. Cancel the Office365 from GoDaddy...
F. Move/Transfer the core domain from GoDaddy to MS and associate into the current (.onmicrosoft.com) account
G. Change the primary domain to ABC.com instead of ABC.onmicrosoft.com [or is this step even needed]

The goal is to get everything into the current .onmicrosoft.com Azure account/tenant, users then could use their ABC.com account to get their email and sign in to all of the applications and services at that point (email, business central, visio, etc). I need to make sure we do not lose email access for more than a day or few hours through this process....

Thoughts???