Summary

This article provides summary how to perform migration between versions of exchange servers integrated in MachPanel.

Applies To

This article applies to MachPanel build v6.0.32 and above.

Migration between versions of Exchange Servers integrated in MachPanel

Migration from one version of exchange (e.g. 2007/2010/2013/2016) to another (e.g. 2010/2013/2016/2019) has to undergo two phases.
    

1. Back-end Exchange migration. 
2. Control Panel Database modification to reflect the changes.

Important Note:
 
Kindly note that MachPanel does not offer any migration between versions of exchange integrated.  You have to perform the migration on backend (directly on your Exchange Servers) and then the control panel will need to be modified to recognize those changes and allow you to continue management of your organization and users after they are moved over to new Exchange Server.

In any upgrade/migration scenario, following would be possible options:

Scenario # 1: (Only Workable for Ex2010 & Ex2013)

Upgrade existing setup/server to latest version of exchange (Back-end work).  All organizations get updated in single go. After this we can switch Provider IDs of existing server so that it becomes server group of latest Exchange version.  
So, to summarize, Database modification will make the existing server groups for Exchange in MachPanel get converted to updated server groups and the existing setup keeps working without any issue or further amends. See Steps below

• Login to MachPanel Database server as MachPanel_Db user Get Provider ID from HB_tblExchangeProviders table.

• Update Provider ID in the Table tblExchangeServerGroups

Scenario # 2: (Workable for Ex2007, Ex2010 & Ex2013)
 
Provision new server, install latest version of Exchange and MachPanel Remotes, and do the migration on backend for each organization one by one.  
This means that some sites are on old server while others are on new server.  We have to have two Server Groups in MachPanel (old server group exchange 2007/2010/2013/2016 and new server group of exchange 2010/2013/2016/2019) and then we must adjust sites individually by modifying “HB_tblExchangeHosting” table in MachPanel_Db.

This scenario is workable when you migrate organizations from old server to new server, however the AD Structure remains the same.  

Please note that, after moving the organization on your backend and the organization Exists in MachPanel as well, then you will have to Point the organization to the Exchange New Servers in MachPanel database as well. If the New Exchange is already integrated in MachPanel then you will have to update records from in MachPanel database using details below:

1. Migration from Exchange 2007 to Exchange 2010 and changes required in MachPanel.

• Login to Machpanel Database server as MachPanel_Db user.
• Get SGmemberID of newly integrated "Exchange 2010" Server from MachPanel_DB.HB_tblExchangeServerGroupsMembers table.

• Search for the organization from MachPanel_Db.hb_tblExchangeHosting and update the SGmemberID against that organization to the SGmemberID got from above step.

• The only other change required was updating Server Group ID from Exchange Packages to Server Table.

2. Migration from Exchange 2010 to Exchange 2013 and changes required in MachPanel.

• Login to Machpanel Database server as MachPanel_Db user.
• Get SGmemberID of newly integrated "Exchange 2013" Server from MachPanel_DB.HB_tblExchangeServerGroupsMembers table.

• Search for the organization from MachPanel_Db.hb_tblExchangeHosting and update the SGmemberID against that organization to the SGmemberID got from above step.

• The only other change required was updating Server Group ID from Exchange Packages to Server Table.

3. Migration from Exchange 2013 to Exchange 2016/2019, Exchange 2016 to Exchange 2019 and changes required in MachPanel.

• Login to Machpanel Database server as MachPanel_Db user.
• Get SGmemberID of newly integrated "Exchange 2016/Exchange 2016" Server from MachPanel_DB.HB_tblExchangeServerGroupsMembers table.

• Search for the organization from MachPanel_Db.hb_tblExchangeHosting and update the SGmemberID against that organization to the SGmemberID got from above step.

• The only other change required is updating Server Group ID from Exchange Packages to Server Table.

More Information:

Regarding the AD users of the organization that do not have Exchange account you can also import them but you will require to perform one more step after you have completed the import of Exchange 2010/2013 organization. You will have to go to AD section of MachPanel and click on Sync from backend option against the imported organizations. It will import the AD users as well in MachPanel. Please review following KB article for AD sync from backend:

http://kb.machsol.com/Knowledgebase/Article/54533

We are here to assist you in this migration and assure you that we will do our best to complete this project with you.