Migrate from Kladana ERP to Acumatica

Kladana Counterparty is a single entity covering both customers and vendors. FlitStack splits each counterparty into one Acumatica Customer record and one Acumatica Vendor record based on Kladana's counterparty type flag. Active sales orders route the counterparty to Customer; active purchase orders route it to Vendor. Each gets a primary Location in Acumatica.

Kladana contact records map to Acumatica Contacts attached to Customer or Vendor Location records. Each contact's phone number, email address, job title, and department information migrate as Contact fields. If a contact is marked as the primary contact in Kladana, that flag becomes the Default Contact designation on the corresponding Acumatica Location record, ensuring the most important contact is properly identified during the migration process.

Kladana products with product-type=Service map to Acumatica Non-Stock Items. Products with variants (color, size) map to Acumatica Matrix Items with the parent as the template and variant combinations as matrix rows. Bundle compositions from Kladana become Kit/Special fulfillment items in Acumatica.

Kladana variant attribute combinations (e.g., size + color) become Acumatica Matrix Item rows. The Kladana parent product becomes the Acumatica template Stock Item. Attribute names from Kladana (e.g., Color, Size) become Matrix Dimensions in Acumatica. Each populated combination creates one matrix row.

Kladana warehouses map 1:1 to Acumatica Warehouses. Warehouse code, name, and address fields migrate directly without transformation. For setups using Kladana's bin storage configuration, Acumatica Warehouse Management configuration must be completed post-migration — the original bin records are preserved as a reference file so your team can recreate the bin structure in Acumatica if needed.

Kladana Sales Orders map to Acumatica Sales Orders with the same order number, order date, and due date. Customer reference and description fields migrate as Sales Order description. Line items map to Sales Order Details referencing Stock Item IDs. Open orders migrate with status preserved; completed orders migrate with a Closed status flag.

Kladana invoices map to Acumatica AR Invoice (or Sales Order with AR Invoice generation). Invoice number, date, due date, and amounts migrate. Line items map to Invoice Details. Kladana invoice tax amounts and discounts aggregate into Acumatica's tax and discount line handling. Payment status from Kladana carries as a reference note on the invoice.

Kladana Purchase Orders map to Acumatica Purchase Orders with the same PO number, vendor reference, and dates. Line items link to Stock Item or Non-Stock Item based on product type. Open POs migrate with status Open; received POs migrate as Completed with receipt history preserved as an attachment reference. Currency from Kladana maps to Acumatica's vendor currency setting.

Kladana inventory adjustments, receipts, and shipments map to Acumatica Inventory Receipt (for inbounds) and Inventory Issue (for outbounds or adjustments). Each movement's date, warehouse, and item quantity migrate. Lot and serial number references from Kladana carry into Acumatica's lot/serial tracking fields. Movement reason codes map to Acumatica's Reason Code field.

Kladana Production Orders map to Acumatica Production Orders with the same production ID and planned dates. BOM and materials from Kladana link to Acumatica BOM IDs post-migration. Operation reports and labor tracking from Kladana are preserved as PDF attachments on the Production Order for historical reference. Material variance and actual vs. planned quantities migrate as Production Order line notes.

Kladana BOMs (standard and partial) map to Acumatica BOMs with the same code and version. Material components map as BOM lines referencing Stock Item IDs with quantities. Kladana BOM cost estimates migrate as a BOM Cost Profile record in Acumatica. Multi-level BOMs from Kladana require flattening and mapping to Acumatica's nested BOM structure.

Kladana Business Process Configurator workflows (approval rules, notification triggers, field-update actions) have no direct Acumatica equivalent. We export the complete workflow definitions as a structured JSON specification covering trigger conditions, action steps, and escalation paths. Your Acumatica consultant uses this to rebuild equivalent automation using Acumatica's Business Events, Actions, and Screen Automation.

Kladana custom field definitions and values migrate to Acumatica UDFs. Each UDF must be created in Acumatica's Customization Project editor before data loads. Field type mapping: Kladana text → Acumatica String, Kladana number → Acumatica Decimal/String, Kladana date → Acumatica Date. UDFs on Customer, Vendor, Stock Item, Sales Order, and Purchase Order are supported.

Kladana file attachments (images, PDFs, spreadsheets) associated with products, orders, or counterparties re-upload to Acumatica Files attached to the corresponding entity. Original filenames and upload dates are preserved. File size limits (Acumatica default 25MB per file) are enforced during re-upload. Inline images in notes are downloaded and re-hosted as Acumatica File attachments.