Migrate from ORCA Financial to Infor CloudSuite Corporate

ORCA Financial's flat or hierarchical COA maps to Infor CloudSuite's GL Account structure. We extract account codes, account types (Asset, Liability, Equity, Revenue, Expense), and any custom segments from ORCA. Infor's multi-entity COA may require a company code segment or intercompany account flag; we flag these structural decisions during discovery and configure the Infor company and ledger structure before importing. Active/inactive status from ORCA maps to the Infor Account status flag. Custom ORCA segments (cost-center, department) map to Infor dimension codes if the destination tenant has dimension reporting enabled.

ORCA Financial customer records — name, billing address, payment terms, credit limit, and contact info — map to Infor CloudSuite Business Partner records with bp_type = Customer. The billing address in ORCA maps to Infor's Address Book entry on the Business Partner; shipping addresses map as additional Address Book entries. Payment terms from ORCA (e.g., Net 30) map to Infor's terms-of-payment code. Any custom fields on the ORCA customer record are flagged for manual review as Infor does not support arbitrary custom fields on Business Partner without extending the data model.

ORCA Financial vendor records — name, address, AP terms, and contact info — map to Infor CloudSuite Business Partner records with bp_type = Supplier. Remittance addresses and multi-site vendor records in ORCA are flagged as requiring post-migration review because Infor handles remittance addresses through a separate address-book relationship that must be configured per vendor after import. We preserve ORCA's vendor ID as an external reference field for reconciliation.

ORCA Financial item records — SKU, description, unit cost, unit of measure, and warehouse location — map to Infor CloudSuite Item Master. Stock quantities and reorder points from ORCA migrate as on-hand inventory values; we flag the inventory valuation method used in ORCA (standard, average, FIFO) so it is applied to the corresponding Infor costing method per site. Bin-level location assignments inside warehouses are flagged as a post-migration manual step since Infor's bin structure requires site-level configuration before bin records are created.

Open AP records from ORCA Financial — vendor name, invoice number, amount, due date, and invoice date — migrate to Infor CloudSuite as open AP invoice documents. Each document is created in the AP module against the matching Supplier Business Partner. We migrate open AP as reconciliation-ready records; historical closed invoices do not reopen in Infor. Payment status is set to Open in Infor so AP teams can continue aging management post-migration. ORCA AP terms map to Infor terms-of-payment codes for payment scheduling.

Open AR records from ORCA Financial — customer name, invoice number, amount, due date, and invoice date — migrate to Infor CloudSuite as open AR invoice documents. Unapplied payments and credit memos in ORCA migrate as linked Credit Memo records in Infor. We deliver open AR as a separate reconciliation table for the customer's AR team to verify against Infor post-import. Invoice PDFs stored in ORCA do not migrate as binary attachments; we export a manifest of AR document IDs and filenames for manual re-upload if required.

ORCA Financial warehouse location records — location code, address, and site name — map to Infor CloudSuite Site records. Location codes become Infor Site IDs, and the address maps to the Site's primary address. If ORCA Financial uses sub-location bins within a warehouse, we export bin records and flag them for manual creation in Infor's inventory module because Infor's bin structure requires site-level configuration that must precede bin-level data load.

ORCA Financial user accounts — name, email, and role — map to Infor CloudSuite Operator records. We export a user roster keyed by email address and map ORCA role names to Infor permission groups or operator classes. Since RBAC models differ significantly between ERP systems, we deliver a role-mapping matrix as a written deliverable; the customer's Infor administrator assigns Infor roles during provisioning. Any ORCA Financial user without a corresponding Infor operator account is held in a reconciliation queue.

If ORCA Financial stores open purchase orders, they migrate to Infor CloudSuite Purchase Orders with status Open. PO line items map to Infor POLine records with Item, quantity, and unit cost. Supplier on the PO resolves to the matching Business Partner (Supplier) already migrated. Infor's PO approval workflow does not inherit from ORCA's approval chain; approval routing is a post-migration configuration step.

ORCA Financial stores binary attachments against transactions and master records. We do not migrate binary attachments due to inconsistent storage formats and file-size constraints in manual export scenarios. We export a manifest of document IDs, record associations, and file names for the customer's admin to re-upload manually into Infor Document Management or ION after migration. This manifest is included in the handoff package.