Migrate from CREST ERP to Infor CloudSuite Corporate

CREST ERP Customer master records (contact details, addresses, credit limits, payment terms) map directly to Infor CloudSuite Customer and associated Ship-to Address records. CREST ERP's customer-level credit limit maps to the Customer record's Credit Limit field. We preserve any custom properties on the Customer object through a custom field mapping manifest documented during the discovery phase, though these require manual field creation in CloudSuite before data loads.

CREST ERP Vendor master records (supplier details, bank information, performance ratings, purchase terms) map to Infor CloudSuite Supplier records. CREST ERP's vendor catalogue maps to CloudSuite Supplier Item records if the customer maintains a supplier catalog. We validate that CREST ERP payment terms map to valid Infor CloudSuite payment term codes during the import phase.

CREST ERP Item masters (SKU, description, pricing, unit of measure, BOM and routing data) map to Infor CloudSuite Item Master with Item Branch records per warehouse site. CREST ERP BOM structures with multi-level parent-child relationships and work center routing assignments require manual review and remapping to Infor CloudSuite's BOM and Routing forms because the data models differ structurally. Single-level BOMs and routing-less items migrate more directly. CREST ERP unit-of-measure definitions map to CloudSuite UOM codes with explicit conversion rules.

CREST ERP GL accounts (account codes, names, account types, cost center assignments, intercompany settings) map directly to Infor CloudSuite Account records. We preserve account codes, account type classifications, and cost center assignments. Any CREST ERP intercompany account mappings are reviewed during the discovery phase and mapped to Infor CloudSuite's intercompany configuration. GL accounts must load before any transactional records because AP, AR, and Production transactions reference account numbers.

CREST ERP open AP records (vendor linkage, invoice number, amount, due date, current payment status) migrate to Infor CloudSuite AP Invoice records. We track which invoices remain open at migration cutover to avoid re-importing satisfied records. CREST ERP partial payment states map to corresponding Infor CloudSuite payment application records. Vendor lookups are resolved through the Supplier mapping completed in an earlier phase.

CREST ERP open AR records (customer association, invoice number, amount outstanding, aging bucket) migrate to Infor CloudSuite AR Invoice records. We flag credit memos and partial payments for correct offset handling using Infor CloudSuite's payment application logic. CREST ERP aging bucket assignments are preserved as AR Invoice aging status fields. Customer lookups are resolved through the Customer mapping completed in an earlier phase.

CREST ERP Fixed Asset records (acquisition cost, depreciation schedule, asset category, location, maintenance history) map to Infor CloudSuite Asset records. We map depreciation methods and generate Asset Requirement records during migration so that depreciation schedules continue correctly in the destination system. CREST ERP asset categories map to Infor CloudSuite asset type codes. Maintenance history migrates as linked Asset Event records.

CREST ERP Employee records (personal details, job role, compensation history, PTO balances, attendance data) migrate to Infor CloudSuite Employee records with effective-dated compensation preserved. CREST ERP PTO balances map to Infor CloudSuite leave entitlement records, and attendance logs migrate as time entry records. We sequence employee migration before HR records so that employee IDs are available for payroll and leave approvals. CREST ERP custom leave policies and approval workflows require field-level mapping review and manual recustomization at the destination.

CREST ERP Department structure (department codes, names, parent-child relationships) maps to Infor CloudSuite Department and Cost Center records. We validate that cost center assignments on GL accounts align with the department hierarchy in the destination system. Department codes must load before GL accounts and employees because those records reference cost center IDs.

CREST ERP Sales Order records (customer association, line items, quantities, pricing, delivery dates, fulfillment status) migrate to Infor CloudSuite Order Head and Order Detail records. CREST ERP order fulfillment status maps to Infor CloudSuite's order status codes. We resolve customer references through the Customer mapping and line item references through the Item mapping before order detail import. CREST ERP approval workflows on Sales Orders are documented during discovery and delivered as a manual recreation guide for the Infor CloudSuite administrator.

CREST ERP Purchase Order records (vendor linkage, line items, quantities, pricing, expected delivery dates, receipt status) migrate to Infor CloudSuite PO Header and PO Detail. CREST ERP receipt status maps to Infor CloudSuite's receiving status codes. We resolve vendor references through the Supplier mapping and item references through the Item mapping. CREST ERP approval chains on Purchase Orders require documentation review for equivalent Infor CloudSuite workflow configuration during the post-migration setup phase.

CREST ERP Project records (budget, resource assignments, tasks, milestones, time entries) migrate to Infor CloudSuite Project Master and Project Task records. CREST ERP configurable project templates require assessment for remapping to Infor CloudSuite project templates. Resource assignments map to Project Resource records with employee references resolved through the Employee mapping. Time entries migrate as Project Transaction records. CREST ERP milestone and task dependencies may require manual restructuring in Infor CloudSuite's project hierarchy.