Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Splitting Dynamics CRM...
Microsoft Dynamics CRM (Archived)

Splitting Dynamics CRM environment into separate systems

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

This is a really naive question as I have almost no experience with Dynamics CRM, so I am not sure if there is an good answer or not. I am doing a short write up about some work a company did to their CRM, and I have been given some bullet points with details. Most of it is fine but one is incomplete and I am trying to fill in the blanks with some plausible approaches. If a company had two different lines of business managed with CRM in a single environment and half of the company was sold, forcing them to separate the environment and data into two systems, how would you go about disentangling the functionality and data? Would a person likely just create two new solutions and start adding completely separate features, and then have to modify everything that is shared to remove references to the other line of business? Are there any general ideas or approaches one may have taken to resolve this? 

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Splitting Dynamics CRM environment into separate systems

    Thanks for the idea. Given my lack of experience actually using CRM I wasn't terribly comfortable using any of my own ideas. I think that will help though, give me enough to write a short paragraph with a plausible description. Worse case scenario they did something completely different and they will correct that paragraph.

  • Verified answer
    ashlega Profile Picture
    ashlega 34,475 on at
    RE: Splitting Dynamics CRM environment into separate systems

    Hi,

     off the top of my head.. It might be worth looking into the option of spawning a completely new CRM instance, deploying all the same configuration there, and, then, creating a data migration package that would only take the right half of the data to the new environment.

     From there, you can take your time to remove whatever customizations/configurations you don't need anymore.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans