Migrate from SoftLedger to Infor CloudSuite Corporate

SoftLedger Locations are the top-level entity container and map directly to Infor Cloudsuite Company records. Each SoftLedger Location carries its own currency, address, and COA inheritance; Infor Company records are the header entity for financial reporting and segment scoping. We extract the full Location hierarchy, map parent-child relationships to Infor Company-Division structures where applicable, and preserve the entity-level currency assignment as Infor's primary currency on the Company record. Multi-entity consolidation in Infor happens through the financial reporting layer rather than real-time ledger consolidation as in SoftLedger.

SoftLedger's per-location COA maps to Infor's shared segment-based GL Account structure. Infor uses a flexible account code format with segment delimiters (company, division, department, account, subaccount). We analyze each SoftLedger COA across all Locations, identify the account number format and type hierarchy, and design the Infor segment structure that accommodates all entity COAs under a shared account framework. Inactive accounts are flagged and mapped to Infor account status. Tax code assignments on SoftLedger accounts map to Infor Tax Groups during configuration.

SoftLedger Customer records map to Infor Business Partner with Role = Customer. Standard fields (name, email, address, payment terms, currency) migrate directly. Custom fields on SoftLedger customers are mapped to Infor Business Partner supplementary fields or user-defined fields. SoftLedger's per-customer currency assignment maps to Infor's Business Partner currency setting. Outstanding AR balances are reconciled against the open invoice migration and validated against the accounts receivable subledger.

SoftLedger Vendor records map to Infor Business Partner with Role = Vendor. AP-specific fields including 1099 eligibility, W-9 status, and payment terms migrate. Outstanding AP balances are reconciled against open AP invoices during migration. SoftLedger's per-vendor currency assignment maps to Infor's Business Partner currency setting. Any custom fields on Vendor records are mapped to Infor supplementary fields.

SoftLedger Journal Entries with Lines map to Infor GL Transactions with journal line distributions. Each line carries account reference, amount, currency, and optional dimension tags. We extract multi-currency journal entries with explicit exchange rate overrides stored as metadata on the entry and apply the override rate in Infor rather than the system rate, preserving the original translated amounts. Dimensional tags (department, cost center) from SoftLedger map to Infor dimension code assignments on each GL line. Beginning balance journal entries are treated as a separate migration phase from running transactions.

SoftLedger AR Invoices map to Infor AR Invoice records. Invoice status (open, closed, void) is preserved so that the destination reflects the outstanding receivables position at migration date. Partial payments are migrated as payment records linked to the original invoice. Invoice line items are mapped to Infor AR Invoice detail lines with tax and discount handling. The SoftLedger invoice number becomes the Infor document number reference.

SoftLedger AP Invoices map to Infor AP Invoice records. Open AP invoices carry outstanding balances that must be reconciled against the AP subledger after migration. SoftLedger's payment terms and due date logic map to Infor's AP terms configuration. Discount taken and discount lost amounts from SoftLedger migrate as separate fields on the AP Invoice line in Infor.

SoftLedger Bank Transactions map to Infor Bank Transaction records. Reconciliation status is preserved — unreconciled items are set to open status in Infor so the finance team picks up bank reconciliation work without prematurely closing the account. Bank transaction references to journal entries are resolved through the GL Transaction mapping. Any bank transaction metadata (check numbers, memo fields, match references) migrates to corresponding Infor fields.

SoftLedger provides a dedicated Beginning Balance upload mechanism rather than standard journal entry posting for opening balances. We structure the upload payload per SoftLedger's required format for each entity's account range and deliver it to the customer for upload into Infor's initial balance setup tables. Running journal transactions are migrated as a separate phase after the opening trial balance is confirmed. We flag any accounts with zero balances in SoftLedger that may require explicit zero-entry setup in Infor for reporting continuity.

SoftLedger Dimensions tag journal lines with organizational attributes such as department, cost center, or project. We extract the full dimension schema and all tag assignments and map them to Infor's dimension code structure. Infor's dimension setup allows hierarchical dimension values; we preserve the original dimension names and values and document the Infor dimension configuration for the customer's admin to finalize against their organizational structure.

SoftLedger Custom Fields on Customers, Vendors, Journal Entries, and other standard objects are discovered during scoping, mapped by data type to Infor's equivalent user-defined field types, and transferred field-by-field. Any SoftLedger custom fields with no direct Infor equivalent are documented in the migration handoff with recommended configuration. Data type mismatches (e.g., SoftLedger multi-select to Infor text) are flagged during validation and resolved with the customer before migration.

SoftLedger's warehouse-level item custom fields are a specialized extension of its custom field capability. If the customer uses SoftLedger item custom fields scoped to specific warehouses, we map these to Infor's item supplementary data or user-defined fields with warehouse-level scoping. This requires coordination with the Infor inventory configuration during setup.