It seems my original post did not stick so here it is again......
Hello! I am currently working with a client who is looking at re-platforming multiple (but not all) applications into xRM. This will involve multiple projects. We are currently working on the first project and want to ensure we build a robust foundation for the re-platforming of the enterprise. Some of the other applications to be brought into xRM are related to the current application being worked on, some are different, and one is an enterprise application for core data that all xRM and non-xRM applications access. The client requires the end users to access xRM via Outlook. We discussed the following two options and came up with mostly pros for having separate instances. This is leading us in the direction of using one instance with multiple entities. But that raises concerns as well. Wondering what considerations and thought processes others have gone through in this process? Overall pro or con is User Management - depending on perspective it could be a pro or a con for either scenario. 1. Separate instances of xRMPros:- provides clarity with separation of applications for security and ownershipCons:- More extensive development required to meet reporting requirements as consolidation of data needed and potentially a BI tool could be required.- Data from the shared xRM application would need integration development to be accessed by the other xRM applications- Users accessing multiple applications would need to close Outlook and change their organization any time they wanted to access a different application.- Outlook can only be set to synchronize with one organization 2. One instance with many entities.Cons:- size of database may get quite largePros:- users do not have to change organizations when accessing multiple applications- can synchronize from multiple applications (this may be a con as could get confusing if data being synchronized not structured well)- reporting could be built using Advanced Finds, SSRS, and Dashboards within the instance, no additional BI tools required Questions:- How differentiate between applications if all in one instance? Potential thought is to use Business Unit. Allows for security to be maintained on the application but also allows shared access across applications for managers. The applications proposed for re-platforming are currently all internal IT ones so the Business Unit isn't planned to be used for representing the business reporting structure. But, that doesn't say another application could come into the folder later and want to use the structure.- Does anyone know if there is a limit to the number of entities that can be in one on-premise instance? CRM online limits to 300 custom entities. This is by no means a definitive list of impacts and we could spend days discussing them. Hoping that someone else has gone through the gyrations and can provide some insight or first hand wisdom. Thanks so much! Melanie