Migrate from ECOUNT ERP to Microsoft Dynamics 365 Business Central

Ecount Items with code, description, unit of measure, cost, price, and BOM links map to Dynamics 365 Item Card records. We export the item master via structured Excel, map Ecount's item type (Finished Goods, Raw Materials, Service) to Dynamics 365 Type (Inventory, Service, Non-inventory), and preserve any BOM sub-material links for BOM reconstruction in Dynamics 365. Standard cost and direct unit cost migrate to the item's cost fields; the customer configures inventory posting groups during destination setup.

Ecount BOMs with multiple levels and process-level inventory adjustments map to Dynamics 365 Production BOM lines and optional Routings. We extract the BOM structure including sub-material codes, quantities per, and scrap percentages, then configure the destination BOM header and line records with the correct unit of measure conversions. If Ecount uses process-level adjustments, we document the routing steps for manual Route configuration in Dynamics 365 Manufacturing.

Ecount Customer records with contact details, payment terms, credit limits, and outstanding balances map to Dynamics 365 Customer Card records. We extract via Excel, map Ecount's payment term codes to Dynamics 365 Payment Terms, and preserve the customer balance as an aging snapshot for reconciliation after go-live. Custom fields added to the Ecount customer input screen become named text or numeric fields on the Dynamics 365 Customer Card.

Ecount Vendor records mirror the Customer structure with supplier-specific fields. We follow the same Excel extraction and field-mapping process as Customer migration, mapping vendor payment terms to Dynamics 365 Payment Terms and preserving any custom vendor-level fields as named fields on the Vendor Card. Vendor balance and outstanding purchase amounts are included as reconciliation snapshots.

Ecount Sales Slips (header and line items) map to Microsoft Dynamics 365 Sales Orders or Sales Invoices depending on the customer's fulfillment model. We extract by period, preserving quantities, unit prices, tax codes, and the Ecount slip number as an external document number. The Dynamics 365 number sequence for Sales Orders must be pre-created; we resolve Item references against the migrated Item master before inserting lines.

Ecount Purchase Slips with incidental cost allocations map to Dynamics 365 Purchase Orders or Vendor Invoices. Header fields (vendor, date, currency) migrate directly; line items resolve against the migrated Item master. Incidental costs (freight, duty, handling) are mapped to Direct Cost accrual or landed cost categories depending on Dynamics 365 configuration.

Ecount's account structure with departments and cost centers maps to Dynamics 365 G/L Account numbers with corresponding posting groups. We extract account codes, names, and account categories, then configure the Dynamics 365 Chart of Accounts with the same numbering logic and assign posting definitions. Department-level restrictions in Ecount map to Dynamics 365 dimension-based access control.

Ecount Employee records including compensation, attendance, and payroll history map to Dynamics 365 Human Resources Employee records. We extract effective-dated compensation changes with their start dates to preserve salary history in the destination. Attendance records migrate as Absence registrations in Dynamics 365 Human Resources. If Ecount payroll data is required, the customer configures the Payroll module or a payroll integration separately because payroll data migration involves tax and regulatory nuance that requires dedicated scoping.

Ecount allows companies to add, rename, or delete fields on any input screen with optional calculation formulas. These custom fields exist in the screen configuration rather than a standard metadata API. We request the customer's upload templates or screen export during scoping, identify all active columns, and pre-create typed custom fields on the corresponding Dynamics 365 table (Customer, Vendor, Item, Sales Line, etc.) with the same column order and formula logic documented for the customer's admin to configure validation rules post-migration.

File attachments linked to Ecount slips and records are extracted as binary files with their reference metadata (record type, record number, attachment name). We re-associate them in Dynamics 365 by creating Document Attachment records that link the file to the corresponding migrated record using the record ID map generated during migration. Any file that cannot be linked to a migrated record is held in a catch-all document library for manual re-association.

Ecount bank statement data extracted via the bank statement service maps to Dynamics 365 Bank Account Reconciliation records. We extract transaction date, description, amount, and reference, then create bank account ledger entries and reconciliation lines. The customer configures the bank account in Dynamics 365 before this phase runs.

Ecount export invoices and packing lists generated from sales slips, including L/C issuing bank and shipper details, map to Dynamics 365 Posted Sales Invoices and Posted Shipments. We extract the complete invoice history, map invoice numbers to external document numbers, and preserve the L/C and shipper references as invoice comment lines or attached scanned documents. Packing list line detail migrates as shipment line records.