Migrate from Freespace ERP to Infor CloudSuite Corporate

Freespace ERP organizes accounts around industry-specific modules rather than a generic chart-of-accounts model, with cost-center assignments embedded at the account level. Infor CloudSuite uses a dimensional GL structure where accounts, cost centers, departments, and optionally projects are separate dimension tags. We extract the full Freespace ERP account code list, map each to a destination GL account, and resolve any cost-center assignments into Infor CloudSuite's dimension tagging system. We flag accounts that reference cost centers not yet defined in the destination and escalate to the customer's Infor consultant for dimension setup before account migration begins.

Freespace ERP customer and vendor records export with name, contact details, billing address, shipping address, and payment-term codes. Infor Cloudsuite consolidates customers and suppliers into a Business Partner record with party-level fields, address roles, and payment terms at the partner level. We map Freespace ERP payment-term picklist values to Infor Cloudsuite payment-term codes, strip non-alpha ASCII characters from name fields to prevent schema violations, and preserve the billing/shipping address distinction as separate address roles on the Business Partner.

Freespace ERP item masters include SKU, description, unit of measure, cost, and BOM associations for manufactured items. Infor Cloudsuite Item Master holds the same core attributes plus warehouse-specific bin, lot, and serial controls. We map unit-of-measure codes 1:1 and flag items with zero or negative cost values for manual review. Multi-level BOM items require a scoping decision: preserve structure as sub-assembly links (for CloudSuite editions that support nested BOMs via Work Center and Routing) or flatten to a single-level explosion (for editions that do not support hierarchy). The customer chooses the BOM strategy during discovery.

Freespace ERP supports multi-level Bills of Materials where subassemblies reference their own child BOMs. CloudSuite Industrial (SyteLine) preserves BOM hierarchy via a parent-component structure; other CloudSuite editions flatten at import. We enumerate all active BOM versions during discovery, identify max nesting depth, and present two handling paths: preserve as Infor CloudSuite BOM with subassembly links (recommended if destination supports) or flatten to a single-level BOM explosion with all components listed at the top level. Component quantity-per, scrap-percentage, and phantom-assembly flags map to the destination BOM header and line attributes.

Open invoices, credit memos, and payment records export from Freespace ERP with document date, due date, open amount, and payment terms. We chunk open AP and AR documents by document date into batches of 500 records, map payment-term picklist codes to Infor Cloudsuite payment terms, and preserve the original invoice number as a reference field. We flag invoices with partial payments to ensure only the open residual amount posts in CloudSuite. All open documents must be posted in Freespace ERP before migration to ensure the destination receives accurate outstanding balances.

Transaction history in Freespace ERP includes production orders, material issues, inventory movements, and cost postings. These are high-volume exports requiring chunking by date range (typically 12-month windows) and sequencing by posting date. We validate that each transaction references a valid GL account and cost center that has already been migrated to the destination. Transactions referencing unmapped accounts are held in a reconciliation queue until the chart-of-accounts mapping is finalized.

Journal entry headers and line items export from Freespace ERP with account codes, debit and credit amounts, posting dates, and dimension tags. Infor Cloudsuite posts journal entries with mandatory header-level posting date and batch reference, and line items require account code, amount, and optional dimension values. We preserve the line-item sequence order from Freespace ERP within the destination batch, validate debit/credit balance totals before posting, and flag any journal entries with unposted status in the source (which should be posted before migration to avoid stranded draft records in the destination).

Freespace ERP employee profiles include name, department, job title, hire date, employment status, and optional custom properties added during onboarding. We enumerate all active custom employee properties during discovery against the platform's field management UI, include them explicitly in the export field list, and map them to Infor Cloudsuite HCM employee extended fields. Any Freespace ERP custom properties not included in the standard export templates are flagged and added to the migration field list before export begins. We map employment status flags (active, inactive, terminated) to Infor CloudSuite HCM status codes.

Freespace ERP payroll history records carry effective-dated compensation rows with pay frequency, salary or wage rates, deduction codes, and retro-adjustment entries. Retroactive adjustments can create rows where the effective date predates the record creation date, producing non-sequential ordering. We sort compensation rows by effective date before importing into Infor Cloudsuite, ensuring downstream payroll systems receive chronologically consistent compensation timelines. Pay-frequency flags map to Infor CloudSuite payroll frequency picklist values. We preserve deduction codes as payroll code references and flag any deduction types not recognized by the destination payroll configuration for manual setup.

Multi-stage production orders export from Freespace ERP with stage names (user-defined), quantities, material consumption links, and routing information. Infor Cloudsuite Manufacturing Management uses a production order structure with defined operations, work centers, and status codes that differ from Freespace ERP's stage model. We map each Freespace ERP production stage to an Infor CloudSuite operation sequence and flag any stage names that have no clear equivalent in the destination's status code set for manual assignment. We preserve material consumption links and bom-associations already resolved in the item migration. Open production orders migrate with their current stage status; completed production orders migrate with full history for audit continuity.

Freespace ERP allows administrators to add custom properties to standard objects (items, employees, vendors, production orders) during onboarding. These extended fields may not appear in the platform's default export templates. We enumerate all active custom field definitions during discovery against the platform's field management UI, verify each appears in the export field list, and map them to Infor Cloudsuite extended field definitions (via Infor OS or the target CloudSuite edition's customization layer). Custom field type mapping: text to text, number to number, date to date, picklist to picklist (with value-set alignment). We flag any custom fields that reference lists exceeding Infor Cloudsuite picklist limits for manual resolution.