Skip to main content
Avalara Help Center

Migrate AvaTax data from Microsoft Dynamics GP to Microsoft Dynamics 365 Business Central

This topic describes the migration of Avalara data from Microsoft Dynamics GP to Microsoft Dynamics 365 Business Cental.

If your business uses 2015 (with SQL Server 2012 and later) versions of Microsoft Dynamics GP and SQL Server and you're switching to Microsoft Dynamics 365 Business Central 2020 release wave 2 or later, migrate your transactional and non-transactional data to set up your reports in Microsoft Dynamics 365 Business Central.

We recommend you first migrate a test environment before attempting to migrate a live environment. It's also a good idea to make a backup of the database you're migrating, just in case something unexpected happens.

There are tools available to help you make the transaction from Microsoft Dynamics GP tables to Microsoft Dynamics 365 Business Central. You can opt for “Data Migration Setup” to get step-by-step instructions. Or, you can go for Azure Data Lake to proceed with the migration. If you migrate using Azure Data Lake, then click here.

We can only migrate the following data/records from Microsoft Dynamics GP:  

  • 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
  • Checkbooks and outstanding transactions in Bank Reconciliation

Steps to Migrate

This section explains the steps to migrate GP tables and Avalara tables from Microsoft Dynamics GP to Microsoft Dynamics 365 Business Central cloud version.

Migrate GP Tables

Microsoft introduced integration run time software that automatically migrates Microsoft Dynamics GP tables to Microsoft Dynamics 365 Business Central version.

The following data will be migrated:

  • Customer Tax Schedule ID/Customer Address Tax Schedule ID
  • Item Tax Code Mapping

Note: Migration support is currently available in the United States, Canada, United Kingdom, and Australia.

Migrate Avalara tables

In Microsoft Dynamics GP, you can validate and export the following Avalara master data tables:

  • Item Tax Code Mapping
  • EUC Codes
  • Customer EUC Mapping
  • Item UPC Mapping
  • Customer mapping (AvaTax / Tax liable)
  • Vendors use tax assessment mapping

To Migrate Avalara Data tables from Microsoft Dynamics GP to Microsoft Dynamics 365 Business Central you must export the Data tables into the template.

Before you begin

If you migrate using Data Migration Setup, then:

  1. Log in to Avalara and go to Settings > Integrations.
  2. Select AvaTax Data Migration Tool to download the zipped folder containing three files:
  3. Unzip the folder.

Export Data Tables from GP

You can follow either one of the below options and export the Avalara data tables into the Microsoft Excel:

  • Smart List Solution
  • SQL Stored Procedure

Export using Smart List solution

If you do not have a smart list solution in Microsoft Dynamics GP, you can export your data using Export using SQL stored procedure.

Follow the steps to export Avalara data table into excel:

  1. In Microsoft Dynamics GP, import the AvaTax_GP_to_BC_MigrationTool.xml file from your smart list solution.
  2. You can see the Avalara folder with the below subfolders, you can select each folder and validate the data to be migrated:
    • AvlaraCustEUC
    • AvalaraEUC
    • AvalaraItem
    • AvalaraItemUPC
    • AvalaraTaxSchIDCust
    • AvalaraTaxSchIDCustAddress
    • AvalaraVendorCUT
  3. After you validate the data, click Export option and export to the template provided (AvalaraDataMigrationTemplateforGPtoD365BusinessCentral.xlsx).
  4. Save the excel sheet in your drive.

Note: In AvalaraItem, you have to modify SmartList and update "User Category Value" field as per AvaTax Configuration Field value (Path: AvaTax Configuration → General → Tax Code Mapping - fields’ value

Export using SQL stored procedure

You can use SQL stored procedures to extract data into the template file.

Follow the steps:

  1. Open both files in SQL 
  2. Execute the files and save data in the excel file AvalaraDataMigrationTemplateforGPtoD365BusinessCentral.xlsx

Import Avalara Data Tables to Microsoft Dynamics 365 Business Central

After the Microsoft Dynamics GP data has been copied into the AvalaraDataMigrationTemplateforGPtoD365BusinessCentral.xlsx file, open Microsoft Dynamics 365 Business Central and follow the steps:

  1. Type Configuration Packages into the search box and then press Enter.
  2. Navigate to Go to Pages and Tasks and click on Configuration Packages
  3. On Configuration Packages, click on the Process tab, and then click the Import Package
  4. Select the Avalara provided AvalaraRapidStartPackageforGPtoD365BusinessCentral.rapidstart package file.
  5. Select the Package tab, and then select the Import from Excel
  6. On VIEW – CONFIG. PACKAGE IMPORT PREVIEW, scroll down and select the required New Package check box, and then click the Import option to import the selected package(s).
  7. After the package is imported successfully, click the Process tab, and then click Apply Package
  8. Click Yes to migrate the data.

Avalara Tables in Microsoft Dynamics 365 Business Central Post Migration

After successful migration, you can see the corresponding Avalara tables from Microsoft Dynamics GP migrated to respective tables in Microsoft Dynamics 365 Business Central as shown below:

Avalara Table Name in GP Avalara Table Name in BC

AVAENTITYUSECODE

AVAEntityUseCode.Table.al

AVA_CUST_ENTITY_CLASS

AVACustEntityClass.Table.al

AVAUPC

AVAItemUPCMAP.Table.al

AVAVENDO

AvaVendorExt.Table.al