Migrating On-Premise Dynamics 365 Business Central to Cloud

A simple and easy look into how you can migrate On-Premise Dynamics 365 Business Central to Cloud. Using Business Central 14 on-Prem and Business Central 16.2 Cloud, we walk you through 5 easy steps on how you can do it yourself.
Visit our website for more information: www.sabrelimited.com
Stay up to date with the latest news:
Facebook: / sabrelimited
LinkedIn: / sabre
Twitter: SabreERP/with_rep...
#BusinessCentral #SabreLimited #Dynamics365 #Dynamics365Cloud #BusinessCentralMigration

[@rumalmadawa3728]

Thanks for the sharing your knowledge with us. Great video🙂

[@scottsteffen1434]

Great walkthrough of this process. I have an issue with my migration from GP to BC, wondering if you might have any insight. When attempting to migrate from GP 18 to BC (SaaS), nothing is migrated to the BC master records (Customers, Vendors, COA...). The GP master records have been migrated to BC in tables 'GP Account', 'GP Customer', 'GP Vendor'. Any ideas why or even where to look?

[@Sabrelimited]

Hi Scott. Sorry but we have not done any GP to BC migrations. It sounds like perhaps there is an extra step that needs to be done that moves the data from the GPxxx tables to the "standard" tables? Check and see if the GP Migration Wizard has any steps after the data is transferred.

[@IvanLabrador]

Hi, great video. The transaction history (Posted Sales Invoices, etc) is migrated too?

[@Sabrelimited]

Yes - all the “base” NAV data is migrated from the local SQL database to the cloud AZURE SQL database for the new tenant. All your data is moved, history and all.

[@IvanLabrador]

@@Sabrelimited Hello, I hope you are well. I wanted to ask you if you know, I migrated from BC14 on premises to BC18 on Cloud, all the information was passed, except the custom fields (information in extended tables) and the new tables. What could be happening? Thank you.

[@robertjolliffe]

@@IvanLabrador Hi, You need to create a custom extension and install it in your on-prem (no C/AL code) and the same extension in the cloud. If you don’t do that you can’t migrate custom data. C/AL customizations are skipped.

[@IvanLabrador]

@@robertjolliffe Thank you very much for responding and for your time.

[@Sabrelimited]

Yes, everything is transferred from all the tables in the source database to the target in the cloud.

[@user-xi9jv7kh1v]

Hello. WHAT HAPPEN IF THE TABLES HAS EXTENSION. HOW TO DO MANAGE? I TRY TO MIGRATE AND MIGRATED ALL THE FIEDS, EXCEPT THE EXTENSION FIELDS

[@Sabrelimited]

If you have a table with extensions in BC 14, then you need the same extension with the same field names in BC cloud. I think the GUID of the Extension needs to be the same also. If you look in SQL - and add an extension to ITEM adding a field called MyField you will find a new table called something like {company name}$911be045-baf6-466d-9828-af1654561db5$ITEM Where 911be045-baf6-466d-9828-af1654561db5 is the extension ID. it is going to copy the data from the table with that name on-prem to the table with that name in the cloud. You can see these table names in the Cloud Migration Manager. If the same extension ID with the same table extensions exist in the cloud it will work.

[@Sabrelimited]

Oh - and by the way - based on what I wrote below that means you need to take all C/AL custom fields and create Table Extensions for all of them. That is actually the time consuming part of the upgrade.

[@user-xi9jv7kh1v]

​@@Sabrelimited thanks for the reply. I created the extension for the cloud, but my version 14 comes from the nav version, it has the nav structure, for example company information, its extension is included in the same name table.