Skip to Content
Importing from Minimax

Importing from Minimax

Minimax is one of the most common accounting tools in Slovenia, so VegaERP ships a dedicated importer for it rather than a generic CSV mapping tool.

What gets imported

  • Contacts — customers and suppliers, including foreign entities. The importer preserves foreign tax numbers and the VAT-payer flag per contact, and de-duplicates contacts that don’t have a stable external key by matching on name and tax number instead of blindly creating duplicates.
  • Chart of accounts and opening balances — so historical reporting stays intact after the switch.
  • Payroll master data — employees, contracts, and the statutory catalog needed to keep running payroll without re-entering everything by hand.

Before you start

  1. Export the relevant data from Minimax (contacts, chart of accounts, opening balances, employees) in the format the importer expects.
  2. Decide your cutover date — the day VegaERP becomes the system of record. Import opening balances as of that date; don’t import historical transaction detail you don’t need for reporting.
  3. Make sure your VAT-payer status and flat-rate status are set correctly on the company profile first (see Getting started) — the importer uses this to decide whether imported documents need VAT book entries.

Running the import

Run the importer from the data-import section of the app. It processes contacts first (so later documents can reference them), then the chart of accounts and balances, then payroll data if applicable.

After the import — what to check

  • Duplicate contacts. The importer dedupes on name + tax number when no stable Minimax ID is available, but always spot-check the contact list after a large import.
  • Foreign suppliers/customers. Confirm foreign tax numbers carried over correctly — this matters for VAT book reporting on cross-border transactions.
  • Opening balances. Reconcile the imported trial balance against Minimax before you book your first new document in VegaERP.

If something looks wrong after an import, don’t manually patch individual records — re-running the import is designed to be safe (it upserts rather than duplicates), so fix the source export and re-run instead.

Last updated on