Migrate from BizAutomation Cloud ERP to Microsoft Dynamics 365 Business Central

BizAutomation Organizations (the CRM-layer customer/company records) map to Microsoft Dynamics 365 Business Central Customer records. Standard fields including company name, type, billing and shipping address, and payment terms migrate directly. Multi-entity BizAutomation organizations with subsidiary structures map to a parent Customer with related subsidiary Customer records linked via the Relationships feature. Custom Organization fields require a field-level review against Business Central's custom field extension model because BizAutomation's proprietary schema stores user-defined properties as separate columns that must be typed to the correct Business Central data type before import.

BizAutomation Contacts link to Organizations and carry standard name, email, phone, address, and lifecycle stage fields. They map directly to Business Central Contact records, with the Organization relationship preserved via the Contact Business Relation table. Custom Contact properties follow the same reverse-engineering requirement as Organization custom fields: each property must be mapped to a typed Business Central field or extension field before import.

The BizAutomation GL Chart of Accounts, including account number, name, type, and parent hierarchy, maps directly to Business Central G/L Account. We export the full account list and map each BizAutomation account number to the corresponding Business Central account structure with the correct Account Category (Income, Expense, Asset, Liability, Equity) and posting group assignments. The destination G/L Account numbering scheme is designed in coordination with the customer's finance team before import to avoid conflicts with Business Central's reserved number ranges.

BizAutomation Vendor records including company name, contact information, payment terms, and address map to Business Central Vendor records. We export all vendor data before Purchase Orders to maintain referential integrity. Vendor-specific data such as default GL expense accounts and vendor-specific discounts are mapped to Business Central's Vendor posting group and Vendor ledger entry setup. Historical AP aging records migrate as open Vendor Ledger Entries that the finance team reconciles post-migration.

Inventory Items including SKU, description, cost, price, warehouse location, and quantity-on-hand map to Business Central Item records with Item Category and Base Unit of Measure assignments. Custom item properties and matrix (variant) items with dynamic attribute combinations require field-level mapping. Matrix parent items export as Item templates with variant attributes (Size, Color, Material) that we decompose into individual Item Variants in Business Central, generating child SKUs with the correct attribute combinations. We flag any inventory quantity snapshots that may require a separate stock-count entry in Business Central due to date-based snapshot timing differences.

BizAutomation Sales Orders link Customers, Inventory Items, pricing, and shipping rules and map to Business Central Sales Header and Sales Line records. Open orders migrate as Sales Orders in Dynamics 365 with status set to Pending or Released depending on the customer's workflow. Historical closed orders migrate as Sales Invoice records for audit reference, preserving original order number, order date, customer reference, and line item details. Custom order statuses and workflow states in BizAutomation require a value-mapping table because they do not map 1:1 to Business Central's document status model.

BizAutomation Purchase Orders map to Business Central Purchase Header and Purchase Line records with the same open-versus-historical split as Sales Orders. PO records carry financial obligations against matching Vendor accounts, and we preserve the PO status to distinguish between open, received-in-progress, and closed purchase documents. Line items with vendor-specific part numbers and drop-ship flags map to Purchase Line with the appropriate vendor item number and drop-ship information stored on the line.

BizAutomation Shipment records represent fulfillment events tied to Sales Orders and include shipment date, carrier, tracking number, and linked order. These map to Business Central Posted Sales Shipment records linked to the migrated Sales Order. If the destination Business Central instance uses the Warehouse Management module, shipment lines also appear as Warehouse Shipment Lines. We preserve carrier and tracking information as shipment header data and recommend that the customer's admin reviews carrier integration options in Business Central post-migration.

BizAutomation Projects spanning the PSA module, including tasks, time entries, and contract billing, map to Business Central Job records with Job Tasks as the WBS structure. Project status, start and end dates, and assignees migrate cleanly. Custom project fields and milestone billing rules require field-level mapping against Business Central's Job extension model. Time entries attached to Projects migrate as Job Journal Lines with the billable flag and billable quantity preserved. Contract billing rules with rate schedules map to Job Task lines with the appropriate billable price and unit of measure.

BizAutomation Activities represent the engagement history on Organizations and Contacts: calls, emails, tasks, and meetings. We export activity type, date, owner, linked record, and note content. Due to the volume of activity records and the lack of a direct bulk import path in Business Central, we process activities through the Dynamics 365 Dataverse API with chunking and parent-record lookup resolution. Each activity lands as a corresponding record linked to the migrated Contact or Customer. Custom activity types and note attachments require manual field-level review and are documented in the mapping spreadsheet for customer sign-off before import.

BizAutomation Opportunities tracking pipeline deals against Organizations, with stage, amount, probability, close date, and owner, map to Business Central Sales Quotes in the early pipeline stages or Job records for project-based opportunities. Pipeline stages from BizAutomation that have no direct Business Central equivalent are mapped to Sales Quote Status or Job status values defined during schema design. Amount and probability data migrate as extension fields because Business Central's standard Sales Quote does not carry a probability field. Custom pipeline stages in BizAutomation require a status mapping table built during the scoping phase.

Orders originating from Shopify, BigCommerce, WooCommerce, Magento, or EDI marketplaces through BizAutomation's multi-channel integration carry the same structure as standard Sales Orders and map to Business Central Sales Orders in the same manner. We identify e-commerce-origin orders during export by the source channel flag in the database and map the channel identifier to a custom field on the Sales Header for reporting purposes. Post-migration, the customer configures the e-commerce platform's native Dynamics 365 Business Central integration or a middleware connector to route new orders directly into Business Central.