Migrate your Kladana ERP data

Items in Kladana support variants, bundles, serial numbers, batches, expiry dates, and barcode associations. We map all standard item attributes including cost price, sell price, and reorder points. Variant matrices and bundle compositions are preserved as nested structures during migration.

Counterparties are unified objects representing both customers and suppliers. Each counterparty links to a full transaction history, open invoices, and contacts. We preserve all linked metadata and roll forward balances for active counterparties.

Sales Orders capture the full lifecycle: draft, confirmed, reserved, fulfilled, and invoiced states. We map order headers, line items with pricing, fulfillment status, and associated shipment records. Open orders are flagged for cutover planning.

Purchase Orders mirror the Sales Order structure for inbound procurement. We preserve linked supplier references, expected delivery dates, and receipt status so inventory projections carry forward accurately.

Kladana supports multiple warehouses with bin storage, stocktakes, and internal transfers. We extract per-warehouse stock-on-hand quantities, reserved quantities, and pending inbound and outbound movements to reconstruct inventory positions at the destination.

BOMs define component relationships for manufactured items. Kladana supports multi-level BOMs and BOM versions. We map BOM structures but note that destination systems often represent subassembly nesting differently; field-level alignment is required during migration scoping.

Production Orders reference a BOM, a routing, and planned quantities. They track actual output, material consumption, labour hours, and variance. We preserve the production order header and line data, but routing-specific operation sequences require custom mapping since not all destinations model operations identically.

Kladana generates invoices linked to orders and counterparties. We extract invoice headers, line items, tax codes, payment status, and outstanding balances. Fully paid invoices are migrated as historical records; open invoices are flagged to preserve receivables and payables tracking.

Kladana includes a task management layer and a workflow configurator for automating business processes. Tasks assign actions to users with status tracking. Workflows are configuration records with conditional logic that often do not translate directly to other platforms. We export task records and flag workflows for manual reconstruction at the destination.

Kladana supports custom fields on Items, Counterparties, Orders, and other objects. Custom field definitions and their values are migrated as key-value pairs. The destination must have compatible custom field slots or a notes/attributes field to receive this data.

User access control in Kladana is role-based with fine-grained permissions per module. Role definitions are proprietary configurations that do not map 1:1 to other platforms. We export role assignments and recommend a role-mapping exercise during onboarding.

Kladana's CRM module stores contact records, sales history, interaction notes, and custom offers linked to counterparties. These are migrated as structured records aligned to the destination's contact object schema.