Migrating From Exchange Server 2003 to Office 365Posted by Frost Enemark on April 24th, 2021 If you're still running Exchange Server 2003, then you need to fast track your workplace 365 migration, because Exchange 2003 stopped being supported by Microsoft in 2014. Also, most Exchange Server 2003 systems are running on Windows Server 2003 and this will also no longer be supported by Microsoft after June 2015. check here mean your system will be increasingly open to external hacker attacks as security breaches are no longer being fixed by Windows updates. In addition, unless you have moved your server to a virtual environment sometime over the last few years, it is extremely likely that your physical file server can be out of warranty, running slowly, nearing its disk capacity and starting to suffer reliability issues. Migration from Exchange 2003 to Office 365 can be safely done, however there's often a supplementary problem to be overcome concerning Microsoft Outlook. Many organizations that are running Exchange 2003 are also running Office 2003. The good news is that moving to Office 365 presents a great opportunity to also replace Office 2003 by choosing an Office 365 plan that includes Office 2013 - including the Office 365 Business Premium plan. The bad news is you have a chicken and egg situation because Office 2003 generally - and Outlook 2003 in particular - can not work with Office 365. This means that during the migration process you will need to decide between upgrading your email system first, and then not being able to get access to it until you've updated all the computers to a later version of Office (at the very least office 2007). Or, you upgrade all of the computers to a more recent version of Office first, and then do the migration of Exchange Server to Office 365. Whichever method you choose, you will see a period of time when users are stuck in no man's land - they won't have the ability to access their email server from their version of Outlook. So a choice ought to be made - is it far better upgrade Office first, or could it be best to upgrade the email server first? Real life experience shows that it's best in every situation to upgrade to Office 365 first and upgrade Office 2003 users to Office 2013. Here's two hypothetical examples to prove this point: Company A has 20 staff with 19 users running Outlook 2010 on their computers and with only 1 user running Outlook 2003. It would be best to migrate the e-mail server to Office 365 first, because only the one user won't be in a position to access the new email server until their version of Office gets upgraded. And it should take only one hour or so to get that user's computer upgraded to Office 2013. Company B also offers 20 staff, however in their case 19 users are on Office 2003 and only 1 is on say Office 2010. Initially this seems like an issue - if the Exchange 2003 Server is migrated to Office 365 first then the 19 staff won't be able to access their emails before computers have Office 2013 installed. And conversely, if the 19 computers are updated to Office 2013 first, they don't manage to access their emails before Office 365 migration process has been completed. Fortunately, in this case there is a very good interim solution - users could make usage of OWA (Outlook Web Access) to access their emails via the browser until their computers are updated to Office 2013. Indeed, it will also be possible for them to now have usage of Office 365 email on a range of smartphones and tablets they may already have like iPhones, iPads, Windows mobile devices and Android devices. Performing migrations to Office 365 from later versions of Exchange are a lot simpler to action, but with a well-designed scoping plan that considers the implications of old versions of Office, the Exchange 2003 migration process can still be performed in a timely and cost-effective fashion. This could be that the ultimate way to assure your organization of a successful Office 365 migration from Exchange 2003 is to use the services of a Microsoft Partner that has Office 365 certifications and real-world experience in performing Office 365 migrations.Like it? Share it! More by this author |