Migrate from Maximum Software to Microsoft Dynamics 365 Business Central

Maximum Software Customer records map to the CustCustomerV3Entity in Dynamics 365 Finance and Supply Chain Management or the Customer table in Business Central. We map Customer Account Number to CustAccount, Customer Name to Name, and payment terms to the DefaultDimension (financial dimension combination). Credit limits, customer groups, and payment days transfer as custGroup, creditMax, and paymDayId respectively. Multi-currency customers require currency code mapping to the Exchange Rate Type in Dynamics 365.

Maximum Software Vendor records map to VendVendorV2Entity in Dynamics 365 Finance and Supply Chain Management or the Vendor table in Business Central. We map Vendor Account Number to VendAccount, Vendor Name to Name, and payment terms to paymTermId. 1099 reporting flags map to Tax1099 fields, and W-9 status fields carry forward. Vendor groups map to VendGroup for posting profile assignment in the destination.

The Maximum Software Chart of Accounts maps to MainAccount in Dynamics 365 Finance and Supply Chain Management. We preserve account numbers, account names, and account type (Asset, Liability, Expense, Revenue) as accountType. Financial Dimensions that exist in Maximum Software map to DimensionAttribute entities in Dynamics 365. Effective dates on accounts transfer to validFrom/validTo on the data entity. Organizations with segment-structured account codes should be aware that Dynamics 365 does not enforce segment formatting; this is configured at the reporting level via Account Structures.

Maximum Software Items map to EcoResReleasedProductV2Entity in Dynamics 365 Finance and Supply Chain Management or Item in Business Central. We map item number to ItemId, item name to NameAlias, and item type (Stock, Service, BOM) to ItemType. Unit of measure transfers to UnitOfMeasureSymbol. For items with costing methods (FIFO, Standard, Moving Average), we map to CostingVersion and InventModelGroup. Multi-site items require site assignment via InventSiteId and InventLocationId during migration. Maximum Software item categories map to Product Category hierarchies in Dynamics 365.

Open invoices from Maximum Software migrate to CustInvoiceJournal lines in Dynamics 365 Finance and Supply Chain Management or open Customer Ledger Entries in Business Central. We map invoice number to InvoiceId, invoice date to InvoiceDate, due date to DueDate, and outstanding amount to RemainAmount. The customer and vendor account lookups are resolved before import. Open invoices that are partially paid require RemainAmount and PaymentSchedules set correctly to reflect the outstanding balance in Dynamics 365's aging structure.

Open vendor invoices from Maximum Software migrate to VendInvoiceJournal in Dynamics 365 Finance and Supply Chain Management. We map invoice number to InvoiceId, vendor account to VendAccount, invoice date to InvoiceDate, and invoice amount to InvoiceAmount. Tax codes require explicit mapping to TaxGroup and TaxItemGroup in Dynamics 365 because the tax engine does not infer from the vendor record. Line items map to InvoiceLine entities with account distributions mapped to the correct MainAccount and financial dimension combination.

Maximum Software Users map to UserInfo in Dynamics 365 Finance and Supply Chain Management. We match by email address as the primary key. Roles and security groups from Maximum Software map to SecurityRole assignments in Dynamics 365, with the customer providing the role mapping table during discovery. Users without a matching Azure Active Directory entry are held in a reconciliation queue for admin provisioning before record migration begins.

Maximum Software records with effective dates (posting profiles, account assignments, cost centers) require explicit effectiveFrom/validFrom and effectiveTo/validTo values on DimensionCombination entities. Dynamics 365 enforces effective-date scoping at the data entity level. We extract all effective-dated assignments from Maximum Software and create separate dimension combination records per period rather than collapsing them to a single current value, preserving historical accuracy. This is flagged for customer review before migration because it can significantly increase record counts.

Fixed asset master records from Maximum Software migrate to AssetTable in Dynamics 365 Finance and Supply Chain Management. Asset number maps to AssetId, asset name to Name, acquisition date to AcquisitionDate, and acquisition cost to AcquisitionCost. Depreciation books (book rules, useful life, depreciation method) map to AssetBook with DepreciationMethod, ServiceLifeMonths, and DepreciationConvention. Assets under depreciation require a depreciation schedule migration that is validated against the General Ledger during reconciliation.

Open purchase orders migrate to PurchTable and PurchLine in Dynamics 365 Finance and Supply Chain Management. We map PO number to PurchId, vendor account to VendAccount, and purchase line items to PurchLine with item number, quantity, and unit cost. Purchase order status (Open, Received in Full, Invoiced) must map to PurchStatus. Lines that are partially received require receipt quantity and pending invoice quantity correctly set to avoid duplicate receipt prompts in Dynamics 365.

Open sales orders migrate to SalesTable and SalesLine in Dynamics 365 Finance and Supply Chain Management. We map order number to SalesId, customer account to CustAccount, and order lines to SalesLine with item number, quantity, unit price, and line discount. Delivery address and terms map to DeliveryTerms and InventSiteId for warehouse assignment. Order hold statuses require explicit mapping to SalesStatus to prevent accidentally released orders that should remain pending.

Maximum Software warehouse or location records migrate to InventSite (site), InventLocation (warehouse), and WMSLocation (bin) in Dynamics 365 Finance and Supply Chain Management. Site and warehouse codes map to InventSiteId and InventLocationId respectively. If Maximum Software uses a single-site model, we create a default site and warehouse in Dynamics 365 and assign all items to it during migration. Multi-site configurations require a site mapping table provided by the customer during discovery, and items are reassigned to the correct site-warehouse combination at migration time.