Migrate from Kladana ERP to Infor CloudSuite Corporate

Kladana Items with variants, batches, serial numbers, expiry dates, and barcode associations map to Infor Item Master. We preserve SKUs (Kladana article ID), descriptions, cost prices, sell prices, reorder points, and unit of measure. Serial number and batch tracking attributes map to Infor's lot and serial number configuration. Barcode data migrates as an item attribute. Infor requires the item master to be configured before any BOM, stock, or order records can reference it, so this is always the first object loaded.

Kladana Counterparty is a unified object for both customers and suppliers. We split on the counterparty_type attribute into Infor Customer and Infor Supplier records. Address data, contact information, and tax registration numbers map to Infor's address book structure. Kladana counterparty-specific payment terms and credit limits migrate as configuration data. Each counterparty must be present before any Sales Order or Purchase Order referencing it can be loaded.

Kladana BOMs define component relationships for manufactured items. Multi-level BOM subassemblies map to Infor BOM structures. Kladana's support for BOM versions requires special handling: Infor CloudSuite does not track BOM versions as a first-class concept and collapses BOMs to a single active version. We export BOM version history, identify records with multiple versions, and flag them for the customer to designate a canonical version before migration. Component quantities, scrap percentages, and operation step references migrate from Kladana routing operations.

Kladana Production Orders reference a BOM and routing, with planned quantities, actual output, material consumption, labour hours, and variance data. We map the production order header, BOM reference, and material consumption lines to Infor Production Orders. Planned-versus-actual variance data migrates as historical cost records. Infor's production order sequencing requires the BOM to exist first, so BOM load precedes production order load. Infor does not natively replicate Kladana's production order workflow stages; we configure the production order statuses in Infor OS to match the customer's operational states.

Kladana Sales Orders with full lifecycle states (draft, confirmed, reserved, fulfilled, invoiced) map to Infor Sales Orders. We preserve order headers, line items with pricing and discounts, fulfillment status, and shipment references. Open Sales Orders load first so that inventory reservation logic in Infor can compute correctly at go-live. Closed and invoiced orders migrate as historical records with invoice references. Customer and product references are resolved at migration time using the item and counterparty lookups established in the first two object loads.

Kladana Purchase Orders mirror the Sales Order structure for inbound procurement. We preserve linked supplier references, expected delivery dates, receipt status, and line item pricing. Open Purchase Orders load with supplier and product references resolved from the item and counterparty lookups. Historical Purchase Orders migrate as closed records with receipt history. Infor requires the supplier record to exist before a Purchase Order can reference it.

Kladana multi-warehouse data with bin storage and internal transfers maps to Infor's Warehouse Management configuration. Per-warehouse stock-on-hand quantities, reserved quantities, and pending inbound and outbound movements migrate as inventory transactions. We extract the current stock snapshot from Kladana and load it as an inventory opening balance in Infor, preserving serial number and batch references where applicable. Infor's warehouse hierarchy (Company > Division > Plant > Warehouse) must be configured before stock can be assigned to a location.

Kladana invoices linked to orders and counterparties map to Infor AR (for sales invoices) and AP (for purchase invoices) records. We extract invoice headers, line items, tax codes, payment status, and outstanding balances. Fully paid invoices migrate as historical records. Kladana's lightweight financial module means that ledger entries, journal postings, and formal financial statements are reconstructed from these invoice records in Infor's full AR/AP/GL module post-migration.

Kladana custom fields on Items, Counterparties, Orders, and other objects migrate as key-value pairs. Infor OS supports extended fields and custom attributes on most master data and transaction objects. We pre-create the Infor custom attribute definitions before loading data, then populate attribute values during the relevant object loads. Custom field data types are mapped to Infor field types (text, number, date, picklist) during the schema design phase.

Kladana CRM records store contact information, sales history, interaction notes, and custom offers linked to counterparties. These migrate as Infor Contact records with associated interaction logs. Contact details (name, email, phone, role) map from Kladana's contact sub-object. Interaction notes and sales history migrate as Infor interaction records with timestamps. Infor's Contact Manager module is the destination; it is available from the Professional tier of most CloudSuite editions.