Migrate from mybizz erp to Microsoft Dynamics 365 Business Central

MyBizz ERP Customer records map to Business Central Contact records. If the customer operates in B2B mode with company associations, we create Contacts linked to Customer records using the Business Central Customer Posting Group. For B2C records with no company affiliation, we use the Personal Contact type. All core contact fields (name, email, phone, address) map directly. Custom fields identified during pre-migration audit are mapped to Business Central custom fields or preserved in a migration reference field since MyBizz ERP UI export may not expose all custom field values in standard format.

Vendor records from MyBizz ERP map directly to Business Central Vendor. Payment terms, currency settings, and tax registration numbers carry forward into the Vendor Card. We resolve any vendor naming inconsistencies (alternate names, abbreviated names) during the transformation phase and create a vendor lookup table for reconciliation against any existing Business Central vendor records.

We extract inventory items via MyBizz ERP Dashboard > Menu > Inventory > Items > Export as the primary dataset. Each Item maps with SKU, description, unit of measure, and costing method (Standard, FIFO, Average) to the Business Central Item card. For stockkeeping units, we create Item Variants. Non-stock items are created with the Non-Inventory type. Lot and serial number tracking settings migrate when flagged during scoping. We reconcile item quantities separately from the item master, using the stock report export as the opening inventory quantity in Business Central.

MyBizz ERP Chart of Accounts maps to the Business Central Chart of Accounts with full parent-child hierarchy preservation. Account type (Posting, Heading, Total) and income statement versus balance sheet classification carry forward. We map account numbers and names directly, and set the relevant Posting Group on each account. Account masks and number lengths that differ from Business Central conventions are handled in the transformation layer before import. Posting definitions (which accounts receive which transaction types) are documented separately for Business Central configuration.

MyBizz ERP invoices require a status split at migration time. Unpaid and draft invoices migrate as unposted Sales Invoice documents in Business Central, preserving all line items, amounts, due dates, and customer references. Fully paid invoices migrate as Posted Sales Invoice records, preserving the payment reference and posting date. We map MyBizz ERP payment terms to Business Central Payment Terms Code and flag any invoices with a status that cannot be resolved cleanly for the customer's admin to review before posting.

Quotes map to Business Central Sales Quote, preserving line items, amounts, currency, and expiration dates. The quote status from MyBizz ERP migrates as a custom field since Business Central Quotes do not have a native status field beyond the expiration date. We include the original quote number from MyBizz ERP in the External Document Number field on the Business Central Quote for audit traceability.

Payment transactions linked to invoices map to Business Central Payment Registration entries or cash receipt journal lines. The payment date, amount, payment method, and reference to the corresponding invoice are preserved. For payments with no linked invoice (prepayments or voided transactions), we create general journal lines for audit completeness. MyBizz ERP payment method labels are mapped to Business Central Payment Method Codes during the transformation phase.

MyBizz ERP booking records map to Business Central Jobs if the customer uses project-based billing, or to Service Orders if the customer uses service management. The mapping decision is made during scoping based on the customer's service workflow. We preserve service date, customer reference, booking status, and any item or resource assignments. Custom status values from MyBizz ERP that have no direct Business Central equivalent are flagged for the customer's admin to configure in the destination system.

Expense records map to Business Central Purchase Invoices for vendor-linked expenses and to General Journal Lines for non-vendor expenses. Each record preserves vendor name, amount, expense category, and date. We map MyBizz ERP expense categories to Business Central General Business Posting Groups and Tax Groups during transformation. Attachment references from MyBizz ERP are documented for re-upload via Business Central Document Service after migration.

MyBizz ERP Lead records with contact information and lead status map to Business Central Contacts flagged as prospective customers using the Contact Business Relation table. Lead status values migrate as a custom field on the Contact since Business Central does not have a native Lead object separate from Contact. We map contact name, email, phone, and address fields directly. Any lead scoring or qualification data from MyBizz ERP is preserved in a custom field for use in Business Central sales processes.

MyBizz ERP workflows, approval chains, and automated actions do not migrate as code to Business Central because the workflow engines use different trigger models, action types, and condition syntax. We deliver a written inventory of every active MyBizz ERP workflow and approval chain with its trigger conditions, actions, and assigned users, plus a recommended Business Central Workflow or Power Automate equivalent for each. The customer's admin or a Business Central partner rebuilds them post-migration.

MyBizz ERP reports and dashboards do not migrate to Business Central since Business Central uses Power BI, the Financial Report Designer, and Excel for reporting rather than the MyBizz ERP report format. We deliver a written inventory of all active MyBizz ERP reports, including the report name, object it applies to, and any filters or parameters, so the customer's admin knows exactly what requires rebuilding in Power BI or the Business Central report designer.