Migrate from Streamleader to Epicor Prophet 21

Streamleader Customer records map to Epicor Customer (CustCnt/ShipTo hierarchy). The Streamleader account code becomes Epicor's CustNum with a corresponding Customer record header. We preserve billing address, shipping addresses, payment terms, and credit limits. Where Streamleader uses a separate Accounts object, we join records at export time and flatten the relationship. If Streamleader supports parent-child customer hierarchies, we map those to Epicor's Customer-Parent relationship and create the top-level record first so that ShipTo records resolve their parent reference on insert.

Streamleader Vendor records map to Epicor Vendor (VendCnt). Vendor name, contact details, payment terms, and tax IDs transfer directly. We create the Vendor record before any PO or receipt history to satisfy the parent reference. Vendor-specific metadata (e.g., Streamleader custom fields on Vendor) migrates to Epicor UD columns on Vendor if the customer's Epicor instance has UD Vendor columns configured.

Streamleader Item records map to Epicor Part. We transfer PartNum (SKU), PartDescription, Unit of Measure, standard cost, and standard price. Pricing tiers from Streamleader custom fields (if any) are stored in Epicor UD columns on Part. UOM conversions that Streamleader stores as custom attributes are built as PartUOM conversion records in Epicor. Stocked vs. non-stocked flags from Streamleader map to the Part's TypeCode (Stock, Service, Compressor, Rental, etc.).

Streamleader Chart of Accounts maps to Epicor GL Account (GLAccount). We preserve account codes, account descriptions, account types, and the full account hierarchy. Streamleader's top-level segments map to Epicor's Natural Account and Optional segments depending on the customer's chart structure. We note that Epicor requires reconfiguration of fiscal year calendars if Streamleader uses a non-calendar fiscal year; this is flagged during discovery and documented as a post-migration admin task.

Streamleader open AP (vendor bills) maps to Epicor AP Invoice with open invoice status flags preserved. We export invoice number, vendor reference, invoice date, due date, total amount, and outstanding balance. Partial payments from Streamleader are carried as payment records in Epicor. Epicor's AP Invoice must have a corresponding Vendor record already present; we load Vendors first. AP invoice line items map to Epicor AP Invoice lines with GL account and cost centre references.

Streamleader open AR (customer invoices) maps to Epicor AR Invoice with open invoice status flags. We transfer invoice number, customer reference, invoice date, due date, total amount, and outstanding balance. Credit memos and overpayments from Streamleader carry as AR Credit Memos and AR Payment records respectively. Customer must already exist in Epicor; we load Customers before AR records. The AR Invoice Group and fiscal period are set from the Streamleader invoice date.

Historical transaction migration is scoped during discovery based on reporting requirements. We chunk exports by date range (typically 12 or 24 months) and validate line-item counts. Epicor GL records are created as Posted Transactions with the original journal entry date and source module. Customers and Vendors referenced in historical transactions must already exist in Epicor. Historical AR/AP records are loaded as completed transactions in Epicor's history tables. Full audit trail transfer is recommended but may require Epicor BAQ (Business Activity Query) configuration post-migration.

Streamleader User accounts map to Epicor User records. We export user name, email, and role assignments. Epicor User security is configured via its security groups (Security Manager); we map Streamleader role names to Epicor Security Groups during discovery and document the recommended group assignments. Permissions do not map directly because Epicor's ACL model is tied to its menu structure and specific companies/sites. We export role names for manual mapping by the customer's Epicor admin post-migration.

Streamleader custom fields on any object migrate to Epicor UD columns on the corresponding table (UD100, UD101, etc.) or via ZDataTable UD extensions. Epicor UD field setup requires adding columns via IceBO.ZDataTable and writing BPM logic to populate them at runtime if they reference calculated values. We flag every Streamleader custom field during technical audit, document the target Epicor UD column and BPM logic required, and escalate the UD development to the customer's Epicor admin team as a configuration task outside standard migration scope.

Streamleader does not publish BOM capabilities in its documented feature set. If the source data includes BOMs (bill of materials or recipe structures), we map them to Epicor PartMtl (Bill of Materials / Job Manager). If no BOM data exists in Streamleader, we document the absence and recommend a BOM capture exercise before or during Epicor configuration as part of the manufacturing implementation phase.

Streamleader open Sales Orders map to Epicor OrderHed and OrderDtl. Header-level fields (customer, order date, terms, ship date) migrate as OrderHed records. Line items migrate as OrderDtl with PartNum, quantity, unit price, and warehouse resolved. We resolve Customer references to Epicor CustNum before loading, and validate that all PartNums referenced in OrderDtl exist in Epicor's Part table. Open order status flags from Streamleader map to Epicor OrderRel ReservedQty and PickPackShip status.

Streamleader's API does not confirm programmatic access to binary document attachments (invoices, receipts, contracts). Epicor stores documents in ICE tables (Ice.Data.Doc) with DocumentReference linking to the parent record. We do not migrate document blobs as code or API call. We document the document storage locations in Streamleader, recommend a manual file extraction and re-upload to Epicor's Document Management, and flag this as a manual step in the migration checklist. If Epicor is deployed with a configured document repository (SharePoint, Network Drive, or IceBO DocStorage), we include the re-upload path in the handoff documentation.