Migrate from Accura to Microsoft Dynamics 365 Business Central

Accura Customer records carry billing contact, shipping contact, and payment terms in a flat structure. We split these into Dynamics 365 Accounts (the company/company name) and Contacts (the individual contacts with roles). The Accura customer number becomes the Account number field; billing address and shipping address map to the Account's invoice address and delivery address respectively. Payment terms from Accura (Net 30, Net 60, COD) map to Dynamics 365 Payment Terms terms. If Accura stores multiple contacts per customer, each migrates as a separate Contact record linked to the parent Account.

Accura Job records are the core entity carrying status, line items (press runs, finishing, materials), pricing, and customer reference. We map Jobs with status Open or In Progress to Microsoft Dynamics 365 Sales Order (draft) records preserving the original job number, order date, and line items. Jobs with status Closed or Completed map as Sales Order historical records or Project transactions depending on whether the print shop tracks jobs as project cost objects. Job-specific custom fields carry forward into Sales Order extensions. Stage names from Accura map to Sales Order status values defined in the Microsoft Dynamics 365 Sales order processing setup.

Accura stock items map to Dynamics 365 Items with Item type = Stocked Item. On-hand quantity from Accura becomes the opening inventory quantity in Dynamics 365 inventory dimensions (Site and Warehouse). Unit cost from Accura maps to the Item's Cost price. Items with negative balances or zero on-hand in Accura are flagged for customer review before import because Dynamics 365 inventory setup requires a valid warehouse and site to post quantities. Lot and serial number tracking migrates if enabled on the source; otherwise it is noted as a configuration step in the destination.

Accura non-stock materials (inks, substrates, third-party services) map to Dynamics 365 Items with Item type = Service or Non-Stocked depending on how the print shop classifies them. Unit of measure and cost basis migrate. Non-stocked items do not carry inventory dimensions in Dynamics 365 and are excluded from physical inventory counts.

Open invoices from Accura migrate as Microsoft Dynamics 365 Sales Invoice records with status = Open or Draft depending on the customer's payment reconciliation state. Invoice number, invoice date, due date, and total amount map directly. Line items from the Accura invoice map to Sales Invoice lines with matching Item numbers, quantities, and unit prices. Accura payment terms determine the due date calculation. Invoice-to-customer linkage uses the Account number resolved from the Customer mapping.

Historical paid invoices from Accura migrate as posted Sales Invoice records in Dynamics 365. They carry a Paid = Yes flag and the original payment date. We migrate them as read-only records preserving the full invoice body and line items. Migrations of historical invoices are scoped to a defined lookback period agreed during discovery to avoid importing stale data that has no operational value.

Accura Vendor records map to Dynamics 365 Vendors. Vendor name, contact info, payment terms, and default currency migrate. Dynamics 365 enforces unique Vendor account numbers; we apply a vendor-prefix convention during import to avoid collisions with customer account numbers. Vendor lead times map to the Vendor's Delivery terms if used in purchase order processing.

Accura user accounts with name, email, role, and department migrate to Dynamics 365 User records. We extract all active and inactive user accounts during scoping and flag inactive accounts for deprovisioning rather than migration, so the customer does not over-license at the destination. User passwords do not transfer and require manual provisioning in Dynamics 365. Role assignments from Accura inform the Dynamics 365 security role assignment but may require adjustment because the two systems have different role permission models.

Accura custom fields added to any object migrate as additional columns in the CSV extract. We carry them into Dynamics 365 as extension fields on the equivalent entity (e.g., cust_pressType__c on Sales Order). Custom fields that have no matching target field are flagged for manual configuration in Dynamics 365 before import. The customer decides during scoping whether to create all custom fields or consolidate some into existing Dynamics 365 field equivalents.

Job files, proofs, and documents stored within Accura are not accessible via CSV export. We produce a file-location inventory listing every document path and the associated Job or Customer record, so the customer can manually retrieve or archive these assets. For organizations that need these files accessible inside Dynamics 365, we document the SharePoint or Azure Blob integration configuration steps as a post-migration task.

Accura job pricing (press rates, setup costs, finishing rates, markups) migrates as Sales Price List lines in Dynamics 365 Trade Agreements if the print shop uses standard pricing. For job-specific estimates that are not standardized across orders, we document the pricing structure for configuration as Sales Order line defaults or Project pricing groups. This mapping depends on whether the print shop quotes jobs from a price list or from historical estimating data.

Accura invoice totals and payment history map to Dynamics 365 Customer Ledger Entries (CustLedgerEntry). Open receivables migrate as open entries; paid invoices migrate as closed entries. The mapping preserves aging buckets (Current, 30, 60, 90 days) based on the original invoice due dates. Any Accura credit memos or adjustments map to Dynamics 365 Customer Ledger Entries of type Payment or Journal as appropriate.