Migration: Dynamics CRM 2011 on premise to CRM Online 2013 (preferably to CRM Online 2015)

(0) Share

Report

Posted on by meenxip

I need some of guidance on how difficult it will be to migrate from Dynamics CRM 2011 on premise to CRM Online 2013 (preferably to CRM Online 2015)

some key points to note are:

We need CRM to be able to create objects in our Office 365/SharePoint online instance (Mainly folders and sites)
We would need to migrate the existing data to the cloud if it is feasible
As part of the upgrade/move we would like to incorporate a number of high level business processes into CRM, as well as change some of the current functionality. we have some workflows, custom workflows, java scripts, custom entity, plugins

can you provide any documentation on how to migrate from Dynamics CRM 2011 on premise to CRM Online 2013 (or CRM Online 2015)

Any documentation on what limitation we will have on migration.

Thanks.

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (2)

Suggested answer

Mandar Joshi 2,116 on at

Like (1)

Report

Below links should help. Thanks!

technet.microsoft.com/.../hh699716.aspx

blogs.msdn.com/.../upgrading-dynamics-crm-2011-to-crm-2013.aspx

community.dynamics.com/.../microsoft-dynamics-crm-upgrade-from-crm-2011-to-crm-2013.aspx

Was this reply helpful? Yes No
Suggested answer

Bruno Lucas 5,421 on at

Like (0)

Report

Unfortunately on premises to on-line is more like a data migration. Unless you have a crm online account still on 2013 you will need to first upgrade your on premises to 2015.

SharePoint integration (if SharePoint online) its easier from online to online

the customisations can be migrated after the upgrade by exporting the default solution. but the data is more laborious.

Do you still have any customisation like JavaScript or Plugins using the old crm 4 endpoints? it would work on 11 but not anymore. Make sure you also understand the limitations of a sandboxed environment. if your crm has any special plugin that contains some third-party dll or perform some operation like writing files to the disk, it won't be possible online

www.dynamicscrmpros.com/microsoft-dynamics-crm-moving-premise-online-vice-versa

Was this reply helpful? Yes No
meenxip on at

Like (0)

Report

Thank you for your reply. "Unless you have a crm online account still on 2013 you will need to first upgrade your on premises to 2015."

I didn't understand this sentence. do you mean I should move from 2011 on premise to 2013 online and then its easier to move from 2013 online to 2015 online?

Was this reply helpful? Yes No
Bruno Lucas 5,421 on at

Like (1)

Report

It means that you can't purchase a crm online 2013 account. the only 2013 instances available are the customers that already had it since before the upgrade and requested to postpone the change.

if you have crm 2011 on premises, you need to upgrade it to 2015 on-premises (the customisations) before you can deploy it to online.

Was this reply helpful? Yes No
Verified answer

Bruno Lucas 5,421 on at

Like (1)

Report

Check this out. this article covers 4 and 11 to 13 but the process is basically the same

www.wave-access.com/.../migration-from-crm-4-crm-2011-on-premise-to-crm-2013-online.aspx

Scribe is expensive but delivers

http://www.scribesoft.com/webinar-migrating_from_dynamics_on-premises_to_online

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

Before I went on my current long-term project, I just did this exact thing for a former customer who was using CRM 2011. They needed to go to CRM 2015, but had custom business logic written against legacy web services in CRM 2011 and needed to upgrade or re-build many of that code. Further, they needed to change some of their business processes - over the years, surprise! they evolved/changed...

Normally when we do an upgrade we limit the scope of the upgrade to only the minimum required changes to reduce risk, but because I had worked with them before and understood what was implemented as well as what needed to change, we decided to include changes to logic as well as do the upgrade all in one iteration. We used something similar to the sure step rapid implementation methodology, and in 90 days we successfully went from a pre-UR12 CRM 2011 to CRM 2015 environment.

At a high level much of the configuration was done from scratch, retaining only the entities/attributes/relationships/optionsets that persisted in the new business model, and I fired up Visual Studio 2013 and using the SDK I connected to the legacy CRM 2011 system as a source, and CRM 2015 as a target and performed a top-down data migration translating data entity by entity in an agile manner with iterative data quality testing. My tool worked a lot like Scribe did, but I was in complete control of the back-end code and didn't have to call support if there was unexpected behavior so no need to wait for someone else to engage, bug fixing was close to us.

I think the keys to this are having a close relationship between the stakeholders who understand the business and the team responsible for executing the change, so lots of buy-in from sponsorship and no or few blocks.

If you need more detail on any of these high level points please contact me.

Cheers,

Michael D Mayo

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Michael,

I have do this exact same upgrade process and found your answer insightful. I'd be interested to know if you if you used any developer tools aside custom devs? Also if you could provide any more details on the process you followed that would great.

Thanks,

David

Was this reply helpful? Yes No
Suggested answer

SynchronicityAlex 20 on at

Like (0)

Report

Dynamics CRM On Premise to Online migration

http://www.synchronicity-systems.com/Echo

info@synchronicity-systems.com

Was this reply helpful? Yes No