Migrate your SoftLedger data

Locations are SoftLedger's top-level entity objects. Each Location has its own currency, address, logo, and COA inheritance. We migrate the full entity hierarchy intact and preserve the parent-child structure across the migration.

The COA is defined per Location and includes account number, name, type, tax code assignment, and status. We extract the full COA per entity and map it to the destination's account schema, flagging any accounts with active balances.

Customer records include name, email, address, payment terms, currency, and optional custom fields. We migrate all standard fields and map any custom field values to the destination's equivalent.

Vendor records parallel customer records and include AP-specific fields like 1099 eligibility. We preserve all vendor metadata and outstanding AP balances during migration.

Journal Entries carry Lines with account ID, amount, currency, dimension tags, and source references. Multi-currency entries require exchange-rate handling — we pull the effective rate at posting date and flag entries with custom override rates.

SoftLedger issues separate Invoice records for AR and AP. Open invoices are migrated with their status preserved so the destination picks up unpaid balances. Closed invoices may be migrated as historical records or summarized depending on scope.

Bank Transactions link to Journal Entries and carry reconciliation status. Unreconciled items must be migrated with their open status intact to avoid prematurely locking the bank reconciliation in the destination.

SoftLedger supports Custom Fields on standard objects. We discover all active custom fields during scoping, map their data types, and transfer values field-by-field. Any missing destination fields are flagged before migration runs.

Dimensions tag journal lines with organizational attributes (e.g., department, cost center). We preserve the full dimension schema and all tag assignments, ensuring that analytical reporting continuity is maintained post-migration.

SoftLedger stores custom report definitions separately from data. We extract the report JSON configurations and map the referenced account IDs to their destination equivalents, rebuilding the report layout in the target system.

SoftLedger provides a specific Beginning Balance upload mechanism for migrations. We structure the upload payload to match SoftLedger's required format rather than posting raw journal entries, which avoids balance-sheet duplication.

User accounts and role-based permissions are tied to the organization's SSO and identity provider configuration. We do not migrate user credentials or roles; these are reconfigured at the destination by the customer's admin team.