Bewerken

Share via


Configure Dynamics GP company migration

The Business Central cloud migration tools for Dynamics GP include the GP Company Migration Configuration page. This page allows you to make global settings for all companies selected to migrate with the ability to update at a company level if necessary. For more information about the data that can be migrated, see Dynamics GP data migrated to Business Central online.

Complete this task after you set up cloud migration and before you replicate data.

For an overview of the full end-to-end process for Dynamics GP cloud migration, go here.

Prerequisites

Run cloud migration setup.

Get started

The GP Company Migration Configuration page opens automatically when you complete the Cloud Migration Setup assisted setup. You can also open the page by searching for and opening the Cloud Migration Management page and then selecting the GP Company Migration Configuration action.

Shows GP company migration configuration page

Once you have the GP Company Migration Configuration open, you can start to configure what data you to migrate by using the different sections of the page. The page enables you to configure the migration globally for all companies that you chose to migrate (using the upper sections of the page) or on a per-company basis using the Per Company section.

You don't necessarily have to make any changes on this page. However, you're required to make changes if there's more than one segment in Dynamics GP because you must indicate which segment to use the global dimensions. And as best practice, you should specify how many years back to migrate data, otherwise the tool migrates all years. Whether or not you make changes, we recommend that you review the default settings before you close the page and continue the migration process.

Configure migration globally

The steps in this section configure the data migration globally for all companies that you chose to migrate cloud migration setup. If you're migrating more than one company, you can specify the configuration on a per-company basis.

  1. Set the dimensions.

    To assign default dimensions for all companies you're migrating, select the Set All Dimensions action. Then select the two segments from Dynamics GP that want to use as the global dimensions in Business Central. The remaining segments are automatically set up as shortcut dimensions. Learn more about dimensions in Business Central.

    When you're migrating several companies then only those companies that use two segments from Dynamics GP are applied the global dimensions. For the companies that use different segments, you must go to the Per company section of the page and set the dimensions manually for these companies.

    You don't have to use the Set All Dimensions action. You can always specify the dimensions separately for each company in the Per company section.

  2. Choose the modules to migrate.

    Use the Modules section to choose the specific modules you want to migrate data from to Business Central. By default, all modules are selected for migration. If you don't want to migrate data for a module, turn off its switch. For example, if you don't want to migrate data for payables, turn off the Payables switch. In this case, the Open Purchase Orders switch is automatically turned off because the open purchase orders module relies on vendors, which are part of the payables module.

    If you're migrating the General Ledger module, be sure to go the Per Company section and specify the Oldest GL Year field. The year and all future years are migrated to Business Central. If you don't set the Oldest GL Year field, all years are migrated.

  3. Choose whether to migrate master data only for modules.

    Use the Master data only section to specify those modules for which you only want to migrate master data. For example, if you only want to migration bank account information, turn on the Bank switch. Bank transactions aren't migrated in this case.

    By default, both master data and transactional data for the selected modules are migrated. Master data represents the core information that about entities that changes infrequently, for example, like information about a bank. Transactional data captures specific activities or events for an entity, like bank deposits and withdrawals.

  4. Choose whether to disable auto posting for migrated transactions.

    By default, the migration process automatically posts migrated transactions in batches based on the type. Use the Disable auto posting section to specify transactions that you don't want posted automatically. To disable auto posting, turn off the switch for batch.

    Disabling auto posting is useful if you wanted to modify transactions before they're posted. For example, if you wanted to adjust some general ledger accounts before they're posted, turn off the Account batches switch.

  5. Choose the inactive record or discontinued items that you want to migrate.

    Use the Inactive records section to specify the inactive records or discontinued items that you want to migrate. By default, no inactive records or discontinued items are migrated. So, for example, if you wanted to migrate inactive customers, turn on the Inactive Customers switch.

  6. Choose the classes that you want to migrate as posting groups.

    Use the Classes section to specify the classes that you want migrated to Business Central. For each class you migrate, a posting group that has the same name as the class is created in Business Central. For example, if you want to migrate the Customer class in Dynamics GP to a posting group called Customer in Business Central, turn on the Customer class switch.

  7. Choose the historical transactions that you want to migrate.

    Use the historical snapshots section to specify historical transactions that you want migrated to Business Central. The selected transactions are migrated to extension tables in Business Central. User in the Business Central client can then view the data from specific Dynamics GP list pages.

    To migrate historical transactions, do the following steps.

    1. Turn on the Enable/Disable All Transactions switch.
    2. Turn on the switch for each transaction type you want to migrate, like GL Transactions and AR Transactions.
    3. Go to the Per company section and set Oldest Snapshot Year field the earliest year in GP that you want migrated.

Configure migration per company

Use the Per company section to set the data migration settings separately for each company when you're migrating more than one company. You can specify the same settings as you can globally, plus a couple more. By default, each company uses the global settings.

Use the following fields to specify how far back in time you want to migrate general ledger (GL) account summary data and historical snapshots:

  • Oldest GL Year - Use this field to select from which year in the past you want to migrate GL account summary transactions. If the Oldest GL Year field is empty, all years are migrated. Account summary transactions are generated and posted for open and history years that are set up in Dynamics GP. The summary amounts are created based on the fiscal periods set up in Dynamics GP. For example, suppose 2019, 2020, 2021, and 2022 are historical years in Dynamics GP, but you only wanted to migrate data from 2021 and later. In this case, you set the Oldest GL Year to 2021. As a result, summary transactions for 2019 and 2020 aren't migrated to Business Central.

  • Oldest Snapshot Year - Use this field to select from which year in the past you want to migrate history snapshots. If the Oldest GL Year field is empty, history snapshots from all years are migrated.

Next steps

Run data replication.