Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
New organization in CRM RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    We currently have one organization in CRM that we are working with.  Based on your experiences what are the factors that play into making a decision to create another organization?  Just wanted to see how other people made the decision to create multiple organizations.

    Any insight will be helpful.

    Wednesday, April 24, 2013 5:33 PM

Answers

  • Question
    Sign in to vote
    2
    Sign in to vote

    Everyone should have at least three organizations: dev, test and production. On one of my current projects we have 12 non-production organizations.

    Beyond that, if you are considering separate production organizations for different divisions, there are lots of factors to consider and no right answers. I've done this kind of analysis for several enterprise customers.

    Here are some factors that drive a single org:

    • Overlap in customers
    • A good data warehouse that can provide a summary of activity from the other CRM systems
    • CRM for Outlook can only sync with a single organization, so that's often a factor

    Here are some factors that drive multiple orgs:

    • No overlap in customers
    • Overlap in use of system entities (e.g. two divisions need to use opportunities or cases for quite different purposes)
    • Global deployments in different timezones

    What is driving you to consider multiple orgs?

    Neil Benson, CRM Addict and MVP at Slalom Consulting. Find me on Twitter. Join over 20,000 other CRM professionals on the Microsoft Dynamics CRM group on LinkedIn.

    Thursday, April 25, 2013 5:16 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Always the best practices is keep separate organization for development, live, test, backup. Dont do everything in the same organization.

    For each project create one new organization, because each client will have different requirement and business process.

    Keep one organization with base product without any customization if any new update installed you can find out what are the features added in base product.

    Thanks & Regards, MS CRM Consultant, V.Surya. My Blog: http://inventcrm.wordpress.com/


    • Edited by SuryaMSCRM Thursday, April 25, 2013 5:14 AM
    • Proposed as answer by SuryaMSCRM Thursday, April 25, 2013 5:15 AM
    • Marked as answer by Mego123 Thursday, April 25, 2013 2:57 PM
    Thursday, April 25, 2013 5:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Creating number of  organizations in CRM  is making an safe to place to land ourself in case of any difficulties.Its always preferable to maintain minimum of 3 organizations i.e., for R&D,Testing and live  and also maintain an base organization where none of the customization should be done .While importing any other solution if it gets corrupted then we can import the base product solution.

    Best Regards

    Meenakshi

    • Proposed as answer by meenakshi Patnala Thursday, April 25, 2013 6:17 AM
    • Marked as answer by Mego123 Thursday, April 25, 2013 2:57 PM
    Thursday, April 25, 2013 5:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I don't think that mere existence of more organizations on the same server consumes more resources in practice. After all it's only more databases on the SQL Server unless someone's actively using the dev & test organizations. Of course you can't conduct any performance related testing on the same server or debugging without affecting the production CRM. Another limitation is that you don't have any place to test the impact of Update Rollups that get applied to the application server. Especially with changes like the UR12 cross-browser support this can be problematic.

    Jukka Niiranen - My blog: Surviving CRM - Follow @jukkan on Twitter

    • Marked as answer by Mego123 Friday, April 26, 2013 2:40 PM
    Thursday, April 25, 2013 7:26 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Always the best practices is keep separate organization for development, live, test, backup. Dont do everything in the same organization.

    For each project create one new organization, because each client will have different requirement and business process.

    Keep one organization with base product without any customization if any new update installed you can find out what are the features added in base product.

    Thanks & Regards, MS CRM Consultant, V.Surya. My Blog: http://inventcrm.wordpress.com/


    • Edited by SuryaMSCRM Thursday, April 25, 2013 5:14 AM
    • Proposed as answer by SuryaMSCRM Thursday, April 25, 2013 5:15 AM
    • Marked as answer by Mego123 Thursday, April 25, 2013 2:57 PM
    Thursday, April 25, 2013 5:13 AM
  • Question
    Sign in to vote
    2
    Sign in to vote

    Everyone should have at least three organizations: dev, test and production. On one of my current projects we have 12 non-production organizations.

    Beyond that, if you are considering separate production organizations for different divisions, there are lots of factors to consider and no right answers. I've done this kind of analysis for several enterprise customers.

    Here are some factors that drive a single org:

    • Overlap in customers
    • A good data warehouse that can provide a summary of activity from the other CRM systems
    • CRM for Outlook can only sync with a single organization, so that's often a factor

    Here are some factors that drive multiple orgs:

    • No overlap in customers
    • Overlap in use of system entities (e.g. two divisions need to use opportunities or cases for quite different purposes)
    • Global deployments in different timezones

    What is driving you to consider multiple orgs?

    Neil Benson, CRM Addict and MVP at Slalom Consulting. Find me on Twitter. Join over 20,000 other CRM professionals on the Microsoft Dynamics CRM group on LinkedIn.

    Thursday, April 25, 2013 5:16 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Creating number of  organizations in CRM  is making an safe to place to land ourself in case of any difficulties.Its always preferable to maintain minimum of 3 organizations i.e., for R&D,Testing and live  and also maintain an base organization where none of the customization should be done .While importing any other solution if it gets corrupted then we can import the base product solution.

    Best Regards

    Meenakshi

    • Proposed as answer by meenakshi Patnala Thursday, April 25, 2013 6:17 AM
    • Marked as answer by Mego123 Thursday, April 25, 2013 2:57 PM
    Thursday, April 25, 2013 5:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks everyone for all your insights.  I was considering multiple orgs for different business units at my company but since there will be overlap in customers as well as a need to use the outlook client, I will stick with one organization. 

    Form the comments, it looks like some people are using a single installation of CRM to manage the DEV, Test and Production environments via multiple organizations.  With this set up, a production system is going to be consuming the same server resources as DEV and Test and won't that raise a performance issue?

    Thursday, April 25, 2013 2:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I don't think that mere existence of more organizations on the same server consumes more resources in practice. After all it's only more databases on the SQL Server unless someone's actively using the dev & test organizations. Of course you can't conduct any performance related testing on the same server or debugging without affecting the production CRM. Another limitation is that you don't have any place to test the impact of Update Rollups that get applied to the application server. Especially with changes like the UR12 cross-browser support this can be problematic.

    Jukka Niiranen - My blog: Surviving CRM - Follow @jukkan on Twitter

    • Marked as answer by Mego123 Friday, April 26, 2013 2:40 PM
    Thursday, April 25, 2013 7:26 PM