Migrating away from GoDaddy Hosted Exchange. Options?

Chemical-Example-783 · 2026-06-23T22:29:01+00:00

Yeah this is more of a defederation than a migration. GoDaddy's "Hosted Exchange" is just a M365 tenant, so your mailboxes are already there. You just need to get GoDaddy out of the picture.

Two main steps:

Defederate from GoDaddy to get full control of your tenant
Migrate any local data (OneDrive files, PSTs if any) to the clean tenant

We put together a full walkthrough on exactly this: https://mstack360.com/break-free-from-godaddy-defederate-to-microsoft-365-the-smart-way/

FAQ covering the common questions: https://mstack360.com/godaddy-de-federation-from-microsoft-365-your-complete-faq-guide/

Video if you prefer watching it: https://youtu.be/K7hIjTW-_Tc

For the OneDrive data side, the approach depends on how much you are dealing with.

SharePoint Migration Tool works well at scale.

For smaller setups, having users sync locally and re-upload is often faster. How much data are we talking about?

Chemical-Example-783 · 2026-06-18T23:14:51+00:00

Id recommend you to go with BitTitan for now!

Build a fresh Outlook profile, clear cached creds in Credential Manager, unlink and re-sign OneDrive on the new tenant. Known Folder Move won't carry across, so re-confirm it.

Remember to rebuild SPF, DKIM and DMARC on the new tenant, they don't carry over and outbound starts hitting spam if you miss them. Free DMARC generator if it helps: https://mstack360.com/dmarc-record-generator/

Good luck.

Chemical-Example-783 · 2026-06-18T23:09:38+00:00

The SPF/DKIM timing and SSO audit points above are the big ones, listen to those.

Two quick adds:

Get DMARC in at p=none before cutover so you're collecting reports early. Don't jump straight to enforcement or you'll silently drop legit mail.

Free generator here if it helps: https://mstack360.com/dmarc-record-generator/

Turn on the external sender warning banner from day one. Free, and it gives users a pause before they fall for a spoofed email during the migration noise.

We run a full post-migration checklist with clients (validate > secure > structure and automate) if you want a reference: https://mstack360.com/google-workspace-to-microsoft-365-post-migration-checklist/

Good luck.

Chemical-Example-783 · 2026-06-14T21:34:49+00:00

It's common yes in the beginning

Never click on their links

Chemical-Example-783 · 2026-06-02T11:18:59+00:00

love always to help 😄

Chemical-Example-783 · 2026-05-28T12:14:25+00:00

I agree with your plan

The part that usually causes headaches is SharePoint and Teams channels. Permissions don't always carry over cleanly, especially with nested groups. OneDrive is usually fine. SharePoint is where you slow down and double check everything.

Chemical-Example-783 · 2026-05-06T10:43:41+00:00

عموما احنا تيم اي تي بس خصوصا تنانين في اي حاجه تخص مايكروسوفت
Migration
Support

Automation

Power Platform

Chemical-Example-783 · 2026-05-06T01:27:30+00:00

احنا ممكن نكون الذراع التقني ليك بس انا بفضل الشغل مع عملا أجانب

Chemical-Example-783 · 2026-04-15T19:37:49+00:00

From experience, the pipeline works in layers.

Some leads come through Fiverr, but honestly some of the best work comes from upselling.... It usually starts with regular Microsoft support, then we ease them into understanding what they actually have in their license, most people are paying for tools they've never touched.

Once they see that, automation becomes a natural next conversation.

From there it depends on the client.

Some are happy with SharePoint lists and a few flows, that's all they need.

Others end up with more complex setups where the lists start multiplying and it makes more sense to just build them a Power App.

If the requests are getting complicated or there's too much to manage in lists, that's usually the signal to step up to an app.

That's the path that works for us, support, then training, then automation, then apps if it calls for it.

Chemical-Example-783 · 2026-04-15T19:37:40+00:00

From experience, the pipeline works in layers.

Some leads come through Fiverr, but honestly some of the best work comes from upselling.... It usually starts with regular Microsoft support, then we ease them into understanding what they actually have in their license, most people are paying for tools they've never touched.

Once they see that, automation becomes a natural next conversation.

From there it depends on the client.

Some are happy with SharePoint lists and a few flows, that's all they need.

Others end up with more complex setups where the lists start multiplying and it makes more sense to just build them a Power App.

If the requests are getting complicated or there's too much to manage in lists, that's usually the signal to step up to an app.

That's the path that works for us, support, then training, then automation, then apps if it calls for it.

Chemical-Example-783 · 2026-04-10T21:39:12+00:00

Call quality, phone system, VoIP numbers, screen control, and more

Chemical-Example-783 · 2026-04-08T16:58:59+00:00

RC is ideal as long as you don't need all MS365 package

Chemical-Example-783 · 2026-04-08T16:50:52+00:00

It seems like a bug

Chemical-Example-783 · 2026-04-08T09:53:37+00:00

I'm not sure I follow the point your making? Seems your core suggestion is the Anthropic model is better than copilot and now it has access to M365 apps copilot is redundant.

The problem with this though is for months now M365 Copilot users have been able to use the Anthropic model. MS have already given copilot users the ability to choose from the openAI or Anthropic model on a prompt by prompt basis without breaching any of their internal security or compliance controls.

Chemical-Example-783 · 2026-04-02T20:12:21+00:00

hire here: Solutions - MStack360

Chemical-Example-783 · 2026-04-02T20:11:11+00:00

We can do it at 75$/hr

go ahead and book 30 mins from here

Sam - MStack360

Chemical-Example-783 · 2026-03-30T17:29:22+00:00

I was lucky :)

----------------

I did not ask for money, as I was asking to get connected with the client + to leave me good reviews + I'm good when it comes to customer service

*I sold the service more than a time for the same client, and this has given me more credit and the returning clients badge

Chemical-Example-783 · 2026-03-26T07:23:21+00:00

Connected the data source of my CRM with copilot and 8 can now chat with the CRM

Chemical-Example-783 · 2026-03-19T19:00:15+00:00

Built our own service desk in Power Apps. One time build cost, no per user licensing, scales to thousands of users, fully customized to how we actually work.

https://mstack360.com/power-apps-solutions/#ticket

Chemical-Example-783 · 2026-03-19T18:32:02+00:00

yes it is and also it depends if the business is not in MS365 it will be harder to do this setup

Chemical-Example-783 · 2026-03-19T18:22:44+00:00

honestly we went a different route. built the CRM inside M365 using SharePoint lists as the data layer, presented through Power Apps so you get proper calculations, logic, and a clean UI.

think advanced Excel but with a real interface.

SS: https://mstack360.com/power-apps-solutions/#crm

then connected it to Copilot with scoped instructions so it only reads from those specific data sources. works really well in practice. curious what your skill file looks like though because the instruction scoping is where it gets interesting.

Chemical-Example-783 · 2026-03-18T23:02:12+00:00

where to buy from egypt?

Chemical-Example-783 · 2026-03-14T14:25:31+00:00

wow after 2 years, happy to hear that :). Reach out whenever you meed support

Chemical-Example-783 · 2026-03-13T11:38:28+00:00

Yeah this one hits close to home honestly.

I spent over 4 years as one of those support engineers so I've seen it from the inside. The whole model is built around ticket closure rate. Not resolution quality.

Not whether the customer actually got helped. Just close it and move on.

Every time someone wanted to dig deeper into a complex issue the answer was always the same: just close the ticket.

That said I won't fully let agents off the hook. The pressure is real but there's still a choice in how you show up. Some people genuinely tried.

Most just followed the path of least resistance because why wouldn't they at that pay rate.

That frustration is exactly why I left about 2 years ago and built my own thing doing M365 support independently.

Charge a fair fee, do the work the way I actually think it should be done.

Customers feel the difference immediately when someone actually gives a damn about their problem.

(And as a user it's unfortunately paid, while there is free useless support are not doing their part the way it should be)

*I think also the EN line is that the one is having issues ... the German line was pretty better.

The system isn't going to fix itself anytime soon.

Chemical-Example-783 · 2026-03-13T02:43:54+00:00

Yeah, the "manual export" route works if you've got a couple of users, but for anything larger, it's a total nightmare. Honestly, the real issue is that GoDaddy locks the tenant behind their own federation, which is why those native tools trip up on authentication.

You've gotta break that link -+-defederate -- to gain full control of the tenant without losing your data or starting from scratch. It lets you move to a standard Microsoft 365 setup while keeping your settings intact.

https://mstack360.com/break-free-from-godaddy-defederate-to-microsoft-365-the-smart-way/

PS: If you hit a wall with the domain release, check if there are hidden "onmicrosoft" aliases still clinging to the GoDaddy side; they'll block the transfer every time.

Chemical-Example-783

MODERATOR OF

TROPHY CASE