Migrate from Kladana ERP to Microsoft Dynamics 365 Business Central

Kladana Items map to Dynamics 365 Products with Item type set to Stocked Item for inventory-tracked goods or Service for non-stocked items. We carry over all tracking dimension settings: serial number, batch number, lot, and expiry date configurations map to the corresponding tracking dimension groups in Dynamics 365. Barcode associations migrate as item barcode records attached to the Product. Cost price and sales price migrate as purchase price and sales price on the Product.

Kladana Item variants (size, color, configuration combinations) map to Dynamics 365 Product variants. The variant dimensions in Kladana become Product dimension groups (Size, Color, Configuration, Style) in Dynamics 365. We create the variant matrix in the destination before any stock positions are loaded so that inventory quantities can be attributed to the correct variant SKU at import time.

Kladana Counterparty records with a customer role split into Dynamics 365 Customer records. The customer postal address and delivery address in Kladana map to the Dynamics 365 Address table, with the first address marked as the primary address for each purpose. Note that Kladana allows multiple primary addresses per type (invoice, delivery) while Dynamics 365 enforces one primary address per address purpose; we map the most recent or most-used address as primary and flag any additional addresses for manual review.

Kladana Counterparty records with a supplier role split into Dynamics 365 Vendor records. Supplier-specific fields including payment terms, invoice account, and purchase order address migrate to the corresponding Vendor fields. Any multi-currency settings on the supplier in Kladana map to the Vendor's currency and payment currency configuration in Dynamics 365.

Kladana Sales Orders map to Microsoft Dynamics 365 Sales Orders with order status, header discount, and line item pricing preserved. The Kladana order lifecycle (draft, confirmed, reserved, fulfilled, invoiced) maps to the corresponding Microsoft Dynamics 365 Sales Order status values. Header-level charges from Kladana migrate as miscellaneous charges on the Sales Order. We resolve the Customer and Salesperson references at import time using the email-based lookup.

Kladana Purchase Orders map to Dynamics 365 Purchase Orders with order status, expected delivery date, and receipt status preserved. The supplier reference and purchase dimensions (cost center, project) migrate to the corresponding Purchase Order fields. Any landed cost allocations on the purchase order line map to the Charge currency amount on the Purchase Order.

Kladana warehouses map to Dynamics 365 Warehouses under a Site. We extract per-warehouse stock-on-hand quantities, reserved quantities, and pending inbound and outbound movements as inventory movement records. Serial number, batch, and expiry date positions from Kladana map to the corresponding inventory tracking dimensions in Dynamics 365, requiring that the tracking dimension groups are configured before stock data loads. In-transit warehouse locations in Kladana map to in-transit warehouses in Dynamics 365 Supply Chain.

Kladana BOMs map to Dynamics 365 BOM records. Kladana supports multiple BOM versions per product and allows a production order to reference a specific version; Dynamics 365 manages BOM versions as a separate entity linked to the BOM header. We export BOM version history from Kladana and create corresponding BOM Version records in Dynamics 365, flagging any BOM with multiple versions for the customer to designate which version becomes the default active BOM at cutover.

Kladana Production Orders map to Dynamics 365 Production Orders with planned quantity, actual output, material consumption, labour hours, and variance data preserved. The production order references the BOM Version resolved from the BOM mapping step. Routing operations from Kladana production orders map to production route operations in Dynamics 365. Planned-versus-actual variance data migrates as production journal lines so that the financial impact of variance is recorded in the inventory valuation.

Kladana Sales Invoices map to Microsoft Dynamics 365 Sales Invoice lines with invoice number, invoice date, due date, line items, tax codes, and payment status preserved. Paid invoices migrate as posted invoices with a payment journal reference; outstanding invoices migrate as open posted invoices. The customer invoice address maps to the Dynamics 365 Invoice address.

Kladana Purchase Invoices map to Dynamics 365 Vendor Invoice lines with invoice number, invoice date, due date, line items, tax codes, and payment status preserved. Vendor invoice approval status in Kladana maps to the corresponding workflow state in Dynamics 365. Prepaid invoices and invoices with holds are flagged in a custom field for the customer's AP team to review post-migration.

Kladana CRM contact records and interaction notes map to Dynamics 365 Contact records with the activity timeline preserved as Tasks, Emails, and Phone Call logs. Custom offers and sales history linked to a Counterparty migrate as notes and Opportunities attached to the Contact or the related Account. The contact's email, phone, and address fields map directly to the Dynamics 365 Contact address and communication fields.

Kladana custom fields on Items, Counterparties, Orders, and other objects migrate as key-value pairs carried in custom extension fields on the corresponding Dynamics 365 table. The destination environment must have the matching custom fields created in the AL extension before migration begins. We generate the field creation script from the Kladana custom field definitions and deliver it as a change-set or AL extension package for the customer's Dynamics 365 admin to deploy.

Kladana user roles with fine-grained permissions map conceptually to Dynamics 365 Security Roles. We export role assignments and permission configurations as a written inventory with a recommended Dynamics 365 Security Role mapping table. Role configurations do not map 1:1 because the permission models differ; the customer reviews and assigns roles manually in the Dynamics 365 admin center post-migration.