Migrate from Konnect ERP to Acumatica

Konnect CRM customer records map to Acumatica Customer screen (CR202000). Primary address, contact email, payment terms, and credit limits transfer directly as matching fields. Konnect customer-specific custom fields such as tier classifications or industry tags are flagged for Acumatica custom attribute creation via PXCacheExtension before records load. The customer type field uses value mapping to Acumatica Customer Class IDs.

Konnect vendor master records map to Acumatica Vendor screen (AP202000). Remit-to address, 1099 reporting flag, tax identification number, and payment terms transfer as-is. Multi-address vendor records in Konnect collapse to one primary remit address in Acumatica with secondary addresses stored as separate location records linked to the vendor entity. Vendor class assignments are mapped via value mapping during the schema review.

Konnect product catalog items map to Acumatica Inventory Item (IN202000). Stock items, non-stock items, and service items each have a corresponding Item Type in Acumatica's pick-list. Konnect's unit-of-measure conversions are preserved in Acumatica's UOM classes, and standard cost values transfer to the StdCost field. Item class assignments map directly to Acumatica ItemClass IDs.

Konnect project records carry customer association, billing plan, and man-hour allocation. These map to Acumatica Projects (PM301000) where the project template, budget tiers, and cost codes are re-created based on the approved mapping table. Konnect project-level billing triggers transfer as Acumatica project invoices linked to the same customer. Project status values map to Acumatica Project Status pick-list.

Konnect timesheet rows (employee, date, hours, project task, cost code) map to Acumatica Time Entries (EP301000). Original dates and labor costs carry over as custom fields since Acumatica's CreatedDateTime is set at migration time. Approval status is reset to draft for re-approval post-migration. Employee matching uses email resolution against the EP301000 employee master.

Konnect project invoices map to Acumatica AR Invoices (AR301000) linked to the corresponding project. Konnect standalone AR invoices also map to AR301000. Tax amounts use Konnect's tax codes mapped to Acumatica Tax Zone IDs; GST/HST applicability is carried forward as tax jurisdiction assignments. Document status values map via value mapping to Acumatica AR Document Status.

Konnect vendor bills map to Acumatica AP Invoices (AP301000) linked to the vendor. Line-item distribution to GL accounts and subaccounts is resolved using the Konnect expense-account mapping reviewed during the schema-planning phase. Prepayments and retainage flags carry forward as Acumatica holds on the document.

Konnect's flat account codes require decomposition into Acumatica's two-field account structure. We work with your finance team to define the subaccount segmentation (e.g., by department, region, or cost center) and deliver a mapping table before any transactional data loads. Account type, posting settings, and active/inactive status transfer directly.

Konnect multi-location data is consolidated into Acumatica Branches (CS100000). If Konnect used separate database instances per branch, we merge them into a single multi-branch Acumatica tenant with inter-branch inventory transfer configurations, centralized general ledger posting, and branch-specific tax zone assignments. Each branch receives its own branch ID and is configured for appropriate financial entity settings.

Konnect custom properties — e.g., customer-tier flags, project-specific cost codes, or item-classification tags — require Acumatica PXCacheExtension classes. We document each custom field's data type and populate a schema plan that your Acumatica developer or partner implements before the data migration runs.

Konnect document attachments on invoices, projects, and customer records download and re-upload to Acumatica's note file storage. Files are associated to the migrated record by reference ID so the attachment history remains visible in the document's Attachments tab post-migration. We preserve the original file names and upload timestamps for audit trail continuity.

Konnect workflow definitions — project-approval chains, document-release workflows, email notification rules — do not transfer. We export the full workflow definition as a structured reference document so your Acumatica administrator can rebuild approval maps in Acumatica's Workflow Engine or through custom handlers. The export includes screen IDs, step sequences, approver assignments, and conditional logic.