Migrate from EQUAL to Infor CloudSuite Corporate

EQUAL Accounts represent both inbound and outbound monetary flows within a single record. We split each EQUAL Account into an Infor Customer master (for inbound/receivable flows) and/or a Vendor master (for outbound/payable flows) based on the transaction history attached to the Account. If an Account has only expense Transactions, it maps to Vendor. If it has only inbound Transactions, it maps to Customer. Accounts with both require both records. The original EQUAL Account ID is preserved in a custom reference field for audit and reconciliation.

EQUAL virtual and physical Card records carry metadata such as card type, spending limits, and linked department codes. We map Cards to Infor ItemMaster records (if treated as a spend instrument) or Infor Asset records (if treated as a physical or virtual payment device requiring tracking). The mapping decision is made during scoping based on whether the customer uses Infor's inventory module for card tracking or maintains card spend visibility through the GL. Card assignment metadata migrates as custom fields on the chosen Infor object.

EQUAL Transactions carry direction (credit/debit), currency, merchant name, and expense category. We split Transactions into Infor AP Invoice records (outbound/payable), AR Invoice records (inbound/receivable), or GL Journal Entry lines depending on the Account type and transaction direction. Each transaction's original timestamp becomes the Infor document date and GL posting date. The merchant metadata and expense category tags are preserved as line-level custom fields or mapped to Infor cost center codes during schema design.

EQUAL tracks multi-currency ledger balances per Account with per-transaction exchange rates. We configure Infor's multi-currency GL settings during schema design, mapping each EQUAL currency code to an Infor currency identifier. Historical exchange rates used in EQUAL Transactions are stored as Infor GL exchange rate records at the per-period level so that the trial balance reconciles at historical rates. Currency Balance aggregates are validated against the Infor GL trial balance after import.

EQUAL expense categories (tags applied at the Transaction level) do not have a 1:1 equivalent in Infor CloudSuite's financial schema. We map each EQUAL expense category to an Infor Cost Center code or a GL Account code during schema design, depending on whether the customer wants cost-center-level or account-level visibility in Infor reporting. Custom fields on the GL Journal Entry line carry the original EQUAL category name as a reference field.

EQUAL Transactions carry merchant name, merchant category code, and location metadata that Infor does not store natively on AP/AR records. We map merchant name to the Infor Vendor reference on AP records where the merchant functions as a Vendor, or store it as a custom text field on the AP Invoice or GL Journal Entry line. Merchant category code is preserved as a custom field for reconciliation against card spend reports.

EQUAL's live ledger entries map directly to Infor GL Journal Entry records. We preserve the original EQUAL transaction ID, date, currency, amount, and description as Infor journal line fields, with the GL account mapped through the expense category configuration. Journal entries are posted in Infor's configured fiscal period sequence, and the trial balance is validated after each batch.

EQUAL supports custom fields on Account, Card, and Transaction records. We pre-create the destination custom fields in Infor CloudSuite during schema design, matching EQUAL field types to Infor field types (text, number, date, picklist). Custom fields with lookup relationships in EQUAL are resolved to the corresponding Infor master record ID before import. Any custom fields without a clear Infor equivalent are flagged for customer decision during scoping.

EQUAL supports document attachments on Transactions. We migrate attachments as Infor ContentDocument records linked via ContentDocumentLink to the corresponding AP Invoice, AR Invoice, or GL Journal Entry. Document filenames and any EQUAL-specific metadata are preserved in the Infor ContentVersion record. We migrate attachments after the parent financial records are created so that the parent record IDs are available for linking.

EQUAL user accounts referenced on Transactions (as approver, creator, or owner) map to Infor OS User records. We match by email address. Users without a matching Infor OS account go to a reconciliation queue for the customer's administrator to provision before production migration begins. User role and permission mapping from EQUAL to Infor OS security roles is out of migration scope and handled by the customer's Infor administrator.