ERP migration
Field-level mapping, validation, and rollback between Kentro ERP & 3PL and Acumatica. We move data and schema; workflows are rebuilt natively in Acumatica.
Kentro ERP & 3PL
Source
Acumatica
Destination
Compatibility
10 of 12
objects map 1:1 between Kentro ERP & 3PL and Acumatica.
Complexity
BStandard
Timeline
2–4 weeks
Overview
Kentro ERP & 3PL models commerce operations as products with multi-channel sources, fulfillment workflows, and real-time inventory tied to warehouse bins. Acumatica models the same entities through a financial lens: Inventory Items with valuation methods, Sales Orders with shipment and invoice flow, and Customers with Bill-To/Ship-To split locations. FlitStack AI extracts Kentro's products, open orders, customers, and inventory snapshots via API, then maps them to Acumatica's Inventory ID, Sales Order, and Customer records with UOM conversions, cost center assignments, and warehouse-site routing. We surface Kentro's fulfillment states (backorder, cross-dock, Amazon FBA) as Acumatica shipment and availability records. Any workflow automations or channel-specific shipping rules must be rebuilt in Acumatica's Generic Inquiry or automation screens — we provide a feature-equivalence export as a rebuild reference. The migration uses API export from Kentro combined with Acumatica's import framework for incremental validation. During extraction, FlitStack records Kentro's internal IDs and timestamps for each entity. The transformation stage applies UOM class mapping, sets the InventoryID ValMethod to match Kentro's costing, and assigns cost center segments from Kentro's product categories. After mapping, a sample of records is validated against the Kentro snapshot to ensure accuracy before the full import. The import framework uses Acumatica's Import by Scenario with CSV batches, and any new records created in Kentro during the final window are captured by a delta-pickup run before cutover.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Kentro ERP & 3PL object lands in Acumatica, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Kentro ERP & 3PL
Product / SKU
Acumatica
Inventory Item (InventoryID)
1:1Kentro products map to Acumatica Inventory Items. We preserve the Kentro SKU as InventoryCD, map the product description to Description, and set the Stock Item checkbox based on whether the product is inventory-bearing in Kentro. UOM (each, case, pallet) maps to a UOM class in Acumatica with cross-reference to Kentro's unit of measure.
Kentro ERP & 3PL
Customer
Acumatica
Customer
1:1Kentro customers migrate to Acumatica Customers with Bill-To and Ship-To locations. Kentro's billing address and shipping address become separate location records under the customer. Customer class in Acumatica is set based on Kentro's customer type (wholesale vs. D2C) to apply the correct tax zone and payment terms.
Kentro ERP & 3PL
Supplier
Acumatica
Vendor
1:1Kentro suppliers map to Acumatica Vendors. The supplier's address, contact email, and payment terms migrate as Vendor attributes. We preserve the supplier's Kentro ID in a custom field for reconciliation against purchase history. We also assign a Vendor Class based on the supplier’s category to set payment terms and tax zones. Bank account details for ACH can be migrated to Acumatica’s Vendor payment methods with appropriate security handling.
Kentro ERP & 3PL
Sales Order (open)
Acumatica
Sales Order
1:1Open Kentro orders become Acumatica Sales Orders with the original order date preserved as OrderNbr. reference. Kentro's order-status values (pending, processing, shipped) map to Acumatica's order status workflow. Each line item maps to Sales Order Detail with InventoryID, quantity, and the Kentro shipping method mapped to ShipVia.
Kentro ERP & 3PL
Fulfillment / Shipment
Acumatica
Shipment + Inventory Transaction
many:1Kentro's fulfillment records are split across Acumatica's Shipment and Inventory Transaction entities. The fulfillment ID becomes the Shipment Nbr.; line-level shipped quantities create Inventory Receipt or Issue transactions to update on-hand. Original carrier and tracking number migrate as Shipment attributes.
Kentro ERP & 3PL
Inventory Snapshot / On-Hand
Acumatica
Inventory Item Site (Qty. On Hand)
1:1Kentro's bin-level on-hand quantity per warehouse becomes an Inventory Item Site record per Site (warehouse). Kentro's FEFO priority number maps to a Lot/Serial Nbr. class if Acumatica uses lot tracking, or is preserved as a custom field for fulfillment sequencing. Qty. Available is recalculated in Acumatica based on allocated and available logic.
Kentro ERP & 3PL
Purchase Order
Acumatica
Purchase Order
1:1Open Kentro purchase orders migrate to Acumatica Purchase Orders with Vendor, line items (InventoryID + quantity), and expected delivery date preserved. Kentro PO status maps to Acumatica's PO status field. Line-level discounts, shipping instructions, and any notes attached to each PO are also transferred as attributes on the Purchase Order detail. If Kentro records the buyer contact, we map that to the Requested By field in Acumatica for traceability.
Kentro ERP & 3PL
3PL Service Record
Acumatica
Custom Field + Fulfillment Workflow Note
1:1Kentro's 3PL service records (cross-dock flag, Amazon FBA prep status, white-glove flag) have no native Acumatica equivalent. We preserve these as custom fields on the Shipment (e.g., FulfillmentType__c) and include a migration note for your Acumatica admin to configure fulfillment workflow rules.
Kentro ERP & 3PL
Backorder Record
Acumatica
Availability Check + Allocation Note
1:1Kentro backorder records map to Acumatica's availability check result on the Sales Order. Backordered quantity appears as a line-level note; the original backorder date is preserved as a custom field. Fulfillment rules for backorder release are documented for rebuild in Acumatica's automation.
Kentro ERP & 3PL
Channel Source Label
Acumatica
Custom Field on Sales Order
1:1Kentro's channel label (Shopify, Amazon, TikTok) per order has no native Acumatica equivalent on Sales Order. We create an OrderSource__c custom field and populate it with the Kentro channel name. This enables Acumatica Generic Inquiry filters to segment by channel.
Kentro ERP & 3PL
Return / Refund
Acumatica
Sales Order (credit) / Inventory Issue
many:1Kent returns migrate as credit memos or adjustment lines in Acumatica. If inventory is returned to a specific bin, we create an Inventory Issue transaction. Return reason codes map to a custom field for reporting. The credit memo links to the Sales Order so AR can be offset. Returned inventory cost posts to the COGS account, and we preserve the timestamp for reporting. Acumatica generates it from the credit memo.
Kentro ERP & 3PL
Multi-Channel Listing
Acumatica
Inventory Subitem or Cross-Reference
1:1Kentro's product listing variations per channel (e.g., Shopify SKU vs. Amazon ASIN) map to Acumatica's Inventory Cross-Reference table. We preserve the channel-specific identifier in a custom field on each InventoryID cross-reference record. This cross-reference lets Acumatica match marketplace sales to the correct inventory item automatically. It can also store the channel price for reference during order import.
| Kentro ERP & 3PL | Acumatica | Compatibility | |
|---|---|---|---|
| Product / SKU | Inventory Item (InventoryID)1:1 | Fully supported | |
| Customer | Customer1:1 | Fully supported | |
| Supplier | Vendor1:1 | Fully supported | |
| Sales Order (open) | Sales Order1:1 | Fully supported | |
| Fulfillment / Shipment | Shipment + Inventory Transactionmany:1 | Fully supported | |
| Inventory Snapshot / On-Hand | Inventory Item Site (Qty. On Hand)1:1 | Fully supported | |
| Purchase Order | Purchase Order1:1 | Fully supported | |
| 3PL Service Record | Custom Field + Fulfillment Workflow Note1:1 | Fully supported | |
| Backorder Record | Availability Check + Allocation Note1:1 | Fully supported | |
| Channel Source Label | Custom Field on Sales Order1:1 | Fully supported | |
| Return / Refund | Sales Order (credit) / Inventory Issuemany:1 | Fully supported | |
| Multi-Channel Listing | Inventory Subitem or Cross-Reference1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Kentro ERP & 3PL gotchas
Multi-client 3PL data isolation requires careful scoping
EDI compliance data is format-specific and brittle
Historical inventory positions are snapshots, not audit trails
Acumatica gotchas
API user licenses cap concurrent sessions and request throughput
Multi-tenant filtering requires CompanyID awareness
Custom fields require separate discovery before field mapping
Notes and attachments use a separate linked table structure
Implementation timelines frequently run 3–9 months end-to-end
Pair-specific challenges
Migration approach
Extract Kentro data via API with pagination and rate-limit handling
FlitStack AI connects to Kentro's REST API and exports all products, customers, vendors, open orders, fulfillment history, and inventory snapshots in paginated batches. We implement cursor-based pagination with rate-limit delays to prevent API throttling. Each batch is validated for schema completeness before the transformation stage. The export includes Kentro's internal IDs, timestamps, and custom field values for traceability. We produce a manifest of record counts per object before transformation begins.
Configure Acumatica schema: chart of accounts, Sites, customer classes, and inventory valuation
Before any data lands in Acumatica, your team (or our team) configures the foundational schema. This includes creating a Site per Kentro warehouse, setting Inventory Item valuation methods (Standard, Average, or FIFO) to match Kentro's cost layers, defining customer classes for Bill-To/Ship-To segmentation, and configuring UOM classes. We deliver a schema setup checklist derived from the Kentro data inventory so nothing is missing at import time. This is the most planning-intensive step in an ERP migration and typically takes 1–2 weeks.
Transform and map Kentro data to Acumatica entities with field-level validation
We map each Kentro object to its Acumatica counterpart: Products → Inventory Items with UOM and cost setup, Customers → Customers with Bill-To/Ship-To locations, Orders → Sales Orders with line items and Site routing. Kentro's multi-channel label becomes an OrderSource__c custom field. FEFO priority numbers are preserved as lot/serial records or custom fields for fulfillment sequencing. Custom fields on Acumatica records capture Kentro IDs for post-migration reconciliation. We run a field-level diff against a sample of records to verify the mapping before the full run.
Run a sample migration with field-level diff and inventory reconciliation
A representative slice of Kentro data — typically 100–500 records covering products, customers, open orders, and a fulfillment snapshot — is migrated to Acumatica in a test environment. We generate a field-level comparison report showing source value, mapped value, and any transformation applied. Inventory on-hand in Acumatica is reconciled against the Kentro snapshot by Site and SKU. Any mapping gaps (missing UOMs, unconfigured Sites, value-mapping misses) are corrected before the full run is scheduled.
Execute full migration with delta-pickup and one-click rollback
The full dataset is migrated to Acumatica during a low-activity window. A delta-pickup window (typically 24–48 hours) captures any new orders, inventory changes, or customer updates created in Kentro during the cutover. Audit logs record every operation. If reconciliation reveals gaps — for example, a shipment quantity mismatch or a missing Site — one-click rollback reverts the import without touching the source Kentro data. Post-migration, we validate open order balances and inventory positions in Acumatica against the Kentro cutover snapshot.
Platform deep dives
Kentro ERP & 3PL
Source
Strengths
Weaknesses
Acumatica
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Kentro ERP & 3PL and Acumatica.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Kentro ERP & 3PL: Not publicly documented.
Data volume sensitivity
Kentro ERP & 3PL doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Kentro ERP & 3PL to Acumatica migration scoping. Not seeing yours? Book a call.
Walk through your Kentro ERP & 3PL to Acumatica migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Kentro ERP & 3PL
Other ways to arrive at Acumatica
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.