Migrate from Konnect ERP to Infor CloudSuite Corporate

Konnect ERP Customer records (name, contact details, GSTIN, billing address, outstanding balances) map to Infor CloudSuite Business Partner records with the customer flag set. The GSTIN field maps to the Tax ID or VAT Registration field in Infor's Business Partner master. Outstanding balance is preserved as an open AR amount on the Business Partner record but Infor recommends carrying forward open invoices as AR/AP transactions rather than summary balances. We validate that every Customer has a corresponding state code before import because Infor CloudSuite tax jurisdiction assignment depends on the address state.

Konnect ERP Items (SKU, description, unit of measure, HSN code, cost, price) map to Infor CloudSuite Item Master records. The HSN code from Konnect ERP maps to the Tax Code field on the Item Master; we flag any HSN code that does not have a corresponding Infor tax code entry and escalate for manual resolution before the item import runs. Unit of Measure maps from Konnect's UOM field to Infor's UOM code with a lookup against the Infor UOM conversion table.

Konnect ERP Chart of Accounts entries (account code, name, type, parent) map to Infor CloudSuite Chart of Accounts with a customer-provided mapping table. Account codes vary by company setup in Konnect ERP; we extract the full COA and apply a destination-account mapping table before import. Infor CloudSuite enforces a sequential load order for the COA (account types before individual accounts, parent accounts before child accounts), which we honor explicitly. Any Konnect ERP accounts without a mapped Infor equivalent are flagged in the pre-migration report for the customer to decide on new account creation.

Outstanding Konnect ERP invoices (open/closed status, amounts, due dates, customer reference, line items) map to Infor CloudSuite AR Open Invoice records. The Customer ID in Konnect ERP must resolve to a Business Partner ID in Infor CloudSuite, which requires the Business Partner import to complete first. Invoice line items reference Item IDs that must have been migrated to the Item Master before the invoice import runs. We preserve invoice date, due date, invoice number, and GST tax breakdown as separate fields in Infor CloudSuite's invoice header.

Konnect ERP Project records (customer association, billing plan, milestone schedule, man-hour allocations) map to Infor CloudSuite Project or Work Order depending on the CloudSuite edition in use (Industrial vs Distribution). The customer association maps to the Business Partner reference on the Project. We preserve the full project structure including milestone dates and allocate the project man-hour budget to Infor's labor tracking module. Projects without a valid customer reference in Konnect ERP are held in a pre-migration queue.

Konnect ERP Timesheet records (employee reference, project reference, date range, hours logged) map to Infor CloudSuite Labor Tracking entries. The Employee reference must resolve to an Infor Employee ID, and the Project reference must resolve to an Infor Project or Work Order ID. We pre-map all Employee and Project IDs before the timesheet import runs. Entries without a valid project reference are excluded from migration with a count reported in the pre-migration reconciliation.

Konnect ERP Employee records (personal details, department, designation, effective-dated status, compensation) map to Infor CloudSuite Employee Master. The employee's state and country determine the payroll jurisdiction in Infor Workforce Management. We export all active and terminated employees within a defined retention window (typically two years) and flag any employee with a missing department or designation for manual resolution before import. Active compensation fields migrate to Infor's pay component structure with a mapping table for the customer's review.

Konnect ERP E-Invoicing and E-Way Bill records (GSTIN-tagged with HSN for goods and SAC for services) map to Infor CloudSuite Tax Register entries. The HSN/SAC code remapping is the most complex field-level transformation in this migration because Infor CloudSuite uses a jurisdiction-specific tax code table that may not contain the same HSN/SAC values stored in Konnect ERP. We generate a pre-migration HSN/SAC gap report listing every unique code in Konnect ERP that has no Infor CloudSuite counterpart, and the customer creates the missing tax codes in Infor before the GST transaction import runs. IRN (Invoice Reference Number) from Konnect ERP's E-Invoicing module maps to the External Reference field in Infor.

Konnect ERP Vendor records (if the Purchases module is active) map to Infor CloudSuite Business Partner records with the vendor flag set. The vendor's PAN and GSTIN map to the Tax ID fields. Vendor outstanding balances (AP) map to Infor CloudSuite AP Open Invoice records in the same manner as AR records. If the Konnect ERP Purchases module is not active in the source instance, we skip this object and document the absence in the pre-migration scope confirmation.

Konnect ERP inventory stock records (item reference, warehouse, quantity on hand, last transaction date) map to Infor CloudSuite Inventory On Hand records. We require the Item Master to be loaded first so that item ID references are valid. Warehouse mapping from Konnect ERP warehouse codes to Infor CloudSuite site codes is required and is validated during the pre-migration reconciliation step. Inventory valuation method (FIFO, average cost) is preserved in the Item Master configuration migrated in the Items object.

If the Konnect ERP Manufacturing module is active, BOM records map to Infor CloudSuite Bill of Materials with component items resolved against the Item Master. Routing records (process steps, work centers, cycle times) map to Infor CloudSuite Routing or Work Center definitions. We flag any BOM with a component item not found in the Item Master and hold the BOM for manual resolution. BOM and Routing migration is skipped if the Manufacturing module is not active in the source instance.

Konnect ERP user-defined fields on any active module are captured as part of the module-level extraction. We map these to Infor CloudSuite extended fields or user-defined fields using Infor's configuration API. The customer identifies which custom fields are business-critical during scoping; fields not identified are excluded. Custom field type mapping (text to text, number to number, date to date) is validated before import, and type mismatches are escalated.