Migrate from eBIZ SMARTZ Business ERP to Microsoft Dynamics 365 Business Central

eBIZ SMARTZ Customer records map to Dynamics 365 Customer entities. In Dynamics 365 Finance and Operations, the Customer table is a single party-type dimension used across Sales Orders, Free Text Invoices, and Project contracts; in Business Central, Customers are separate records linked to Contacts. We preserve the 360-degree view by mapping the source customer balance, credit limit, and payment terms to the corresponding Dynamics 365 fields, and we carry forward the full order and invoice history as related records. The customer account number from eBIZ SMARTZ becomes the Dynamics 365 Customer Account Number, used as the dedupe key during import.

eBIZ SMARTZ Orders map to Microsoft Dynamics 365 Sales Order (or Purchase Order depending on order direction). The transactional linkages to the customer account and any linked invoice references migrate as Order lines referencing the Customer Account and the original order number preserved as an external reference field. Order totals, taxes, discounts, and shipping charges map to the corresponding Dynamics 365 line and header fields. If eBIZ SMARTZ tracks order delivery status, that maps to a Sales Order status or warehouse shipment reference in Dynamics 365.

eBIZ SMARTZ Invoice records map to Microsoft Dynamics 365 Sales Invoice or Free Text Invoice depending on whether the source invoice is a sales document or a general ledger billing document. The invoice-to-order linkage migrates as a line-level order reference, and the invoice-to-customer linkage resolves to the Customer Account. Payment reconciliation status from eBIZ SMARTZ maps to the Dynamics 365 Invoice Status field. If historical invoices have partial payments, those split payments migrate as separate Customer Payment records linked to the original invoice.

eBIZ SMARTZ Payment records map to Dynamics 365 Customer Payment Journal entries or directly to Customer Transactions depending on the destination's posting profile configuration. We preserve the payment-to-invoice linkage using the SettleTrans functionality so that the Dynamics 365 payment journal lines are applied against the corresponding open invoices. Payment method, payment reference, bank account, and amount migrate as journal line fields. Consolidated cash application across divisions maintained in eBIZ SMARTZ maps to separate Customer Payment entries per legal entity in Dynamics 365.

Chart of accounts entries from eBIZ SMARTZ map to G/L Account records in Dynamics 365 Finance and Operations or Business Central. Account type (Asset, Liability, Equity, Revenue, Expense), account group, and posting definition require field-level mapping to the Dynamics 365 G/L Account structure. Number series for Customers, Orders, Invoices, and Payments migrate as Dynamics 365 Number Series with gap-filled ranges applied after migration. Custom fields added to the chart of accounts during eBIZ SMARTZ implementation require pre-creation as Dynamics 365 custom fields before master data import begins.

Historical journal entries and subledger transactions from eBIZ SMARTZ map to General Ledger Journal Lines in Dynamics 365. We preserve the original journal entry numbering sequence and posting dates to maintain the audit trail continuity. Each journal entry header maps to a Journal Batch, and individual line items carry the account number, dimension values, debit, credit, and description from the source. If eBIZ SMARTZ maintains voucher numbers or document references, these migrate as Voucher or Document Number fields in Dynamics 365. The migration window requires careful sequencing to prevent gap-induced reconciliation failures in the receiving ledger.

eBIZ SMARTZ operating locations (corporate headquarters, divisions, and operating locations) require a split mapping in Dynamics 365. Headquarters and division structures map to Operating Units or Legal Entities depending on the destination's organizational model and fiscal reporting requirements. Individual operating locations map to Sites and Warehouses within each legal entity. We identify the location-to-entity mapping during scoping by analyzing eBIZ SMARTZ's organizational hierarchy and the customer's consolidated financial reporting requirements. Parent-account linkages in eBIZ SMARTZ become dimension hierarchies or intercompany relationships in Dynamics 365.

eBIZ SMARTZ Employee records map to Dynamics 365 Human Resources Worker records if the destination includes the HR module, or to the Worker table in Finance and Operations for HR-and-Payroll deployments. Employee fields including employment start date, department, job title, manager relationship, and historical compensation records require type-mapped fields in the destination. Benefits enrollment data migrates if the destination HR system is configured for benefits administration; otherwise, we migrate the employee record as a Worker without benefits history. Organizational chart data from eBIZ SMARTZ maps to the Dynamics 365 Position hierarchy.

Custom fields added during eBIZ SMARTZ implementation require pre-creation in the Dynamics 365 destination schema before any data import begins. We inventory every custom field across the eBIZ SMARTZ schema during discovery, classify each as a direct field mapping, a transformed field, or a value to be archived, and then create the corresponding custom field in Dynamics 365 with the appropriate field type. Fields with picklist or option set values from eBIZ SMARTZ require corresponding Option Set definitions in Dynamics 365. This step must complete before any record migration starts.

If eBIZ SMARTZ includes custom-developed modules or extended table structures beyond the standard modules, these map to Dynamics 365 custom tables (Extension tables in Finance and Operations, custom tables in Business Central). We pre-create the destination table schema including all fields, data types, and lookup relationships, then migrate the records using the appropriate Dynamics 365 data entity or API. Custom tables with foreign key references to standard entities require parent-record migration sequencing so that the lookup resolution succeeds at insert time.

eBIZ SMARTZ item and product records map to Dynamics 365 Released Products (Finance and Operations) or Item records (Business Central). Item number, product name, item type (stock item, service, kit), unit of measure, and costing method migrate as product master fields. If eBIZ SMARTZ tracks BOM (Bill of Materials) or routing structures, these map to BOM and Route entities in Dynamics 365 Manufacturing if the destination includes production control. Item pricing and discount structures migrate as Trade Agreements in Dynamics 365.

If eBIZ SMARTZ maintains vendor records for procurement or accounts payable, these map to Dynamics 365 Vendor entities. Vendor name, address, payment terms, W-9 or tax registration, and default posting profiles migrate as vendor master fields. Open purchase orders linked to vendors migrate as Purchase Orders in Dynamics 365 with vendor lookup references resolved at migration time. Vendor-ledger history including historical invoices and payments migrates to Vendor Transactions using the same SettleTrans approach used for customer payments.