Moving from CRM 2016 to 365...

(1) Share

Report

Posted on by USA80

Hello,

My company currently has CRM 2016 on prem and we are moving to 365 on prem. I have my servers ready for the setup, but I want to make sure I take the correct steps to do the install correctly before I mess something up. Any insight you can share is greatly appreciated. Not only on the install but also on getting the database over to be used with 365.

Thank you in advance.

*This post is locked for comments

I have the same question (0)

All responses (15)

Answers (0)

Suggested answer

Mahadeo Matre 17,021 on at

Like (0)

Report

Hi,

Are you doing fresh installation of D365 or you are upgrading.

If you are upgrading then need not to worry about.. just install updates as you normally installs..Update will changes CRM 2016 to D365

Was this reply helpful? Yes No
USA80 26 on at

Like (0)

Report

This will be a fresh install

Was this reply helpful? Yes No
Suggested answer

Mahadeo Matre 17,021 on at

Like (0)

Report

Hi,

As you are using CRM 2016, you might be following some predefined steps.

Generally before installation of CRM make sure you have all service accounts created and has required permissions as per Microsoft recommendation.

then based on your organization load / data decide how many servers you want for CRM. do it need load balancing etc.

You can follow installation guide

www.microsoft.com/.../details.aspx

also check following link for all details of on-premise deployment

docs.microsoft.com/.../on-premises-deployment-landing-page

Was this reply helpful? Yes No
awalters 3,079 on at

Like (1)

Report

When you're saying 365, do you mean version 9.0? Or 8.2 (they changed the name before 9.0)? If you're referring to 9.0, be aware there's currently a bug that prevents you from updating any organization from a previous version into 9 on-premise. They supposedly have a fix but it hasn't been released yet.

Was this reply helpful? Yes No
USA80 26 on at

Like (0)

Report

Yes, I mean the latest release of 365...so looks like 9.0 for on prem. So if I install 8.2 as a fresh install will that work?

Was this reply helpful? Yes No
awalters 3,079 on at

Like (0)

Report

Migrating your org to a fresh install of 8.2 will work. It will not yet work for 9.0, until they release an update. (Supposedly they have the fix working, and they may have given hotfixes to a few people from what I'm hearing, but there's no public release date on it just yet.)

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

I agree with Allison.

For all those thinking of migration to V9 for Production. Please do not. Even a stock (Blank slate for testing) organisation will never migrate without workarounds. I have had to rollback my development servers. Hope this is useful advise to those of you out there.

I'd wait till Microsoft's release is tested without errors before proceeding. Not 3 workarounds that I had to go through. 1 supported and 2 suggested by the community.

Was this reply helpful? Yes No
USA80 26 on at

Like (0)

Report

Where can I get the install for 8.2 and install instructions?

Was this reply helpful? Yes No
Suggested answer

Abarao Bhople 445 on at

Like (1)

Report

Hello USA80 ,

Considering your CRM2016 setup is production environment.

to upgrade the same with Dynamics365 you have a below options.

1) In Place Upgrade. (on Same server)

To upgrade by this approach you need to take Database backup MSCRM_Config and your organization DB first.

then install "CRM2016-Server-KB3205084"

this update will rebrand your crm2016 to Dynamics 365

you will see the changes , your product has been converted to Dynamics365.

Need to upgrade Reporting extension as well "CRM2016-Srs-KB3205084-ENU-Amd64" and

remain products Eg. CRM Email Router ...

once you have completed above installation , need to apply below updates in sequence.

it will bring your deployment to Dynamics 365 latest updates 8.2.3 after installtion of KB4467675.

KB4013759 (Dynamics 365 Update 2.1)

KB4046795 (Dynamics 365 Update 2.2)

KB4467675 (Dynamics 365 Update 2.3)

2) Side by side Migration. ( Recomended by microsoft ) on seprate new server

It will not hamper your production (current) enviroment.

Restore your production database and then start installtion of CRM2016-Server-KB3205084 need to follow below steps

this KB3205084 update will rebrand your crm2016 to Dynamics 365

you will see the changes , your product has been converted to Dynamics365.

Need to upgrade Reporting extension as well "CRM2016-Srs-KB3205084-ENU-Amd64" and

remain products Eg. CRM Email Router ...

once you have completed above installation , need to apply below updates in sequence.

it will bring your deployment to Dynamics 365 latest updates 8.2.3 after installtion of KB4467675.

KB4013759 (Dynamics 365 Update 2.1)

KB4046795 (Dynamics 365 Update 2.2)

KB4467675 (Dynamics 365 Update 2.3)

Hope this will help you.

Thank you .

Abarao Bhople

Was this reply helpful? Yes No
USA80 26 on at

Like (0)

Report

I have a new server, and will be doing a fresh install. So it looks like I need to install CRM 2016 first and then apply patches to get to CRM 365. With that being said....what should I install for CRM 2016 on the new server first? Should I be running CRM2016-Server-ENU-amd64 install?

Was this reply helpful? Yes No