Migrate from Konnect ERP to Microsoft Dynamics 365 Business Central

Konnect Customer records map to Dynamics 365 Customer (Account in Finance and Operations, Customer in Business Central). We preserve name, contact details, GSTIN as Tax Registration Number, billing address, and outstanding balance. The primary-address constraint in Dynamics 365 requires that Konnect's multiple primary-flagged addresses (invoice, delivery) be split into separate Address records in the destination. Any Customer record without a valid GSTIN is flagged for verification before import because GSTIN is required for Indian E-Invoicing compliance.

Konnect Item master records map to Dynamics 365 Items. We preserve SKU (mapped to Item Number or Product Number depending on the Dynamics 365 edition), description, unit of measure, HSN/SAC code as the tax code reference, and standard cost/price fields. Items marked as inventory items in Konnect create inventory setup in the destination's warehouse module; service items create service items without inventory tracking. Item type (inventory vs service vs hybrid) is preserved as a configuration flag.

Konnect COA account codes and hierarchies extract as a flat list and require a destination-account mapping table before import. Dynamics 365 enforces Account Type (Income, Expense, Asset, Liability, Equity) and Account Category for financial statement grouping. Financial Dimensions in Dynamics 365 (Cost Center, Department, Business Unit, Project) have no direct Konnect ERP equivalent and must be designed during the schema phase. We deliver the COA mapping table with account-by-account decisions reviewed by the customer's finance team before migration.

Outstanding Konnect invoices (open status, amounts, due dates) migrate as Customer Invoices in Dynamics 365. Invoice line items reference Item IDs that must be migrated before invoice import so that the line item lookup resolves correctly. Closed invoices (fully paid, fully written off) migrate as historical records if the customer requests full history; otherwise they are archived. GST amounts on invoices are recalculated from the destination's tax code setup rather than copied from Konnect to ensure compliance consistency.

Outstanding vendor bills in Konnect ERP migrate as Vendor Invoices in Dynamics 365. The vendor record must exist in the destination vendor master before AP import, so vendor data is migrated in the same phase as customer data. Tax amounts are recalculated from destination tax codes, consistent with the Accounts Receivable approach. Open/closed status is preserved in a custom field for reconciliation.

Konnect Project records map to Dynamics 365 Projects or Jobs depending on the destination edition. Project customer association, billing plan, milestone schedule, and man-hour allocations migrate as project structure. Project-linked timesheet entries reference the project ID, which must be resolved during migration. We flag any Project without a valid customer association in the destination for admin review because Projects without a legal entity or customer contract may need reclassification.

Konnect timesheet records (employee linked to project with date range and hours logged) migrate as time transactions in the destination project management module. Entries without a valid project reference in the destination are pre-mapped or excluded; entries without a valid employee reference are held in a reconciliation queue. The employee's Konnect department and designation map to the destination's dimension structure (Cost Center or Department) if those dimensions are configured.

Konnect Employee master records map to Dynamics 365 Worker or Employee. We preserve personal details, department, designation, effective-dated employment status, and active compensation fields. Salary, benefits, and payroll data migrate only if the destination uses Dynamics 365 Payroll or a connected payroll module; otherwise they are flagged as outside scope and archived. Employee photo and document attachments migrate as document records attached to the Worker or Employee.

Konnect GST transaction records carry GSTIN, HSN/SAC codes, and IRN (Invoice Reference Number) for E-Invoicing validation. These require field-level mapping to the destination's tax code structure. HSN/SAC codes in Konnect may not align one-to-one with Dynamics 365's Indian GST tax code table, so we flag any HSN/SAC value without a direct destination match and escalate before import. E-Way Bill metadata (vehicle number, transportation mode, distance) migrates as extended invoice attributes. IRN validation status is preserved in a custom field on the migrated invoice for audit trail.

Open sales and purchase orders in Konnect ERP migrate as Orders in Dynamics 365. Order status (open, invoiced, cancelled) maps to the destination order lifecycle. Line items require Item ID resolution. Ordered quantities vs invoiced quantities are preserved so that partially invoiced orders continue correctly in the destination. Completed and closed orders are migrated as historical records if requested; otherwise they are excluded to reduce migration scope.

Konnect stores tax rates and GST slabs (5%, 12%, 18%, 28%, exempt, nil-rated) as part of the tax setup. These must be manually replicated in Dynamics 365's Tax Configuration (Tax Codes, Tax Groups, Tax Page). We deliver a written tax configuration checklist with each Konnect tax rate mapped to the corresponding Dynamics 365 Tax Code and Tax Group combination. The customer or a tax consultant implements the configuration before financial record migration begins.

Konnect vendor records map to Dynamics 365 Vendor. We preserve vendor name, contact details, GSTIN as Tax Registration Number, billing address, and payment terms. Vendor records must exist before AP invoice migration can begin. Vendors without a valid GSTIN are flagged for verification because GST-compliant vendor records are required for Indian E-Way Bill generation.