Software

Various Possible Scenarios During D365 Upgrade to Business Central

Scenarios During D365 Upgrade to Business Central
Written by Micah Phillips

The entire process of D365 Upgrade to Business Central can be quite a complicated one if not handled properly. The upgrade process is dependent on various factors such as the experience of the implementation partner, whether you wish to have BC deployed on-premises or on cloud, how old your version of NAV is and how many times you got your solution customized and upgraded.

Ultimately, a D365 Upgrade to Business Central comes down to whether you want to upgrade to an online version or on-premises. Depending on this, various scenarios arise which need to be dealt with in order to make the upgrade a successful one. Depending on which version you upgrade from, you may have to convert or migrate the existing help for your solution.

What happens when you do a D365 Upgrade to Business Central Online?

The path to upgrading to BC Online depends a lot of the current solution you use. The nature of online services these days is such that in most cases, the matter is more about migration than it is about upgradation. At the core of the issue, the main task in hand is to import existing data to an empty company in a Business Central online tenant.

If you happen to upgrade from NAV to BC Online, then it is fully supported provided you consider a few things. End users can upgrade to Business Central online from supported versions of Dynamics NAV on-premises provided their application customization is handled by extensions. Data from tables with code customizations cannot be carried forward from Dynamics NAV. The process has been divided into 2 parts:

  • The first part involves converting non-standard functionalities and customizations into apps and per-tenant extensions.
  • The other part comprises running the cloud migration tool and then switching to using Business Central
    Online going forward.

While upgrading to BC Online, you will be prompted to Set up a company based on questionnaires. In such a case, you will have to Use RapidStart Services.

RapidStart Services is a tool designed to shorten deployment times to improve quality of implementation, introduce a repeatable approach to implementations and enhance productivity by automating and simplifying recurring tasks.

The tool helps gain an overview of the setup process of your new company by providing a worksheet in which one can set up tables often involved while configuring new companies. In the process, one ends up creating a questionnaire to guide customers through the collection of setup information. Most importantly, RapidStart Services prepares you with default setup data that can be fine-tuned and customized.

During the upgradation process, if the system prompts you to import data from any other Finance system, then you must use Excel or Configuration packages to import data. At the time of signing up for Business Central, end users are given the option to create an empty company to upload their own data and to test it as well. Depending on the finance solution they work on, end users can transfer information about customers, vendors, inventory and bank accounts. Additionally, master data and transactional data from other finance systems can also be imported based on default configuration package in Business Central.

During the upgradation, if the system prompts to import data from Dynamics GP, then the Data Migration Wizard must be used to import master data.

There is an assisted setup guide in Business Central that helps migrate data from Dynamics GP. Data can be migrated from Dynamics GP 2015 on SQL Server 2012 and from later versions of Dynamics GP and SQL Server.

When data is migrated from Dynamics GP, information such as chart of accounts master records, customer master records and outstanding transactions from the Receivables module, vendor master records and outstanding transactions from the payables module, inventory items, historical data from receivables payables, sales order processing, purchase order processing and inventory and checkbooks and outstanding transactions in bank reconciliation is migrated to Business Central Online.

At the time of upgradation, if the system prompts you to import data from Intuit QuickBooks, then you must use the data migration wizard to import master data. This extension makes it very easy to migrate customers, vendors, items and accounts from QuickBooks to Business Central.

You can export relevant information and then open an assisted setup guide to upload the Data to Business Central.

Information such as customers, vendors, items, chart of accounts, beginning balance transactions in General Ledger, on-hand quantities for inventory items and open documents for customers and vendors such as invoices, credit memos and payments can be imported from QuickBooks Online to Business Central.

What happens when you do a D365 Upgrade to Business Central On-Premises?

Again, the entire upgradation process depends on the version of Dynamics NAV that you are upgrading from and the degree up to which your solution differs from the standard version of Dynamics NAV. The main challenge during the D365 to Business Central On-Premises upgradation lies in converting the database to upgrading application code and data.

If a scenario arises where the need of the hour is a full upgrade to Business Central from either NAV 2015 or NAV 2016 or NAV 2017 or NAV 2018 or Business Central October 2018, then the upgrade can be done directly to the latest version of Business Central by either Upgrading the Application Code and Upgrading Data. It is mandatory to upgrade the application code first before one begins to upgrade the data.

To upgrade the application code, the end user first must merge from different versions of the application, a process known as code upgrade or application upgrade. There are many ways of upgrading the application code, and mind you, it can be an awfully lengthy process.

The first task is to install the prerequisites and tools. The next task is to prepare the application object text files.

The following tasks include merging versions, handling conflicts importing and compiling merged objects in empty databases, connecting the new business central server instance to the database, compiling all the newly imported objects and then choosing to synchronize later, checking and changing the application family and version, configuring pages and reports to be searchable, building object search index, transitioning the custom code from old codeunit1 to use the new implementation, exporting all objects, importing the upgrade toolkit objects and eventually publishing extensions.

Once the application code is upgraded, next comes upgrading the data. Data upgradation entails the use of data conversion tools to convert old data with the old version’s table and field structure so that it functions together with the new version’s table and field structure. Table objects and table data are majorly modified during data upgradation whereas objects such as pages, reports, code units and XML ports are upgraded as part of the application code upgrade process.

Once all necessary pre-requisites are taken care of, end users must prepare for a multi-level data upgradation process that involves Following

  • Creating a full SQL backup of old databases
  • uninstalling all extensions in old databases
  • uploading business central partner license to old databases
  • deleting all objects except tables in old databases
  • clearing server instance and debugger breakpoint records in old databases
  • converting old databases to Business Central
  • importing upgraded application objects to converted databases
  • connecting a Business Central server instance to converted database
  • compiling all objects in converted database
  • increasing the application version of converted database
  • running the schema synchronization on converted database
  • running data upgrade on converted database
  • upgrading Javascript based control add-ins to new versions
  • publishing and generating symbols for extensions
  • upgrading or repairing V2 extensions
  • publishing and installing local functionality extensions
  • importing permission sets and permissions
  • importing data encryption key
  • setting the language of customer database
  • updating the web server instance configuration file

If a scenario comes during the upgradation process which demands a full upgrade from NAV 2013 or NAV 2013 R2, then first end users must upgrade that version of NAV to NAV 2018 and then to Business Central, by first upgrading the application code as mentioned above and then upgrading the data as mentioned above.

If a scenario comes during the upgradation process which demands a full upgrade from NAV 2009 SP1 or NAV 2009 R2 or NAV 5.0 or NAV 4.0, then end users can follow two different paths depending on the version of NAV they currently work on. For NAV 5.0 and 4.0, they must first upgrade to NAV 2013. For NAV 2009 SP1 and NAV 2009 R2, they must first upgrade to NAV 2013 or NAV 2015.

Once they are on NAV 2013, they must then upgrade to NAV 2018 and then to Business Central by upgrading the application code and upgrading data. For those who are on NAV 2015, they can directly upgrade to Business Central by upgrading application code and upgrading data.

If a scenario arises which calls for a platform-only upgrade of Dynamics NAV or Business Central, then it calls for a technical upgrade. A technical upgrade is best dealt by a Microsoft certified technician, who is a subject matter expert in that area.