Migrate from etEngine to Infor CloudSuite Corporate

Account codes, names, types, and currency assignments map directly to Infor Cloudsuite account master records. We validate account code structure against the destination's chart of accounts configuration before import. If etEngine uses department or cost-center coding embedded in the account number, we split these into separate Infor Cloudsuite dimension fields during transformation. This object is migrated first because all subsequent master and transaction records reference account codes.

Customer records including contact details, billing addresses, and payment terms map to the Infor Cloudsuite customer master. We resolve the default AR account reference from the Chart of Accounts mapping before inserting customer records. Any custom fields on the etEngine customer record are mapped to Infor user-defined fields (UDFs) on the customer master form. Credit limits and payment terms migrate as-is.

Vendor master records map to the Infor Cloudsuite supplier master with contact and payment information preserved. Default AP account references resolve against the Chart of Accounts mapping. We flag any vendors marked as inactive in etEngine and either exclude them or import them as inactive records per the customer's instructions.

Item masters including SKUs, descriptions, standard cost, and standard price map to Infor Cloudsuite item master. We preserve unit of measure conversions, item type classification (stock, non-stock, service), and any custom attributes as UDFs. Item warehouse assignments (if etEngine stores warehouse-level stock data) migrate to the item warehouse cross-reference table (wh item master) after the item master is committed.

Outstanding invoices and credit memos migrate with original invoice dates, amounts, and due dates. We flag any etEngine records with a reconciled or voided status that should not carry forward. Open AP records reference the vendor and AP account from the vendor and chart mappings; open AR records reference the customer and AR account. We sequence AP and AR migration after all vendors, customers, and account mappings are validated.

Past journal entries migrate in chronological order by fiscal period. Each journal entry is chunked into batches of 500-1,000 lines per period to manage database load. We preserve the original posting date, journal batch number, and source document reference. If etEngine stores transaction detail in multiple tables (header and distribution lines), we join and flatten them before writing to Infor Cloudsuite's single journal table format.

User accounts map to Infor Cloudsuite operator records with role and permission assignments. We flag any users who are inactive in etEngine for import as inactive operators with an expiration date set to the migration date. Role and permission mappings are based on etEngine role definitions discovered during scoping; any permissions without a direct Infor Cloudsuite equivalent are documented for the customer's admin to configure post-migration.

Attached files and linked documents export from etEngine to a structured file store (network share or cloud storage bucket), then re-link to their corresponding Infor Cloudsuite records via IDM. We preserve original file names, modification timestamps, and MIME types. Documents without a resolvable parent record (orphan attachments) are placed in a dedicated folder for manual review. IDM configuration (metadata schema, security, and storage location) is set up by the customer's Infor consultant before document migration begins.

etEngine custom fields on any master or transaction record map to Infor Cloudsuite user-defined fields. We create the UDF schema in Infor Cloudsuite before any data migration phase, using the same field label and a matching data type. Multi-select or multi-value custom fields in etEngine map to Infor Cloudsuite multi-select UDFs. Any custom fields that cannot map to a native Infor Cloudsuite UDF type are documented for the customer and migrated as text fields with the original value preserved.

etEngine fiscal period definitions (monthly, quarterly, or custom) map to Infor Cloudsuite fiscal year calendar. We validate that etEngine period dates align with the Infor Cloudsuite fiscal calendar configuration before any transaction migration begins. If the source and destination fiscal year start dates differ, we flag the discrepancy and apply a fiscal period mapping table during journal entry import to ensure historical transactions land in the correct Infor Cloudsuite period.