Migrate from Streamleader to Infor CloudSuite Corporate

Streamleader uses a unified entity model where Customers and Vendors may share a single object or reference. Infor CloudSuite Industrial maintains separate Customer and Vendor objects with distinct schemas, address books, and payment terms. We extract all Streamleader entities with an entity_type indicator, split them into Customer and Vendor records for Infor CloudSuite, and validate that unique identifiers are preserved on both sides. Where Streamleader stores a contact as both a customer-contact and a vendor-contact, we create separate address records on the appropriate Infor entity.

Streamleader Vendor records map directly to Infor CloudSuite VendorMaster. We preserve vendor name, payment terms, tax ID, bank details, and address. Infor CloudSuite requires a vendor code (VendCode) that we generate from the Streamleader account code with a VND prefix if the source does not already carry a vendor code. Vendor-specific metadata such as 1099 eligibility and payment hold flags migrate as configuration fields.

Streamleader Items map to Infor CloudSuite ItemMaster with SKU preserved as ProductCode. Unit of Measure codes, cost, and selling price migrate as standard ItemMaster fields. Streamleader custom item attributes (color, size, brand, etc.) that do not map to Infor's standard ItemMaster columns are stored in the ExtUserText and ExtUserDecimal columns or in a custom ItemXref table we create during schema design. UOM conversions require a UnitOfMeasureMapping table in Infor CloudSuite before Item import proceeds.

Streamleader Chart of Accounts structures migrate to Infor CloudSuite AccountMaster with account code, description, type (Asset, Liability, Equity, Revenue, Expense), and sub-account hierarchy preserved. Infor CloudSuite requires a COA to be initialized before AP/AR records can reference account codes, so this migration runs first. Streamleader custom segment dimensions (Cost Centre, Department) map to Infor CloudSuite sub-account structures. We validate account code uniqueness and flag any orphaned references before loading.

Open Accounts Payable records from Streamleader map to Infor CloudSuite APTran (transaction lines) and apvitem (header). We preserve vendor reference, invoice number, invoice date, due date, gross amount, discount taken, and tax amount. Partial payment history (payments already applied) migrates as Payment records linked to the APTran, with outstanding balance recalculated against the migrated payment history. Unpaid vouchers that reference a Chart of Account code not yet migrated are held in a reconciliation queue until AccountMaster loads complete.

Open Accounts Receivable records from Streamleader map to Infor CloudSuite ARTran (transaction lines) and arsdist (header). We preserve customer reference, invoice number, invoice date, due date, gross amount, credit memos, and outstanding balance. Credit allocations and partially applied payments migrate with the invoice record. Infor CloudSuite requires a customer record to exist before AR invoices can be posted, so Customer migration must complete before AR import begins.

Streamleader historical transaction history migrates to Infor CloudSuite GlTrans and gltransdtl tables in date-chunked batches of 90-day windows. Each transaction includes the journal entry number, posting date, account code, debit/credit amount, and source reference. We validate that every account code referenced in historical transactions exists in the migrated Chart of Accounts. Transaction archives beyond 24 months may be flagged as optional scope based on the customer's reporting and audit requirements, as Infor CloudSuite implementations sometimes archive older history post-migration.

Streamleader User accounts map to Infor CloudSuite OS User records or Employee records depending on whether the destination uses Infor Security Manager or the Infor HCM module for identity management. We export user name, email, role, and status. Streamleader role names are mapped to Infor CloudSuite role equivalents during configuration. Users without an email match in the destination are held in a reconciliation queue for the customer's Infor administrator to provision before production migration proceeds.

Streamleader contact records map to Infor CloudSuite AddressBook entries linked to the corresponding Customer or Vendor entity. Each contact includes name, email, phone, role, and primary address. Infor CloudSuite supports multiple address book entries per entity, which mirrors Streamleader's contact hierarchy. We preserve the primary contact flag and contact type.

Streamleader does not publish whether binary document attachments (invoices, receipts, contracts) are accessible via API. During the technical audit phase, we attempt to export document blobs via Streamleader's undocumented API. If accessible, we stage them for Infor Document Management (IDM) or store them as file references in the Infor CloudSuite FileStorage path. If inaccessible, we document the document locations for manual file transfer and note the gap in the migration scope. IDM configuration is not included in standard migration scope.