Migrate from Decision Builder to Microsoft Dynamics 365 Business Central

Customer records in Decision Builder map to Account in Dynamics 365 when the customer type is Organization. We preserve contact details, customer-specific pricing tiers, and associated hierarchies. For Decision Builder customers stored as individuals, we create Contact records attached to an Account. The Account is created before any Contact import so that the parent CustomerAccount lookup is satisfied at insert time.

Vendor records map to Vendor entities in Dynamics 365 Finance and Operations or to Account with CustomerType = Vendor in Business Central. We preserve payment terms, tax IDs, and address information. Field-level mapping aligns Decision Builder vendor fields to Dynamics 365 vendor fields since naming conventions and required fields vary between the systems.

Item records encompassing inventory products, services, and non-inventory items map to Released Products in Dynamics 365 Finance and Operations or Item in Business Central. We map item types (Inventory, Service, BOM, Planning), pricing, and bill of materials structures. Multi-level BOMs require special handling with version-controlled Product Bill of Materials entities in Dynamics 365.

Multi-level BOMs in Decision Builder map to BOMTable entities in Dynamics 365 Finance and Operations with version control and production route associations. We flag BOMs with more than two levels during discovery and create a written restructure recommendation for the customer's admin before migration, because BOM depth affects production planning configuration.

Decision Builder Projects bundle related Data Structures, workflows, and configurations. Project-level .dec.obj export preserves the full context that individual object export cannot capture. We map Project hierarchies to Dynamics 365 Project entities, including project types (Time and Material vs Fixed Price), worker assignments, and hour categories.

Custom Data Structures store business-specific data in Decision Builder. Simple, flat Data Structures without interdependent relationships migrate via individual Excel export to Dynamics 365 extension entities. Complex Data Structures with relationships to other Data Structures require Project-level .dec.obj export to preserve interdependencies. We assess each Data Structure during discovery and recommend the correct export method.

Open invoices, credit memos, and payment records migrate to Dynamics 365 Finance and Operations customer and vendor transaction tables. Document numbers, invoice dates, due dates, amounts, and aging information preserve through transfer. Post-migration reconciliation in Dynamics 365 closes the loop on any discrepancies between systems at cutover.

Invoice history, payment records, and adjustment logs transfer with full audit trails. Journal entries require mapping to destination chart of accounts which may use different account numbering schemes and segment structures. We pre-map the ledger dimension structures in Dynamics 365 before migration to ensure historical postings land in the correct accounts.

Account structures including segment definitions, account types, and rollup hierarchies require pre-migration mapping sessions to align source and destination account frameworks. Dynamics 365's segment-based chart of accounts and financial dimensions add complexity that requires careful pre-migration alignment before historical data transfers.

Business logic encoded in Decision Builder Rule Flows migrates as documented specifications, not executable code. We provide a written inventory of each Rule Flow's trigger conditions, input parameters, decision logic, and output actions with recommended Power Automate or Dynamics 365 workflow equivalents for your admin to rebuild post-migration.

Attached documents and files migrate alongside their parent records, stored in Dynamics 365's native document management or linked SharePoint/Blob storage. We verify file integrity after transfer and flag any documents that reference objects not included in the migration scope.

User accounts and role assignments map to Dynamics 365 security roles and teams. Active vs. inactive status preserves through migration. Login credentials do not transfer for security reasons. Role mapping requires pre-migration sessions to align Decision Builder's permission model with Dynamics 365's role-based security structure.

Simple Data Structures without interdependent relationships export individually via Excel and map to Dynamics 365 extension entities or custom tables. We create the destination custom fields in the appropriate table before migration, mapping Decision Builder field types to equivalent Dynamics 365 data types.

Timekeeper records map to Dynamics 365 Human Resources HcmWorker entities when the HR module is included in the destination scope. If HR is not included, timekeeper data is mapped to a custom entity with a note for further discussion on long-term storage.