Skip to content
KramviaTECHNOLOGIESTalk to us

Move from your old ERP

A clearer move starts with records you can check.

Kramvia ERP’s migration workflow is designed to reduce repeated setup while making the imported opening position reviewable. Map supported exports, resolve exceptions and reconcile the starting balances before beginning new work in the ERP.

FOLLOW THE WORKFLOW

Review first. Switch with a checked starting point.

  1. Assess the export
  2. Save field mappings
  3. Resolve duplicate & invalid rows
  4. Check stock & balances
  5. Approve the cutover

FICTIONAL WORKFLOW EXAMPLE

A review that explains every row

Illustrative only: a source contains 100 product rows. The review identifies 90 new records, 8 matches to existing records and 2 invalid rows. The two exceptions must be corrected or explicitly excluded; the source count must remain explainable.

Record counts are only one check. Opening quantities, stock values and party debit/credit balances need separate reconciliation before new postings begin.

CONFIRM THE SCOPE

What can move today?

Current adapter scope

Defined EasySol CSV exports: manufacturers, products, customers/suppliers, opening stock and party opening balances.

Needs assessment

Your source version, column mappings, record quality, volumes, exceptions and the stock/balance reconciliation results.

Not established as supported

Other ERP adapters, full historical invoices and transactions, native Excel workbooks and SQL backup conversion.

Current browser intake uses UTF-8 CSV files under 5 MB per review batch. This is an intake limit, not a claim about total migration capacity.

Confirm what can be brought across

The current implemented adapter supports defined EasySol CSV exports for manufacturers, products, customers/suppliers, opening stock and party opening balances. It does not establish support for every ERP, every field or complete historical transactions.

  • Confirm the source version, report type and relevant location.
  • Use UTF-8 CSV files under 5 MB per review batch in the current intake.
  • Treat native Excel workbooks, database backups and additional vendors as separate compatibility work.

Map fields and review each exception

Saved mapping profiles help interpret supported headings. A staged review identifies ready records, duplicates and invalid rows before an authorised apply step creates operational records. Existing master values are not overwritten by the import.

  • Inspect how source identifiers map to existing or new records.
  • Resolve or explicitly skip non-ready rows.
  • Keep supported legacy references associated with reviewed records.

Reconcile the opening position

An import finishing is not the same as a migration being accepted. Compare the source with created, matched, skipped and invalid records, and investigate differences before new transactions are posted.

  • Compare record counts by entity.
  • Check opening stock quantity and value by location.
  • Check party opening debit and credit balances against the source.

Agree the cutover and retain the old records

Plan an entry-freeze window, responsible reviewers and a fallback period. Kramvia does not alter the source system. Retain access to legacy records and start new ERP activity only after the agreed opening position has been accepted.

  • Record known exclusions and pending corrections.
  • Keep a log of transactions occurring around the freeze.
  • If reconciliation fails, investigate and reschedule instead of assuming a safe rollback.

Questions about this workflow

Will all my old invoices transfer?

Full historical transaction migration is not established in the current adapter. Agree the entities and historical exclusions before planning a cutover.

What if the opening totals do not agree?

Investigate the discrepancy and retain the old ERP as the operational system until an accepted opening position is established. Do not treat deleting imported records as a safe rollback.

Is migration automatic from any ERP?

No. The current implemented adapter covers defined EasySol CSV exports. Other sources need representative samples, mappings, tests and reconciliation evidence.

What to bring to the discussion

  • Source ERP/version and the exports it can produce.
  • Entity counts, opening-stock totals and party-balance totals.
  • A reviewer, proposed cutover window and records that must remain accessible.
Discuss your requirements