Migrate from Expandable ERP to Epicor Prophet 21

Expandable's Part Master maps to Epicor Part (Part table). Part Number, description, unit of measure, and revision history transfer directly. Multi-level BOM linkages are preserved by sequencing the Part import before BOM import. Part type (inventory, non-inventory, service) maps to Part.TypeCode in Epicor. User-defined fields from Expandable's custom editor screens migrate to Epicor UD columns configured via UD Column Map before import.

Expandable's versioned BOMs linked to Part revisions map to Epicor BOM and BOM Methods tables. We sequence BOM imports in reverse-indent order (sub-assemblies first, then parent BOMs) to satisfy the bom method revision relationship. Each BOM revision in Expandable becomes a separate BOM revision in Epicor with the ECO effective date preserved. Multi-level assembly traceability for ETO/CTO manufacturers is maintained through the BOM level chain.

Expandable ECO and ECM records tracking revision-controlled part and BOM changes map to Epicor ECR (Engineering Change Request) and ECO (Engineering Change Order) tables. We preserve ECO effective dates, affected BOM levels, and revision chain linkage so that regulated manufacturers maintain the traceability required for FDA 21 CFR Part 820 compliance. ECOs are inserted after their affected BOMs to maintain referential integrity.

Expandable open Sales Orders map to Epicor SalesOrder tables. Order number, customer reference, line items, pricing, and order status transfer directly. We map Expandable's order status codes to Epicor OrderRel.Status. Open orders migrate with allocated inventory linkage preserved. Closed orders are flagged for archive per the migration-archiving decision matrix rather than loaded into the live Epicor environment.

Expandable PO records map to Epicor POHeader and PODetail tables. Vendor assignment, line items, quantities, pricing, and receipt status transfer directly. Partial receipts in Expandable map to Epicor receiving records with the open quantity preserved. Multi-vendor purchase scenarios are handled with vendor-level PO splits resolved at import time.

Expandable's Lot Master with location, lot number, on-hand quantities, and serial number traceability maps to Epicor PartBin. We preserve serial number traceability records for discrete manufacturers requiring full lot genealogy. Multi-site configurations in Expandable map to Epicor Warehouse records. Lot status (available, on hold, quarantined) migrates to Epicor PartBin.LotSelect values.

Expandable GL account balances and journal entries map to Epicor GL Journal and GL Account tables. We extract raw GL subledger data to reconstruct financial statements in Epicor's native reporting suite, compensating for Expandable's lack of a built-in financial statement generator. Current-year and recent prior-year financials migrate; historical records beyond three to seven years (per compliance requirements) are flagged for archive rather than live migration to protect Epicor performance.

Expandable Quality Events linked to parts, lots, and suppliers map to Epicor NonConf records with CAPA tracking linkage. We preserve event severity, root cause classifications, and corrective action status required for FDA 21 CFR Part 820 compliance in med-tech environments. Event-to-part relationships migrate as structured Epicor NonConf records, not flattened text notes, so the compliance chain is queryable and auditable. Epicor quality schema must be pre-configured to accept the migrated event types and status values.

Expandable role-based security with Advanced Security features maps to Epicor User and UserSec records. We export the user-to-role mapping table and rebuild equivalent security profiles in Epicor, accounting for differences between the two platforms' security models. Active users migrate as active Epicor users; inactive Expandable users are flagged for the customer's admin to provision or deactivate based on retention policy.

Expandable customer records map to Epicor Customer. Customer number, name, address, ship-to locations, contact information, and payment terms transfer directly. Customer-specific pricing tiers in Expandable migrate as Epicor price lists linked to the Customer record. Multi-contact customer records in Expandable map to Epicor CustCnt records associated with the parent Customer.

Expandable vendor records map to Epicor Supplier. Vendor number, name, address, payment terms, and ACH/NACHA setup transfer directly. Expandable's NACHA file transfer capabilities for domestic ACH vendor payments map to Epicor's payment setup and bank account configuration. Vendor-specific lead times and purchasing terms migrate as SupplierPP records.

Expandable stores document references and links but does not have a native document management engine. We do not migrate binary attachments directly; we export the link paths and advise the customer to migrate the underlying documents to Epicor's EDMS or a third-party document management system post-migration. Document link paths are preserved in a reference table for the customer's IT team to resolve during the post-migration document consolidation phase.