web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Upgrading CRM 2015 on-premise to Dynamics 365 on-premise

(0) ShareShare
ReportReport
Posted on by

Hi,

I'm searching for some advices on this.
Will custom layouts work afterwards?
How will you recommend to upgrade it? It's a single CRM 2015 server, with MSSQL running on another server.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Andreas Cieslik Profile Picture
    9,267 on at

    Here is a general guide:

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

    What do you mean with custom layouts?

    You can do inplace upgrade if you have relatively new and performant server, otherwise use new servers.

    Check if all new system and software requirements are met by old or new system.

    Before upgrading always make full database backup of MSCRM_CONFIG and ORG_MSCRM databases.

    Then follow guide:

    technet.microsoft.com/.../jj612872.aspx

    upgrade to CRM 2016 and then the DYN365 2.1 update.

  • Community Member Profile Picture
    on at

    Thanks.

    We're using custom views / layouts for accounts and some other places. They might still work after the upgrade?

    It's running in Server 2012 R2, should be fine too? Otherwise, Server 2016 -> MSSQL 2016 -> migrate to CRM 2016?

  • Andreas Cieslik Profile Picture
    9,267 on at

    Yes they will still run. Server 2012 R2 is fine.

    You can refer to this compatibility list:

    support.microsoft.com/.../compatibility-with-microsoft-dynamics-crm-2016

  • Community Member Profile Picture
    on at

    What about the mail flow? Do we have to do any changes? Currently using an CRM Exchange e-mail profile for it.

  • Andreas Cieslik Profile Picture
    9,267 on at

    Server sync or email router?

    Exchange Server version?

  • Andreas Cieslik Profile Picture
    9,267 on at

    Generally there is no issue with it. Only for email router you need to update to CRM 2016 email router.

  • Suggested answer
    Community Member Profile Picture
    on at

    Hello PJMIT,

    Personally with my last upgrade we went with a new SQL server and a new Windows Server both running 2016 editions and found the upgrade process to be relatively painless. If you decide to take a similar route then the process would be to set up all of the required infrastructure on the new servers, take a full backup of the SQL database and migrate it to the new SQL server and then install Dynamics 365 and import an organisation from the SQL database on the new server.

    This allows you to have the choice of quickly utilizing the old organisation and gives total safety.

    Something to keep in mind is to ensure the new organization has a different unique Org ID otherwise you may run into issues with solutions such as PowerObjects.

    IFD setup can also be a pain, there's a great guide if you're not familiar with the process at this link - www.interactivewebs.com/.../how-to-set-up-microsoft-crm-2016-ifd-on-windows-2012-r2-server

    If you have any other questions I'd be happy to provide assistance or advice, feel free to contact me through here or my blog SPandCRM.com

    EDIT: to answer your other questions custom form layouts should work fine after the upgrade, and you shouldn't require any changes in exchange or CRM to get email syncing working again, however I'd suggest approving and re-testing all mailboxes to ensure they are working as intended. Also there is a bug for on-premise where business process flows will not appear correctly on existing records, if you encounter this I'll link you to a help article I've written to help with this.

  • Community Member Profile Picture
    on at

    Thanks for you reply!

    I've already build a new Server 2016, with SQL 2016.

    So the steps should be:

    1: Backup SQL database, import @ new SQL server

    2: Install CRM 2016 on Server 2016 - then what, so make it work as our current 2015 version?

    3: Update to 2.1 (Dynamics 2.1 on-premise)

    4: Testing

  • Community Member Profile Picture
    on at

    Basically from there ensure all of the DNS works correctly and set up Claims-Based authentication and internet-facing deployment if you're using that.

    This Technet article may help - technet.microsoft.com/.../hh699776.aspx

    This article covers IFD setup perfectly - www.interactivewebs.com/.../how-to-set-up-microsoft-crm-2016-ifd-on-windows-2012-r2-server

    If you've not done this before you should be able to use the old installation as a template of sorts to ensure you're setting things up correctly. Worst case scenario if you encounter any issues you can simply keep working on it until it works and once you're happy with it do an export of the latest CRM 2013 SQL database and re-import as a new organisation out of hours. We managed to perform the entire migration over a weekend once we were happy with the setup.

  • Community Member Profile Picture
    on at

    We do only use it internally, with webbrowser. And also the CRM client in Outlook.

    Again, how shall I 'connect' the new CRM to the old one, in order to get the current setup? Or is everything stored in the database? I must be missing something ...

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans