AXForum  
Вернуться   AXForum > Microsoft Dynamics CRM > Dynamics CRM: Blogs
All
Забыли пароль?
Зарегистрироваться Правила Справка Пользователи Сообщения за день Поиск Все разделы прочитаны

 
 
Опции темы Поиск в этой теме Опции просмотра
Старый 26.07.2019, 18:12   #1  
Blog bot is offline
Blog bot
Участник
 
25,459 / 846 (79) +++++++
Регистрация: 28.10.2006
crmtipoftheday: Tip #1285: Dynamics Divorce
Источник: https://crmtipoftheday.com/1285/dynamics-divorce/
==============
We are selling part of our business and want to split our environment into a separate environment and move to another D365 tenant. How do I do that?

splitting up
Recommendations

Here’s my recommendation for splitting on environment into two:
  1. Identify the customer and related records that are shared by both groups. These are the joint custody children and pets in the D365 divorce. Flag these records (can use a custom field).
  2. Start by separating the two groups into different business units—this lets you separate the records before deleting them out and test to ensure that the split is as clean as possible.
  3. Make a copy of the environment.
  4. In the target environment, delete the records in BU1 except for the records flagged in step 1—I would do this first because you can go back and redo if you mess up. Then test.
  5. In the source environment, delete the records in BU2 except for the records flagged in step 1.
  6. Work with Microsoft support to move the new environment to the other tenant
Other considerations
  1. Integrations need to be adjusted to only integrate the appropriate records
  2. Third party ISV solutions may need to be reconfigured/updated and licensing adjusted—the new company will need to license D365 and any third party solutions included.
  3. Under the new licensing model, Microsoft is enforcing functionality via licensing. If, for example, configuration includes field service but the new organization won’t be using field service and users aren’t licensed for it, you will likely need to remove some Microsoft solutions after you copy the environment.
Summary

Separate the data and copy before moving. This minimizes the risk as it can be tested and rolled back before burning the ships.



Источник: https://crmtipoftheday.com/1285/dynamics-divorce/
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
 

Похожие темы
Тема Автор Раздел Ответов Посл. сообщение
crmtipoftheday: Tip #1041: Make Dynamics 365 data import less rigid Blog bot Dynamics CRM: Blogs 0 11.12.2017 03:41
crmtipoftheday: Tip #1029: Get notifications about Dynamics 365 service issues Blog bot Dynamics CRM: Blogs 0 23.11.2017 08:11
crmtipoftheday: Tip #1019: Understand decimal precision in Dynamics 365 Blog bot Dynamics CRM: Blogs 0 09.11.2017 08:14
crmtipoftheday: Tip #1006: Case management vs. ticket management in Dynamics 365 Blog bot Dynamics CRM: Blogs 0 23.10.2017 19:12
crminthefield: Podcast and Overview: Microsoft Dynamics CRM 2011 Update Rollup 12 Blog bot Dynamics CRM: Blogs 0 30.01.2013 01:11
Опции темы Поиск в этой теме
Поиск в этой теме:

Расширенный поиск
Опции просмотра

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.
Быстрый переход

Рейтинг@Mail.ru
Часовой пояс GMT +3, время: 11:57.
Powered by vBulletin® v3.8.5. Перевод: zCarot
Контактная информация, Реклама.