Migrate from CREST ERP to Microsoft Dynamics 365 Business Central

CREST ERP Customer records map to Dynamics 365 Account (Finance and Supply Chain Management) or Customer (Business Central). Each Customer carries contact details, addresses, credit limits, and payment terms. CREST ERP stores multiple addresses per customer; Dynamics 365 F&SCM allows separate Invoice address and Delivery address with one marked as primary. We flag any customer with more than two address records and restructure these as address-reference pairs during the transform phase. Credit limits map to the Dynamics 365 Customer credit limit field.

CREST ERP Vendor records map to Dynamics 365 Vendor (F&SCM) or Vendor (Business Central), with supplier details, bank information, and performance ratings. Vendor payment terms map to Dynamics 365 Vendor terms records. CREST ERP's vendor-supplied catalogue records map to vendor-specific trade agreements in Dynamics 365 if the customer uses the Trade Agreements module. We preserve any vendor notes or performance ratings as custom fields on the Vendor record.

CREST ERP Items carry SKU, description, pricing, unit of measure, and optionally BOM and routing data. Items map to Dynamics 365 Released Products with Product type (Item, Service, or BOM) set per CREST ERP item category. The BOM field in CREST ERP maps to a Dynamics 365 Bill of Materials entity if the item type is BOM. We validate that CREST ERP BOM levels do not exceed the destination's nesting limit and flag any BOM with more than six levels for manual review before import.

CREST ERP GL account codes, names, account types, and cost center assignments map directly to Dynamics 365 Main Accounts. CREST ERP account segments map to the Dynamics 365 financial dimension structure (configured in General Ledger > Chart of Accounts > Configure account structures). We preserve account codes exactly, validate against Dynamics 365 account format rules, and flag any account with a segment count that does not match the destination's configured dimension structure.

Open AP records migrate with vendor association, invoice number, amount, due date, and current payment status. CREST ERP's open AP ledger entries map to Dynamics 365 F&SCM Vendor Invoice Journal lines (pending invoice) or to open AP Invoice records depending on the customer's Accounts Payable workflow preference. We track which invoices remain open at migration cutover and exclude fully paid records. Partial payments and credit memos migrate as offset line items with correct signs.

Open AR records preserve customer association, invoice number, amount outstanding, and aging bucket. CREST ERP's open AR entries map to Dynamics 365 F&SCM Free Text Invoices or Sales Invoice lines (depending on whether the source documents were sales invoices or credit memos). We flag credit memos and partial payments for correct offset handling and verify that the AR aging buckets in Dynamics 365 match the aging periods configured in CREST ERP.

Historical GL journal entries from CREST ERP span multiple years and significant volume. We chunk these into migration batches of 10,000 lines per run, sequencing by posting date and resolving account code references before inserting into Dynamics 365 via the OData or REST API. CREST ERP's journal voucher numbers map to Dynamics 365 Journal batch number and voucher number. Inventory movements and production transactions migrate as separate ledger entry types mapped to the appropriate Dynamics 365 inventory and production journals.

CREST ERP Fixed Asset records include acquisition cost, depreciation schedule, asset category, location, and maintenance history. These map to Dynamics 365 Fixed Assets with the depreciation method translated to the equivalent Dynamics 365 depreciation profile. CREST ERP asset books map to Fixed Asset Books in Dynamics 365, including acquisition date, useful life, salvage value, and accumulated depreciation balance. We compute the depreciated value at cutover and seed the opening balance.

CREST ERP Employee records include personal details, job role, compensation history, PTO balances, and attendance data. These map to Dynamics 365 Human Resources Worker records via the HcmWorker entity. Effective-dated compensation records require sequencing to preserve historical pay period data. We migrate the most recent compensation record as the active worker compensation and flag prior effective-dated records for the customer's HR admin to review in Dynamics 365 HR before finalizing.

CREST ERP Department structure maps to Dynamics 365 Operating Units with department codes, names, and parent-child relationships. We validate that cost center assignments on GL accounts align with the destination department hierarchy. CREST ERP departments that are also used as cost centres in the chart of accounts require corresponding financial dimension values created in Dynamics 365 before the GL migration phase.

CREST ERP HR records include leave applications, approvals, leave balances, and attendance logs. Leave types map to Dynamics 365 Human Resources Leave types with custom leave policies translated to the Dynamics 365 Leave plan structure. CREST ERP attendance entries migrate as absence registrations against the Worker record. Custom leave policies and approval workflows may require field-level mapping review and manual recustomization at the destination because Dynamics 365 HR approval flows use Power Automate rather than a native approval table.

CREST ERP Sales Orders carry customer association, line items, quantities, pricing, delivery dates, and order fulfillment status. These map to Microsoft Dynamics 365 Sales Order headers with order lines linked to Released Products and the appropriate Site and Warehouse from CREST ERP inventory dimensions. CREST ERP SFA pipeline stages from the CRM module map to the Dynamics 365 Opportunity or quote stages as a separate mapping scope if the customer uses CRM alongside ERP.

CREST ERP Purchase Orders include vendor linkage, line items, quantities, pricing, expected delivery dates, and receipt status. These map to Dynamics 365 Purchase Order headers and lines. CREST ERP approval workflows on purchase orders require documentation during discovery and manual configuration in Dynamics 365 via the Procurement and Sourcing approval framework. We capture the approval chain steps as a screenshot manifest and deliver it with the workflow recreation guide.

CREST ERP Project records contain budget, resource assignments, tasks, milestones, and time entries. These map to Dynamics 365 Project Operations or Business Central Projects depending on the destination tier. CREST ERP's configurable project templates require re-creation in Dynamics 365 Project; we document each template's task structure, milestone definitions, and budget categories as a project template recreation guide for the destination admin.

CREST ERP custom fields on standard objects and custom objects built within the application lack a documented export API. We capture custom field definitions through database-level inspection and customer-assisted review, then generate a mapping manifest documenting each custom field's destination equivalent. Custom fields that map directly to Dynamics 365 extensible fields (added via the Field service workspace) migrate as configuration. Custom objects that have no direct Dynamics 365 equivalent are documented as requiring manual schema creation in the destination and flagged for the customer's implementation team to rebuild post-migration.