SBS 2003 Migrate to Office 365 Exchange Online

Hi,

exchange 2003 is not supported for hybrid environment (min Exchange 2010), so you cannot do that type of migration.
You need to do a cut-over migration or some staged. Configure Office 365 Exchange just as you would if it is in your company, reconfigure MX records for your domain to point to Office 365, connect users Outlook to it and then migrate email. Export email to .pst and either upload to Office 365 or just add to users Outlook...or something like that.

How many users do you have, and how many GB of email?

Here are some of guides:
http://blogs.technet.com/b/canitpro/archive/2013/05/31/step-by-step-migration-of-exchange-2003-server-to-office-365.aspx

https://technet.microsoft.com/en-us/library/jj874016(v=exchg.150).aspx
https://technet.microsoft.com/en-us/library/jj874018(v=exchg.150).aspx

Regards,
Ivan.

Hi cutover migration  is exactly what I'm trying to do. I've done this successfully with other exchange 2007 and exchange 2010 servers without an issue.

We are talking about 15 mailboxes around 20gb of email data.

Are you saying SBS 2003 with exchange 2003 isn't supported for a cutover migration to 365?

Hi,

every exchange is ok for cutover or staged. I meant that 2003 is not supported in hybrid :)

any ideas why I can't get this to work?
see attached (it's SBS Exchange 2003 I'm not sure if the exchange server and RPC fields should be the same? and if Authentication matters? )
I've tried externaldomainname.com in both boxes and it refuses to go through saying there's a problem with the migration endpoint.

as I say I purchased an SSL cert with just externalmaildomainname.com and imported it onto the SBS 2003 and can access it fine via the web using the name.com all ok.
IIS show it has the cert on the virtual websites etc.

Starting to think this is a no go and I'll have to manually export them to PST files instead?

hi thanks see attachment.

365.PNG

What should be in Exchange server box and RPC proxy server?
I thought it should just be my mail.domainname.com in both fields?

I'm getting this error when using the Remote connectivity analyser:-

The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=migrate.domainname.com, CN=companyweb, CN=internalservername, CN=localhost, CN=internalservername.localdomainname.local
       A certificate chain couldn't be constructed for the certificate.

Not sure if this is related to not being able to migrate to 365?
I've attached the actual error the migration is giving me as well.
365-error.PNG

Q. What should be in Exchange server box and RPC proxy server?

A. You should have the internal server fully qualified domain name in the Exchange Server box e.g., mail.internaldomain.local and externalmaildomainname.com in the RPC proxy address (to match the name on your SSL certificate).

If the Exchange Connectivity Analyzer fails, then the 365 migration won't work, so you need to resolve the issues with the server certificate first.

If you are getting A certificate chain couldn't be constructed for the certificate then you may need to update the Root Certificates by following this guide:

https://technet.microsoft.com/en-us/library/cc786443(v=ws.10).aspx

If that doesn't fix it, you may need to install a 3rd party certificate that is already trusted by your server.

It should be relatively easy to resolve.  Once you have the test site showing everything working happily, you can then perform the cutover migration.

Alan

I remember SBS2003 world, it is OK to use Self-sign certicate as the exchange certificate.

Problem with Office 365, it need a 3rd party certificate.

you can try to fix this and hopefully this is the last item on the card.

##############

I will recommend MIgrationwiz, as it ignore certificate and etc issues, and read using administrative accounts

http://blog.bittitan.com/2013/06/27/exchange-2003-migration-tip-creating-administrative-credentials/


But it comes with cost.