Skip to main content

Using SCRIBE Online To Migrate From CRM 4.0 to Dynamics 365

Recently I had a client that needed to be migrated from CRM 4.0 on-premise to Dynamics 365 online.  First, I want to say that we opted to not do the upgrade to CRM 2011 on-premise to CRM 2013 on-premise to CRM 2015 on-premise to Dynamics 365 on-premise because the client wanted to start fresh with CRM customization's.  So personally, it would have been a waste of time to do that upgrade process.

The following issues where identified with the data migration:
1) CRM 4.0 is no supported by SCRIBE Online.
2) The server OS that CRM 4.0 and SQL Server ran on was not supported.
3) The version of SQL Server was no supported.

How am I going to migrate this data? Hmm.....

The solutions:
1) The RDP Terminal Server I am using has a supported server OS.
2) I am able to connect to SQL Server CRM 4.0 Database with ODBC.
3) Install SCRIBE On-Premise Agent on the Terminal Server and use the ODBC connector to retrieve the data.

By using the ODBC connector I could access the data in SCRIBE Online in a supported way.  Because of this approach the migration did run a little slower because I couldn't run multiple maps at the same time over the same ODBC connection, because it would throw a connection error.

One piece I was not able to migrate with SCRIBE Online was the attachments stored in CRM 4.0, which was about 80 GB worth.  I couldn't migrate these because of changes in how CRM stored them.  So to accomplish this I did the following:

1)  I downloaded this tools source code from GitHub.
2) I modified it to read a list of guids.
3) I exported a list of attachment guids to csv.
4) I modified the application to then download attachments and put them into one root folder and have subsequent folders in the root.  Each subsequent folder was a guid and inside that folder was the attachment.
4) I then use the Microsoft Dynamics 365 SDK to create a console application to upload the attachments to Dynamics 365 and re-link them to the parent record.

Once I made the code changes and wrote the application I the download and upload ran overnight.


Know you might be asking yourself, "How did you store 80 GB of attachments in CRM online?  Isn't that expensive?"  I will be posting a separate blog on that in my Dynamics 365 blog.
Labels:

Comments

Post a Comment

Popular posts from this blog

Power Pages Update Last Successful Login Using JavaScript and Power Pages API

 Recently while working on a Power Pages implementation for a client, I had the requirement to show the last time a user logged in on their profile page.  I thought this would be easy to do as there is already a field on the contact record for "Last Successful Login" (      adx_identity_lastsuccessfullogin).  This use to update when a user logged in, but it appears Microsoft has removed that automation. While searching I came across a few different ways of achieving this task.  One used application insights in Azure and another one used an HTTP endpoint setup in Power Automate.  I thought, this needs to be simpler.  What I came up with is to use Liquid with JavaScript to tell if a user is logged in or not.  Then use the new Power Pages api to update the logged in users contact record to mark the last time they logged in. Here is the approach I setup: 1) Make sure you turn on the api for contact in Site Settings. 1) Link to Microsoft Do...
100 comments
Read more

Validating User Input In CRM Portals With JavaScript

When we are setting up CRM Portals to allow customers to update their information, open cases, fill out an applications, etc. We want to make sure that we are validating their input before it is committed to CRM.  This way we ensure that our data is clean and meaningful to us and the customer. CRM Portals already has a lot validation checks built into it. But, on occasion we need to add our own.  To do this we will use JavaScript to run the validation and also to output a message to the user to tell them there is an issue they need to fix. Before we can do any JavaScript, we need to check and see if we are using JavaScript on an Entity Form or Web Page.  This is because the JavaScript, while similar, will be different.  First, we will go over the JavaScript for Entity Forms.  Then, we will go over the JavaScript for Web Pages.  Finally, we will look at the notification JavaScript. Entity Form: if (window.jQuery) { (function ($) { if ...
23 comments
Read more

Lookup In Select of URL For Power Pages

 While working on a Power Pages implementation I was consume the Power Pages API to get a Lookup table so I could show and hide information on the form using jQuery.  One issue I was having is I couldn't get a lookup field to return even though I had it as a field in the site setting for the table and included it in the my select statement in the URL.  I kept getting an `unexpected error occurred`. This issue is caused because lookup's are made up using 3 fields. 1) Formatted Value = The information you see in the lookup field (i.e. the record name) 2) Logical Name = The table the related record is a part of 3) Id = The id of the related record In the api there is a 4th field that is returned that is the Associated Navigation Property and it is the logical name of the lookup field. When setting up our select and even saying what columns can be returned in the API, we have to think how the OData endpoint will return the data to us.  ...
3 comments
Read more