Migrate from e-Emphasys ERP to Microsoft Dynamics 365 Business Central

e-Emphasys customer records carry full contact details, billing and branch addresses, credit terms, and linkage to equipment and service history. We map Customer in F&O to the CustCustomerV3Entity or to the Customer and Contact tables in Business Central, preserving branch-level assignments as a custom dimension or a Contact business relationship. Address roles (billing, shipping, branch) map to the Dynamics 365 address-purpose model; if multiple addresses share the same role, we apply a primary-address flag and include others as secondary address records.

Serialized equipment records in e-Emphasys include OEM codes, VIN-equivalent identifiers (EquipmentNumber, SerialNumber), branch assignment, current status, and linkage to the customer record. We map these to Released Products in F&O with the SerialNumber tracked in inventory dimension, or to Items in Business Central with the Serial Item tracking extension enabled. OEM manufacturer codes map to the Product Vendor table; branch assignment maps to a Site/Warehouse dimension or a Business Central Location code. Equipment status (active, rented, sold, consigned) maps to inventory status flags on the product record.

Both serialized and non-serialized parts in e-Emphasys carry bin locations, vendor links, cost tiers, and reorder points. Non-serialized parts map directly to Released Products (F&O) or Items (Business Central) with the appropriate product type. Serialized parts require the inventory dimension model to preserve serial number sequences and are linked to the parent equipment record via a custom relationship table. Bin location maps to warehouse location in F&O or bin code in Business Central. We flag any parts with cost tiers that exceed the destination's standard pricing model for manual review.

Service work orders in e-Emphasys tie to the equipment record, assigned technician, labor hours, parts consumed, and warranty claim association. We map Work Order headers to the Work Order entity in F&O (Service Management module) or to a Service Order in Business Central. Labor lines map to work order lines with the technician's labor rate resolved via the Employee resource rate. Warranty claim associations migrate as a linked Service Agreement or warranty reference on the work order. If the destination uses Project management for job costing, work orders map to Projects with the work order number preserved as the project ID.

Rental contracts in e-Emphasys store complex rate structures including daily/weekly/monthly billing tiers, equipment swap conditions, and early-return penalty rules in a single contract record. We extract contract terms into an intermediate schema, map the contract header and primary rate tier to the Microsoft Dynamics 365 Sales Agreement or Contract, and flag any nested billing tiers and swap conditions that exceed the destination's native contract configuration as a written reconciliation item for the customer's admin. Active rental contracts are flagged for manual verification before go-live because the billing model is not fully representable in standard Dynamics 365 without custom fields.

Whole goods sales orders and quotes in e-Emphasys link to customer and equipment records with pricing tiers and OEM incentive codes. We map Sales Order headers to the SalesOrderHeaderV2Entity in F&O or to Sales Orders in Business Central. Line items carry the equipment or part number, quantity, unit price, and discount tiers. OEM incentive codes map to a trade allowance or promotional price on the sales line. Open orders migrate with order status preserved; completed orders migrate as order history.

GL accounts, journal entry headers, and line items export from e-Emphasys with full account structure and period associations. We map the chart of accounts to the Dynamics 365 Main Account structure, preserving account numbers and financial dimension assignments (branch, department, cost center) as Dynamics 365 financial dimensions. Open journal entries migrate with posting date, account, debit, credit, and currency preserved. Closed period entries migrate as historical journal batches. We do not re-post or re-validate closed periods; period lock status is preserved from the source.

Vendor records, open invoices, and payment history export from e-Emphasys AP module with full vendor linkage and PO-to-invoice associations where they exist. We map Vendor records to the VendVendorV2Entity in F&O or to Vendors in Business Central, preserving payment terms, currency, and vendor classification. Open AP invoices migrate as vendor invoice journals with invoice number, invoice date, due date, and amount. Payment history migrates as posted payment journals linked to the original invoices.

Customer invoices, payments, and AR aging data export from e-Emphasys with customer linkage, invoice details, and payment history. We map open invoices to the CustInvoiceJournalEntity in F&O or to Customer Invoice Journals in Business Central. Payment history migrates as posted payment journals with the payment method and reference preserved. AR aging buckets migrate as at least one historical aging snapshot for reporting continuity. Customer credit limits map to the Credit Limit field on the Customer record.

Employee records in e-Emphasys carry labor rates, certifications, skill categories, and branch assignments. We map to Workers in F&O (Human Resources module) or Employees in Business Central, preserving labor rate as the standard cost on the resource or worker record, certifications as custom fields, and branch assignment as a default dimension or Location. We flag any labor rate schedules that exceed the destination's standard cost model for manual review.

Warranty records in e-Emphasys tie serialized equipment to OEM warranty claims with coverage start date, expiration date, coverage type, and claim history. We map active warranty records to Service Agreements in F&O or to a custom Warranty table linked to the Product record in Business Central. Claim history migrates as service order history attached to the warranty agreement. OEM warranty codes map to the coverage type field; any claim records exceeding the destination's maximum line item count per service order are flagged for manual reconciliation.

e-Emphasys supports user-defined fields across many modules. During discovery we identify all custom fields and their data types, map them to the destination's extension model (F&O extensions via Power Apps or X++ extensions; Business Central custom fields via the built-in Custom Fields page), and include them in the field mapping inventory. Custom field data migrates into the destination custom field alongside the standard field data in the same record batch.