Migrate from Vault-ERP to Microsoft Dynamics 365 Business Central

Vault-ERP allows customized account hierarchies per tenant, so every migration requires a pre-migration schema discovery pass to enumerate the actual account structure. We extract the full account hierarchy via the NetSuite API and map it to a Dynamics 365 Main Account structure with optional financial dimensions (Cost Center, Department, Division, Project) that the customer defines during scoping. Account type mapping (Asset, Liability, Equity, Revenue, Expense) transfers directly; custom account classifications require value mapping per instance.

Vault-ERP Customer records map to Dynamics 365 Customer with contact details, addresses, payment terms, and credit limits transferred 1:1. The custCustomerV3 OData entity in Dynamics 365 Finance and Operations accepts customer groups, currency, and payment schedule. We map Vault-ERP's custom classification fields to Dynamics custom fields on the Customer table. Customer address roles (Invoice, Delivery, Primary) map to LogisticsPostalAddress fields with the appropriate LocationRole.

Vault-ERP Vendor records map to Dynamics 365 Vendor with the same contact, address, payment term, and credit limit patterns as Customer. The VendVendorV2 entity accepts vendor groups, currency, and WHS (warehouse management) flags. One-to-one mapping with value transformation for any Vault-ERP-specific vendor classification fields.

Vault-ERP Items include inventory, non-inventory, and service types. We map item type, pricing, BOM data, and storage dimensions to Dynamics 365 Released Product. Item type in Vault-ERP (Inventory Item vs Non-Inventory Item vs Service) maps to ProductType and InventoryType fields in Dynamics. Custom item fields require per-instance value mapping. BOM structures in Vault-ERP map to Bill of Materials in Dynamics 365 Engineering.

Open payable records carry outstanding balances, payment terms, and linked vendor references. We map these to Dynamics 365 open vendor transactions. Currency and subsidiary metadata must be preserved; multi-currency open AP requires exchange rate locking at migration date to prevent post-migration FX adjustments from distorting the balance.

Open receivable records map to Dynamics 365 open customer transactions. Vault-ERP's payment terms and due date logic map to CashDisc and PaymentTerm on the Customer Invoice. Currency handling mirrors Open AP. Invoice references and linked transaction IDs transfer as LedgerDimension references.

Vault-ERP Sales Orders reference customers, items, pricing, and fulfillment status. We map order headers to SalesTable and order lines to SalesLine. The Vault-ERP order layout may include custom fields that require per-instance mapping to SalesTable custom fields. Order status (Open, Invoiced, Shipped) maps to SalesStatus. Notes and terms migrate as InventSetting references.

Mirror of Sales Order mapping for purchase side. Vault-ERP PO records with vendor references, item lines, quantities, and delivery dates map to PurchTable and PurchLine entities. Vendor lead times and delivery addresses map to PurchDeliveryDetails.

Vault-ERP Employee records include compensation changes, job title transitions, and department reassignments effective on specific dates. We extract the full effective-dated change log for each employee and load it as a sequence of HcmEmployment records with validFrom and validTo dates preserved. The latest compensation record becomes the current HcmWorker profile. Historical pay rates and job titles are stored in HcmWorkerPendingCompensation and HcmPositionWorkerAssignment for audit continuity.

Vault-ERP time tracking records with billable and non-billable hours linked to projects or employees map to Dynamics 365 Workflow Journal or Time and Attendance modules. Project association migrates as ProjJournalTable with ProjJournalTrans. Hour categorization (billable vs non-billable) maps to ProjCategoryId. Custom time entry fields require per-instance mapping.

Document storage in Vault-ERP uses the platform's file management layer. We export file references, metadata, and binary content and load them into Dynamics 365 SharePoint document libraries or Dataverse attachment storage. We verify every migrated document by SHA-256 checksum comparison after transfer and flag any attachment where source and destination hashes do not match. File naming conventions may need normalization to comply with SharePoint character restrictions.

Bank account definitions and opening balance snapshots migrate to BankAccountTable in Dynamics 365. The account number, SWIFT/BIC, currency, and current balance transfer directly. Bank reconciliation history does not migrate; it starts fresh in Dynamics 365 with the opening balance as the first reconciliation point.

Vault-ERP tax codes reference jurisdiction-specific rates and rules. We extract the tax code definitions and associated rates and map them to Dynamics 365 TaxGroup (for sales tax) and TaxItemGroup (for item-level tax) entities. Jurisdiction alignment requires customer validation because regional tax configurations vary significantly between Vault-ERP and Dynamics 365 tax setup.