Migrate from BusPro
Move contacts, invoices, payments, accounting records and ERP exports from BusPro to Numezis using Files / CSV, Numezis support.
Overview
Migrating from BusPro to Numezis is usually a short, controlled project when the data is exportable in a structured way. The goal is to bring across master data first, validate a sample, import the operational and accounting data that still matters, and keep BusPro available as a read-only archive for older detail.
Also known as: BusPro AG.
Category: Legacy / discontinued.
Country focus: Switzerland.
Methods: Files / CSV, Numezis support.
BusPro source profile
Swiss business software with existing customer data that may still need migration even when a product is no longer a new-sales target.
Three migration paths
API
API is not listed as the primary path for BusPro in this guide. If your edition, implementation partner, or administrator can provide an export endpoint for the required data, Numezis support can review it; otherwise use the supported paths shown above.
Files / CSV
Use files or CSV when the fastest and safest route is to export lists and reports from BusPro. Numezis can work from clean CSV, spreadsheet exports, bank files such as CAMT or MT940 when available, and accounting reports that prove opening balances and open items.
Numezis support
Contact Numezis support when you want the migration reviewed end to end. The support path covers source-file review, field mapping, sample import, issue list, final import, and post-import checks so the changeover stays simple and traceable.
Migration focus for BusPro
For BusPro, the migration should not start from a generic export checklist only. Use these provider-specific points to decide what to export first and where the sample import must be checked carefully.
- Prioritize safe extraction and archive preservation.
- Use support-led mapping because legacy exports often need cleanup before import.
Data you can bring into Numezis
- Customers, suppliers, contacts, organizations, and delivery addresses.
- Products, services, price references, VAT categories, and default accounts.
- Chart of accounts, cost centers or dimensions when the source exports them cleanly.
- Opening balances, open invoices, open bills, payments, credit notes, and bank transactions.
- Historical accounting entries when they are needed in Numezis instead of only in the archive.
- Attachments and document references when the source system exports them in a usable structure.
Recommended process
- Confirm the migration scope: modules, period, records, attachments, and cutover date.
- Clean the source data: duplicates, inactive contacts, obsolete products, old tax codes, and unmapped accounts.
- Export the source files or authorize API access with the minimum permissions needed.
- Map fields into Numezis and decide which history stays archived in the old system.
- Run a sample import and verify totals, open balances, VAT treatment, contacts, and document links.
- Run the final import after the agreed freeze point and reconcile the first working day in Numezis.
- Keep the old system as an archive until legal and operational retention needs are covered.
Notes for BusPro
- BusPro data should be handled conservatively because legacy exports can be incomplete, inconsistent, or dependent on an old installation.
- Export both detailed files and printable control reports before any system is decommissioned.
- Use Numezis support for mapping and validation so the new workspace starts from clean data while the old system remains available as evidence.
Support checklist
- Exact source product name, edition, hosting model, and active modules.
- Fiscal years and operational periods to migrate.
- Export files, API credentials or tokens if available, and a contact who can re-export data if needed.
- Record volumes for contacts, products, invoices, bills, payments, accounting entries, and attachments.
- Target cutover date and the period during which source-system edits will be frozen.
- Control totals from the old system: open receivables, open payables, bank balances, VAT balances, and profit-and-loss totals.
FAQ
How long does a migration take?
A clean SME migration can be prepared quickly once exports are available. Larger ERP migrations take longer because modules, dimensions, custom fields, and history need more validation.
Do I need to migrate every historical transaction?
No. Many companies import master data, open items, opening balances, and recent operational history, then keep the former system as archive for older detail.
Can Numezis import attachments?
Yes when the source exports attachments with usable file names, references, or folders. If attachments are locked inside the source system, support will propose an archive-first approach.
What happens if a CSV has errors?
The import should be tested on a sample first. Invalid dates, missing accounts, duplicate contacts, or unmapped tax codes are corrected before the final import.
Can Numezis support handle the migration?
Yes. Support can review files, define mappings, run a sample import, document exceptions, and guide the final cutover.
Official sources
Related
Migrate from einzly
Move contacts, invoices, payments, accounting records and ERP exports from einzly to Numezis using API, Files / CSV, Numezis support.
Migrate from SelectLine
Move contacts, invoices, payments, accounting records and ERP exports from SelectLine to Numezis using API, Files / CSV, Numezis support.