Building the tower of Babylon – Importing CRM Organizations with different base Language
Consider the following scenario:
An organization has two different implementation of Microsoft Dynamics CRM 3.0 and plan to upgrade both to Microsoft Dynamics CRM 4.0 as two separate organizations in a multi-tenancy deployment.
Each Microsoft Dynamics CRM 3.0 implementation has a different base language, one has English and the other has Hebrew.
Is this feasible at all? Can a multi-tenancy deployment host two implementations with different base languages, upgraded from version 3.0?
I encountered a similar scenario lately and since I could not find a straight answer, I conducted a little experiment. It involved two major steps:
- Upgrade both implementations from version 3.0 to version 4.0. One implementation was upgraded using an Enterprise license (The English base language implementation)
- Using the Deployment Manager, import the The Hebrew base language implementation database into the The English base language implementation (Enterprise license).
Surprisingly, this works. A multi-tenancy deployment can host two upgraded implementations with different base languages. I assume it can support more than two different base languages, but it is up to you to experiment with such shenanigans.