Migrating Payment Management data to Continia Banking

Use the Continia Banking Data Migration tool to transfer data from Payment Management (PM) to Continia Banking (CB) in Microsoft Dynamics 365 Business Central.

Note

Content in this article is maintained continuously and some steps may require additional attention depending on your setup. Review all instructions carefully before starting the migration process.

The migration tool provides a guided and structured approach to moving financial data. When migration is complete:

  • Payment Management is automatically deactivated.
  • Continia Banking is activated.

With the enhancements in Continia Banking, some setup elements and data are now handled differently than in Continia Payment Management. The migration tool transfers most of your data, but certain items are not included and must be recreated or adjusted manually:

  • PSP agreements
  • Search and reconciliation rules
  • Multiple bank statement imports
  • Templates for notifications or Danish FIK payment references

After completing the migration, follow the guidance in Verifying and optimizing after migration to review your setup and confirm that all configurations work as expected.

Prerequisites

Before you start migration, make sure the following requirements are met:

  • Business Central version - the content in this article applies to Business Central 27 and later. If you're using Business Central 26, see the previous version of this article, as the functionality described here isn't available in that version.
  • Payment Management version - 27.0.0 or later.
  • Bank account reconciliations - reconcile and post all bank account reconciliations.
  • Journals - post or delete all open journal lines (payment journals, cash receipt journals, purchase journals).
  • Job queues - disable all job queue entries related to Payment Management.
  • Permissions - confirm you have administrative access and permissions to install apps.
  • Field dependencies - verify no custom development depends on Payment Management fields or functionality. Payment Management will be deactivated after migration.
  • Data migration overview - review the Payment Management to Continia Banking data migration overview for details about tables and fields migrated.

Before starting the migration, install the following apps from Microsoft AppSource:

Requirements for on-prem migration

To successfully perform an on-premises migration, the following is required:

  • A developer license, or a customer license with all Payment Management and Continia Banking modules assigned.
  • SUPER user permission set.

Failure to meet these requirements will result in migration errors due to insufficient permissions.

To run the pre-validation

  1. Search (Search) for and select Continia Banking Data Migration Setup.
  2. In the wizard, the pre-validation tool checks your Continia Payment Management data for issues. If a line shows Error, select it to see the details and access related records.
  3. After resolving all errors, close the wizard and restart the migration. When you reopen Continia Banking Data Migration Setup, ensure that all results on the Pre-Validation page show Success, then click Next.

To configure and run the migration

  1. On the Migration Data page, review the data to be migrated to Continia Banking and configure the following options before proceeding. If your environment does not use Master Data Management, leave Use Master Data Management disabled and skip to step 2. If your environment uses Master Data Management, enable Use Master Data Management and configure the following:
    • Master Company - select the company that manages your data and shares it with other companies.
    • Migration per Data Type - for each data type, choose where it is migrated: the master company, sub-companies, or all companies. By default, data is synchronized from the master company.
  2. In the Ledger Entries section, Migrate Open Ledger Entries Only is enabled by default. Specifies whether to migrate payment information only to open vendor and customer ledger entries. When enabled, closed entries are not migrated, which speeds up the migration.
  3. In the Customers, Vendors & Employees, Bank Accounts, and Ledger Entries & Documents sections, all options are enabled by default. In most cases, it is best to leave these settings unchanged. If a particular data type is not relevant to your environment, you can exclude it from the migration. For example, if you do not use payments on sales orders and have a large number of sales documents, excluding Sales Documents may help reduce the migration time.
  4. On the Bank Account Availability step, the wizard provides an overview of your existing accounts and their status in Continia Banking.
    • If no bank accounts are listed, click Create Bank Request Selection to view an overview of available accounts.
    • If a bank is not supported, click Request Selected Bank to notify Continia about the missing bank format.
  5. On the next page, accept the terms and conditions by enabling the I accept the terms and conditions toggle.
  6. All existing bank account verifications from Continia Payment Management are migrated, including their verification status and log. If you also want the migration tool to automatically verify any bank accounts that are not yet verified, enable I want to verify all bank accounts. When enabled, the migration tool marks these verified accounts as Auto-verified by Migration Tool.
  7. Click Review PM Journals to open the PM Journal Migration Decisions page. For each journal batch, select Actions > Set Decision (Selected) or Set Decision (All), and then choose one of the following options. When you are finished, return to the wizard.
    • Pending – no decision has been made. The batch remains unchanged.
    • Keep – keeps the batch and its journal lines unchanged.
    • Delete – deletes the batch and all related journal lines.
    • Migrate – converts the batch from a Payment Management journal to a Continia Banking Export journal.
  8. Click Migrate Data.
  9. Click Yes to start the migration.
  10. The Migration Process page shows the migration progress for each company. Click Refresh to update the status.
  11. When the status is Completed for all companies, click Close to finish the migration.

To activate Continia Banking

  1. On the Migration Prepared! page, click Activate. The system checks which modules are activated in Continia Payment Management. For each company, the system deactivates Continia Payment Management and activates Continia Banking with the corresponding modules.
  2. The Activation Progress page shows the activation progress. Click Refresh to update the status.
  3. Click the number in the Records Migrated column to view the Migrated Data Types page. Go back to the Activation Progress page and click Close to complete activation.
  4. To continue your setup, run the assisted setups for Continia Banking and review the settings in Banking Import and Banking Export.

Next steps

Payment Management to Continia Banking data migration overview