Most of us know about Import Organization (formerly known as the Redeployment Tool), but I’m sure few of us have heard about the Edit Organization. Today I will explain the differences between Import and Edit, and when we should use one or the other, with emphasis on Edit Organization.
- Edit Organization is used to change the settings of an organization that exists already in a CRM deployment.
- Import Organization is used to add a pre-existing organization to a CRM deployment.
Use this feature when the CRM organization already exist in the CRM deployment and you need to move (restore) the organization database into another SQL Server, change SRS Data Connector URL and/or the Friendly Name.
The organization must be Disabled first, in order for the Edit Organization menu option to show up for that organization.
- Customer moves the current organization database into another SQL Server
- Customer restores a backup organization database into another SQL Server; this is an important characteristic that Edit Organization has it and Import Organization doesn’t, even if apparently it looks like might be able to do it (see next).
Edit Organization knows how to “resolves orphan users”: if a user did not exist at the time when the backup was made (it was created later after the backup), then Edit Organization will remove that user from the MSCRM_CONFIG database and clean up all references; if the user existed at the time when the backup was made but was deleted later, then Edit Organization will restore the user and all its references. You should not use Import Organization to restore a backup of organization database in the same CRM deployment, as it will not “resolve any orphaned users”, and as a result you will end-up with the user list in organization database and MSCRM_CONFIG database being out of sync.
The right permissions will be granted to our CRM OU Group from AD in order to access the organization database from new SQL Server.
The organization database must be manually restored onto the new SQL Server with the same name as was used on the old SQL Server. It must be a CRM 4.0 database.
Obviously it does not know how to clone the organization in order to create a copy of the organization as it is working with an existing organization entry in the CRM deployment. Instead, you can use Import Organization to do it as it will create a new organization entry in the CRM deployment.
The Deployment SDK supports Edit Organization.
Microsoft Dynamics SRS Data Connector URL
You can change the SRS URL associated with an organization. This will result in the reports being republished. All the customization done to reports will be kept.
The right permissions will be granted to our CRM OU Group from AD in order to access the reports.
It is just a Friendly Name change, the one that is usually displayed in the Web UI and Deployment Manager. Please note that we do not allow changing the Unique Name.
- Customer migrates production CRM organization from one CRM deployment to another CRM deployment, very likely in different AD domains
- Customer performs pre-production testing, CRM pre-release testing or reproducing issues using production data but in a test environment
- Partner develops client solutions in-house and then ships a pre-configured CRM organization to clients
Use this feature when you must move an organization from one CRM deployment to another CRM deployment. You will end-up with a new organization in the CRM deployment.
Be aware that if don’t have an Enterprise license then, once the import finishes, the existing organization will be deleted (unregistered) from that CRM deployment. That will happen because only the Enterprise license allows you to have more than one organization in that deployment. The existing organization database won’t be deleted though, so you can always Import it back in the same or other CRM deployment.
Deployment SDK does not support Import Organization.