Hello,
Will try to cover most of the questions
Here are high level steps we identified.
1. We request to do organization database(XXX_MSconfig) backup in their sql sever.
You need to request a copy of the CRMOrgName_MSCRM and not MSCRM_CONFIG. MSCRM_CONFIG is specific to the deployment and gets created at install time. If you create a new CRM Deployment on a different server, then you should let the installer create it's own instance, even if the domain stays the same. MSCRM_CONFIG doesn't contain any CRM Organization Data - this is stored in the CRMOrgName_MSCRM database. CRMOrgName_MSCRM is the one you need to back up, copy, restore in SQL and them import in the deployment manager.
2. Spin up a new instance of CRM 365 on our AWS enclave.
3. From the Deployment manager restore the organization.
We have couple of questions
1. Even though we move to new AWS enclave, the domain is common. How can we use existing Active directory groups? when we restore the organization through organization db backup. do we have to do anything here to continue same AD Groups (Reporting Group, PrivReporting Group, SQLAccess Group, PrivUser Group)
I think you can still reuse the same groups if you use an installation configuration file and specify there the AD Groups to use https://docs.microsoft.com/en-us/previous-versions/dynamicscrm-2016/deployment-administrators-guide/hh699830%28v%3dcrm.8%29
I would however recommend creating new groups. CRM fill fill in automatically anyway the groups with the System Users once you import the CRM Organization.
Service accounts i think you can add manually - however this should't be much of an effort.
2. In our current instance,
3. Do we have to use same service Account who is currently as Deployment administrator or can we create a new deployment administrator. Basically when spinning new CRM instance, do we have to use same deployment administrator or can we use new one?
You can create a new one
4. IIS certificate : Do we have to generate new certificate request from our new IIS server or do we have to request third party ( who is hosting currently) to pass on old certificate ?
It depends on the certificate you are using. If you are using a wildcard certificate and importing the organization in the same domain, then you can reused. If you are using a named certificate and the machine name / dns configuration is different, then you need a new certificate
5. Product key: Can we get the product key from existing instance or do we have to get a new product key.
Not a licensing expert. But i think if you take the old environment offline and use the new one, you should be fine to reuse the same product key
6 Encryption key: Do we have to request the encryption key
You need to back it up before you take the CRM Organization offline. You can find this within the CRM Organization itself. No need to request it from the 3rd party vendor. See https://www.crmsoftwareblog.com/2015/02/back-encryption-key-crm-organization/
7. How to Integration with Exchange, SharePoint servers?
Exchange Integration: https://docs.microsoft.com/en-us/dynamics365/customer-engagement/admin/set-up-server-side-synchronization-of-email-appointments-contacts-and-tasks
SharePoint Integration: https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/integration-dev/get-started-sharepoint-integration
8. Currently our version is V8.2, so do we have to spin up V8.2 or can we use V9.0?
You can use V9.0. The CRM Organization will be upgraded during import. However you will need a CRM 9.0 license.
We appreciate your help if some one share any checklist and steps to do this kind of migration ( from third party hosting to our own hosting environment)
I suggest you check the official CRM Implementation Guide. You should find there everything you need https://www.microsoft.com/en-us/download/details.aspx?id=50039
I hope you find this useful.
Radu
