Migrate from Elvis Business ERP to Microsoft Dynamics 365 Business Central

Elvis Customer records map to Dynamics 365 Customer Master. In Finance & Operations and Supply Chain Management, Customers are a separate entity type with address, contact details, and payment terms. In Business Central, the CRM-style Customer record is used for sales-facing records. We determine the target entity type during discovery based on the Dynamics 365 edition selected. Any custom customer fields in Elvis require field-level mapping to the corresponding Dynamics 365 extension fields.

Elvis Vendor records transfer to Dynamics 365 Vendors with contact information, banking details, and payment terms preserved. If Elvis uses a vendor classification scheme not present in Dynamics 365, we flatten the hierarchy during migration. Value mappings for payment terms (Net 30, Net 60) are applied from the Elvis vendor record to the Dynamics 365 Vendor payment terms.

Elvis Item masters including SKU, description, unit cost, and pricing tiers map to Dynamics 365 Released Products or Business Central Items. The item type (Stock, Service, or Bundle) is determined by the Elvis item category. If Elvis uses category structures not present in the destination, we collapse or flatten them. Product variants in Dynamics 365 (size, color, dimension) are created from Elvis item variant fields if present.

Elvis account numbers and names transfer to Dynamics 365 Main Accounts (Finance & Operations) or G/L Accounts (Business Central). Account type mappings — Asset, Liability, Equity, Revenue, Expense — must be confirmed against the destination's chart structure and legal entity requirements. Dynamics 365 supports multi-segment COA structures (company, division, department, cost center), and we map Elvis's single-segment account numbers into the configured segment structure during migration.

Outstanding Elvis vendor invoices transfer as open purchase ledger entries to Dynamics 365. We preserve invoice reference numbers, due dates, open amounts, and vendor references. Aged balances must reconcile before and after cutover. If Elvis stores AP as summary aging records rather than individual invoice lines, we request the full invoice-level detail from the vendor export before migration.

Outstanding Elvis customer invoices transfer as open sales ledger entries to Dynamics 365. We preserve invoice reference numbers, due dates, open amounts, customer references, and currency. Aged AR balances must reconcile to the source before cutover. Credit memos and down payments are mapped to the corresponding Dynamics 365 transaction types.

Historical Elvis sales invoice headers and line items transfer to Dynamics 365 invoice records. Invoice status (Paid, Open, Voided) migrates with the record. PDF attachments associated with invoices require separate file export and re-upload handling — we track each document's association with its parent invoice record during transfer and reattach as document handling records in Dynamics 365.

Historical Elvis purchase invoices transfer to Dynamics 365 purchase invoice records. Line items map to the invoice line entity with item number, quantity, unit price, and tax information. We flag any invoices with mismatched tax codes between Elvis and the destination tax setup for customer review before import.

Elvis user records including name, email, and role assignments transfer to Dynamics 365 User records backed by Azure Active Directory. We map Elvis user roles to the corresponding Dynamics 365 security roles and responsibility centers. If a user's Elvis role has no direct Dynamics 365 equivalent, we assign the closest matching security role and flag it for the customer's admin to finalize permission sets post-migration.

Uploaded files attached to Elvis records transfer via file export and re-upload to Dynamics 365 document handling. We track the association between each document and its parent record (Customer, Vendor, Item, or Invoice) during transfer and re-establish the link in the destination. File types, original upload timestamps, and file names are preserved.

Elvis payment term definitions, tax code structures, and currency settings transfer as configuration data to Dynamics 365. Dynamics 365 Finance and Operations requires a 'golden configuration environment' for configuration data management per Microsoft's implementation guidance. We create this configuration template first, validate it in a sandbox migration, and use it as the source of truth for production migration.

If Elvis stores custom entity types beyond the standard Customer, Vendor, Item, Invoice, and User objects, we map each to a corresponding Dynamics 365 extension entity or custom table. Dynamics 365 supports custom fields and tables in both Business Central (AL extension model) and Finance & Operations (cloud-native extensions). We pre-create the destination schema, including all custom fields and lookup relationships, before importing any custom entity data.