Migrate from Decision Builder to Infor CloudSuite Corporate

Decision Builder Customer records map to Infor CloudSuite Business Partner records with role Customer. We preserve contact details, customer-specific pricing tiers, and address information. The customer number in Decision Builder becomes the Business Partner ID in Infor, and we validate against Infor's address validation rules during import. If Decision Builder stores customer hierarchies, we map them to Infor's Parent Customer relationship.

Decision Builder Vendor records map to Infor CloudSuite Business Partner records with role Supplier. Payment terms, tax IDs, and address fields transfer directly. We flag any Vendor records that reference Data Structures not included in the migration scope, as those lookups will resolve as null in Infor unless the customer defines default values.

Decision Builder Items (inventory products, services, non-inventory items) map to Infor CloudSuite Item records. We map item types, pricing, unit of measure, and cost fields. Multi-level Bill of Materials (BOM) structures require special handling: we export each BOM level, create parent Item records first, then attach BOM components in sub-level sequences that Infor's Item form dependencies require.

Open AP/AR invoices, credit memos, and payment records export cleanly from Decision Builder and map to Infor CloudSuite's Accounts Payable and Accounts Receivable modules. We preserve document numbers, dates, amounts, aging information, and the open/closed status. Post-export reconciliation closes the loop in the destination system. Unpaid invoices require the vendor or customer Business Partner record to exist before the invoice can be linked.

Invoice history, payment records, and adjustment logs migrate with full audit trails as Infor CloudSuite General Ledger journal entries. The chart of accounts mapping must be complete before transaction import because Decision Builder account numbers may use different schemes than Infor's GL account structure. We run a pre-mapping session to align account frameworks and create any missing Infor account codes.

Account structures including segment definitions, account types, and rollup hierarchies require pre-migration mapping sessions to align Decision Builder and Infor account frameworks. We export the full account structure from Decision Builder, map to Infor's GL account segment rules, and flag any accounts that exist in Decision Builder but have no Infor equivalent. Infor requires account codes to exist before any transaction referencing them can post.

Decision Builder Projects bundle related Data Structures, workflows, and configurations. Project-level export via .dec.obj preserves the full context that individual object export cannot capture. We convert .dec.obj exports to intermediate formats, validate all contained Data Structures and their relationships, and import into Infor Projects with their associated configurations intact. This is the recommended export method for anything with interdependent relationships.

Decision Builder custom Data Structures map to Infor CloudSuite custom objects. Complex Data Structures with interdependent relationships require Project-level export to preserve field-level data and cross-record references. Simple, flat Data Structures export via Excel and map directly to Infor fields. We assess each Data Structure during discovery and classify it by complexity before choosing the export strategy.

Attached documents and files migrate alongside their parent records (Customer, Vendor, Item, Project). We verify file integrity after transfer and flag any documents that reference parent objects not included in the migration scope. Infor CloudSuite stores migrated files in its Document Management module linked to the corresponding business object.

Decision Builder User accounts and role assignments require mapping to Infor CloudSuite's permission model. We export user profiles, role assignments, and site/access configurations. Active versus inactive status transfers. Login credentials do not transfer for security reasons; the customer's Infor administrator provisions new credentials post-migration. We map Decision Builder role names to Infor role equivalents during the mapping phase.

Decision Builder rule flows and custom workflow logic stored in the platform do not migrate as executable code. We extract and document each active rule flow and workflow with its trigger conditions, logic branches, and associated Data Structures. This documentation is delivered to the customer's Infor administrator as a rebuild specification for Mongoose scripting, C# assemblies, or Infor OS workflows.