Migrate from COINCAP ERP to Microsoft Dynamics 365 Business Central

COINCAP ERP organises financial accounts within its finance module. We extract the full account hierarchy, account type, and posting group assignments and map them to D365's G/L Account structure. Indian tax codes (GST/SGST/CGST) are extracted as separate tax component mappings rather than embedded in the account code. We preserve the COINCAP account code as a reference field in D365's G/L Entry No. or External Document No. for audit trail continuity. D365's account structure supports dimensions (Cost Center, Department, Division) that COINCAP may not have; we map COINCAP cost-center assignments to D365 DefaultDimension during import.

Party master records for customers live in COINCAP's sales module. We extract customer name, GST registration number (GSTIN), address details, payment terms, credit limit, and salesperson assignment. COINCAP may store multiple addresses per customer (billing, shipping, plant); D365 Customer supports one primary address with additional address records via the Address subtable. We map the COINCAP primary address to D365's Address field and flag any secondary addresses for manual entry post-migration or for the customer to map as related Address records.

Vendor master records in COINCAP's purchase module map to D365 Vendor. We extract vendor name, PAN and TAN references, GSTIN, address, payment terms, and bank details. Vendor-to-Customer cross-references (a vendor who is also a customer) must be identified during scoping because D365 maintains separate Customer and Vendor tables; these become two records with a cross-reference field populated. COINCAP's vendor-specific tax categories map to D365's Tax Business Subject configuration.

Item masters in COINCAP cover raw materials, semi-finished goods, and finished goods across the inventory module. We map item codes, descriptions, UOMs, pricing tiers, item category codes, and product type. COINCAP's inventory valuation method (standard cost, average cost, FIFO) maps to D365's Costing Method field. Stock-keeping unit tracking levels from COINCAP (none, serial, lot) map to D365's Item Tracking Code. Item reordering policies migrate as D365's Reorder Point or Reorder Quantity on the Item card.

COINCAP manufacturing module BOMs may have multi-level nested hierarchies that D365 does not store identically. We flatten multi-level COINCAP BOMs into D365's single-level BOM with multiple BOM versions, or into D365's multi-level production route structure if the customer requires D365's production module for scheduling. We extract each BOM component's quantity per assembly, scrap percentage, and operation steps and map them to D365 BOM Lines and Production Order Routing. BOM version validity dates from COINCAP migrate to D365's Starting Date and Ending Date on BOM Version.

Outstanding payables tracked in COINCAP's finance module are extracted as open vendor ledger entries with due dates, invoice numbers, amounts, currency codes, and vendor references. We load these as D365 Vendor Ledger Entries with Document Type = Invoice and Open = Yes. Aged trial-balance reconciliation is required before migration to confirm that COINCAP's open AP total matches D365's posted vendor ledger after import. Any COINCAP post-dated checks or payment advice records map to D365 Check and Payment Journal entries.

Outstanding receivables from COINCAP's finance module migrate to D365 Customer Ledger Entries with Open = Yes. We extract invoice number, customer reference, due date, amount, and currency. COINCAP may track partial payments against invoices; D365 handles this through the Detailed Customer Ledger Entry subtable. Aged receivables reconciliation is required post-import to confirm totals match. Any credit notes or prepayment records in COINCAP map to D365 Document Type = Credit Memo or Prepayment entries.

All posting transactions in COINCAP are stored as vouchers—sales invoices, purchase receipts, journal entries, debit notes, credit notes. We segment by COINCAP voucher type and map each segment to the corresponding D365 document: sales vouchers to Sales Invoice or General Journal, purchase vouchers to Purchase Invoice or General Journal, and pure journal vouchers to General Journal Lines. Date-range scoping is required because historical transaction volume can be large. Very large transaction histories may require batched migration with D365's data management framework import jobs.

COINCAP assigns users to roles that gate access to specific modules and functions. We extract user IDs, names, email addresses, and role assignments. D365 requires the customer's Azure Active Directory tenant to provision users before migration; we coordinate user provisioning with the customer's tenant admin. COINCAP role names are mapped to D365 Permission Sets or Security Roles by functional area (finance users get GL Accountant role, inventory users get Warehouse User role, etc.). Passwords and session tokens cannot be migrated and must be reset post-migration.

COINCAP ERP deployments across 11 vertical markets frequently include module-specific custom fields that are not present in the base product. These are invisible without direct COINCAP schema discovery. We conduct a vendor-assisted schema audit to identify all custom field definitions, their data types, and the objects they extend. Each discovered custom field is then created as a D365 custom field on the corresponding table (Extension fields in Business Central, custom fields on the entity in Finance and Operations). Industry-specific custom fields in manufacturing, trading, or project verticals are documented separately in the migration handoff package with their COINCAP table.column reference.

COINCAP ERP may store scanned documents and attachments linked to transactions or master records. There is no documented public API endpoint for bulk attachment export. We flag attachment dependencies during discovery and present three options to the customer: manual re-upload post-migration (suitable for small volumes), a separate document-migration workstream with COINCAP vendor assistance and a custom file extraction routine, or accepting that attachments will not migrate. We do not perform custom vendor development to extract attachments as part of the standard migration scope.

COINCAP ERP includes Indian regulatory compliance configurations for GST, fiscal year setup, and Indian accounting conventions. These do not migrate automatically. We extract the COINCAP fiscal year definition and GST tax component structure (CGST rate, SGST rate, IGST rate, HSN code mappings) as a written configuration inventory. The customer's D365 administrator or a D365 implementation partner re-implements these as Tax Codes in D365's Tax engine and the Fiscal Year Calendar in General Ledger Setup. Indian states and Union Territory jurisdiction codes are mapped to D365 State/Territory fields.