Customer Engagement & Dynamics CRM Forum

Expand all | Collapse all

Migration of v9 instance to a new tenant

  • 1.  Migration of v9 instance to a new tenant

    GOLD CONTRIBUTOR
    Posted Jan 03, 2019 04:59 PM
    Hello friends!

    I am working with a company who has a V9 instance of Dynamics 365 running on one tenant and all of their exchange and O365 accounts setup on a different tenant.

    We'd like to have all of the users on a single tenant and need to move our v9 Dynamics instance to the tenant with the O365 accounts.

    I've used DataMigrationUtility.exe to build a schema of the data and have been successful in exporting the data I want to move. However, I still need to export the rest of the customizations and have been struggling with custom fields and items added through a few managed solutions that I no longer have access to.

    If I can identify all of the fields and make new ones that match the data in the schema, even if they aren't from the same managed solution, will that work to import everything?

    Are there any strategies or has anyone written a guide so I can better understand the challenges in moving data and customizations between tenants? I feel like I'm hitting a ton of roadblocks and could really use some help to make this move with confidence.

    Thanks,
    Nick

    ------------------------------
    Nicholas Hance
    Reenhanced
    Green Lane PA
    ------------------------------
    CRMUG Summit - Post


  • 2.  RE: Migration of v9 instance to a new tenant

    SILVER CONTRIBUTOR
    Posted Jan 03, 2019 05:56 PM
    Nick, I believe you can just open a ticket with Microsoft Support and they'll move it for you

    ------------------------------
    Edrei Mpanduki
    CRM Technical Analyst
    Fender Musical Instruments Inc
    Scottsdale AZ
    ------------------------------

    CRMUG Summit - Post


  • 3.  RE: Migration of v9 instance to a new tenant

    SILVER CONTRIBUTOR
    Posted Jan 04, 2019 03:30 AM
    Hi Nicholas

    Two options:

    1. Create an entirely new environment and then import your customisations and migrate your data manually
    2. Ask Microsoft to move the Dynamics instance to new tenant

    Point 2 sounds easy enough but this is something we're exploring at the moment due to a takeover and, in short, it looks like it could be a bit of a pain.  Very important point on this though - it is not currently possible for Microsoft to migrate a V9 instance between tenants.  The last conversation we had with Microsoft in early December said they do not expect the tool to migrate V9 instances between tenants to be available until the end of March 2019 at the very earliest.

    Anyway, here's what Microsoft will reply with when you raise a ticket:

    Hello <INSERT NAME>,



    My name is <SE Name> and I am with the Microsoft Dynamics 365 Team and I will be your point of contact for this case.  I see you have submitted a request for a Tenant to Tenant migration.  Please begin by providing the below Needed Information.  Please read carefully.  This is required to proceed with the migration.  If you would like we can schedule a time to discuss.



    Needed Information:

                   *Please note that Tenant to Tenant Migration requests for 9.0 as a source and destination are not supported at this time, no exceptions.

    *Tentative time of availability for V9.0 Tenant to Tenant Migrations is end of March 2019.



    Are you a Global Administrator of both Source and Destination Tenants?  If not then please be sure to contact the Global Admins to continue with the migration.



    Source tenant domain and its Region (example: EMEA, NA, APAC): <should end with .onmicrosoft.com>

    Enter Domain

    Enter Region

    Destination tenant domain and its Region (example: EMEA, NA, APAC): <should end with .onmicrosoft.com>

    Enter Domain

    Enter Region

    Is your source and/or destination on version 9.0?  If so, please note that Tenant to Tenant Migration requests for 9.0 as a source and destination are not supported at this time, no exceptions.



    Is the Source Tenant coming from APJ and the Destination tenant in OCE?

    Y/N

    Does the Destination tenant have a valid Dynamics 365 subscription?

                        Y/N

    Does the Destination tenant have enough available user licenses?

                        Y/N

    Does the Destination tenant have enough Dynamics 365 Instance licenses?

                        Y/N

    Does the Destination tenant have enough Dynamics 365 storage available for the instances being migrated?

                        Y/N



    Source Dynamics 365 URL(s):

                  Enter Source Organization URL(s)

    NOTE:  Source organizations will be completely removed and after migration you can only access these orgs via the destination tenant



    Destination Dynamics 365 URL(s):

    You will need to create a temporary instance or instances in the destination tenant, depending on how many source instances you are migrating.  Source and destination instances need to be 1:1.  They should also be 8.2.2 or below versions (9.0 temp destination orgs will not work)

                  Example:  If source org is 'test.crm.dynamics.com' then the destination temp org could be named 'testTEMP.crm.dynamics.com'



    Provide User Mapping file (User Mapping steps below):

                  Attach to email

    Customer contact:

               Name: Enter in details

    Email: Enter in details

    Phone: Enter in details

    Do you have Voice of the Customer installed?

                  Y/N

    Once we have validated the user mapping file(s) then we will reach out to you to schedule a date for tenant merge to take place.  Do not decide on a date until we have validated the User Mapping files, this is important.



    *NOTE: You might need to reconfigure some applications after the Tenant to Tenant Migration such as the Microsoft Dynamics 365 Outlook client, Server Side Sync, SharePoint Integration, etc.



    Dynamics 365 User Mapping File steps:



    ****Each org should have a separate User Mapping CSV file

    1.       Open Microsoft Edge browser.

    2.       Navigate to org URL of source instance.

    3.       Open Advanced Find window.

    4.       Look for: Users

    5.       Use Saved View: Full Access Users

    6.       Click Edit Columns.

    7.       Remove all columns except Full Name.

    8.       Add Columns: Windows Live ID

    9.       Click OK, then Results.

    10.   Select all records > click on 'Export Users' in the ribbon > choose 'Static Worksheet (Page only)'

    11.   Perform the same steps above for the Destination org, you should now have two Excel sheets (one for source and one for destination)

    12.   Open the files for editing

    13.   Starting with the Source Excel sheet, copy the records under 'Windows Live ID' column into Notepad (do not copy header)

    14.   Save the Notepad file.

    15.   Next, enter Destination 'Windows Live ID' (UPNs) in the same Notepad document to the right of the corresponding Source UPN, separating Source and Destination UPNs by a comma (,).  Example below:

    user001@source.com,user001@destination.com

    user002@source.com,user002@destination.com

    user003@source.com,user003@destination.com

    16.   Save file as CSV.



     Please let us know if you have questions as you get going on the process.



    Common validation errors:

    ·         User does not exist in organization – Check for misspellings/typos in mapping file and for user existence in specified tenant.

    ·         User already exists in organization – Change UPN of specified user in destination tenant or omit from mapping file if needed.

    ·         Inadequate storage – Customer needs to order additional storage licenses





    Below are the high level steps as guidance. If the above information in red is all correct then reply to this email.  Upon receiving this confirmation from you, a Microsoft Support Engineer (in this case being me) will then engage further to complete a thorough review and advise on next steps in preparation for the migration.



    High Level Process Steps:

    1.       Customer provides the above information

    2.       If you do not have a Dynamics 365 subscription and/or trial under destination tenant, then you will need to have one created.

    *Customer might need to purchase a new Dynamics 365 subscription within the destination tenant (convert to paid), if not already done.

    3.       We need to confirm that the destination tenant has equal or higher number of active user licenses, D365 Instance licenses for instances being migrated, and equal or higher storage as the source tenant.

    4.       Microsoft Support Engineer will work with the customer to map all users and our Operations team runs a validation. If errors are found, we will work with Customer to resolve.

    5.       Once User Validation has been completed, the Microsoft Support Engineer and Customer confirm a date/time for tenant merge to take place. Microsoft Support Engineer and Customer confirm a date/time for tenant merge to take place.

    6.       Our Operations team performs the tenant merge in line with agreed upon scheduling (barring any unforeseen issues).

    7.       Microsoft Support Engineer confirms with customer that merge is complete and org(s) in destination are available.

    8.       The Customer and/or TAM (with assistance from the Microsoft Support Engineer if needed) works with billing to cancel and/or credit previous subscription if needed

    9.       At this point the migration is successful and we can move forward to close the case



    *NOTE: You might need to reconfigure some applications after the Tenant to Tenant Migration such as the Microsoft Dynamics 365 Outlook client, Server Side Sync, SharePoint Integration, etc.  If you run into any post migration issues then please create a new case and reference this one.


    ------------------------------
    Luke Sartain
    CRM Developer
    ICS Cool Energy Ltd
    Fareham
    ------------------------------

    CRMUG Summit - Post


  • 4.  RE: Migration of v9 instance to a new tenant

    TOP CONTRIBUTOR
    Posted Jan 04, 2019 04:08 AM
    Nicholas

    For items that were added by managed solutions and where you no longer have the managed solution files ,you will have to recreate those items (fields and so on) manually.

    Provided the relevant fields are present in the destination system, import will work regardless of how the fields were created.

    The best solution is for Microsoft to move/copy the database but as others point out that isn't an option at the moment.

    So you will need to migrate the data yourself. I recommend the KingswaySoft integration toolkit - you will need an instance of SQL Server Integration services to run it. But it is free to use for migrations.

    Manual migration can take a long time to set up and depending on the amount of data you have a long time to run. You have to be careful to migrate entities in the appropriate order. For example, migrate accounts before contacts before tasks.

    If you are not in a hurry, I'd suggest waiting a month or two to see if Microsoft starts offering the migrations again for version 9.0

    ------------------------------
    Feridun Kadir
    Principal Consultant, MVP
    Expert CRM Services Ltd
    Stansted
    ------------------------------

    CRMUG Summit - Post


If you've found this thread useful, dive deeper into User Group community content by role