OPplus to Continia Banking data migration overview

• 27/03/2026
• 3 minutes to read

This article provides an overview of the data that is transferred when migrating from OPplus to Continia Banking.

Data transferred during the migration

The following data is carried over to Continia Banking:

• Direct debit mandates and their usage
• Remittance information
• Bank closing days
• Payment allocation (chain liability)
• Bank account verification
• Payment suggestion templates
• Vendor/customer:
  • Allow summarizing payments
  • Compress remittance text
  • Remittance advice email sending method (including document layout)
  • Cost type
  • Advice from number of items
  • New payment from number of items

Data not transferred during the migration

Not all data or features will be migrated from OPplus to Continia Banking. Some elements require manual review.

For guidance on accessing historical OPplus data, see Verifying and completing post-migration step.

Import

The following import-related data is not transferred:

• Setup/configuration data - for example, OPplus uses document number ranges that do not align with the numbering logic in Continia Banking. These settings are managed differently and must be configured in the bank account setup.
• Import interfaces - interfaces used to import data are not be migrated.
• Import journals - import journals are not transferred to the new system.
• Rules - OPplus rules are not migrated one-to-one. Continia Banking uses search rules, split rules. If you have accounting rules that post to general ledger accounts, we recommend exporting them to Excel using a configuration package. This also provides an opportunity to clean up outdated rules.
• Imported customer/vendor bank accounts - the table containing imported bank accounts is not migrated.
• CSV Ports - CSV ports used in the payment import are not be migrated. Review these separately and recreate them in the new structure in Continia Banking.

Export

The following export-related data is not transferred:

• Setup/configuration data - general setup and configuration data is not migrated.
• Setup/configuration data for other payment types - configuration for payment methods such as DTAZV, FR, or CH is not transferred.
• Recurring payment proposals - rules and settings for recurring payment proposals are not migrated.
• Posting setup - posting setup for payment export is not transferred.
• Account settings for payment export - account-specific export settings (for example Z4 or ISO formats) are not migrated.