Migrate from SAVIO ERP to Epicor Prophet 21

SAVIO ERP Sales Enquiry records with followup dates and reminder settings map to Epicor CRM Lead records. We preserve the reminder cadence as custom date fields (NextFollowupDate__c, ReminderDays__c) during migration. Followup status and assigned salesperson map to Lead Status and OwnerId via User lookup by email. If the customer uses Epicor's Service module, Enquiries map to Cases with a custom EnquiryType picklist.

SAVIO ERP Quotations keyed by size, thickness, finish (plate), and brand map to Epicor Quote. Per-unit and brand-wise pricing rates transform to QuoteLine records with the Epicor PriceList lookup resolved at migration time. Laminate-specific attributes (plate type, finish code) migrate as custom QuoteLine fields or as part of the configured part variant.

SAVIO ERP Sales Order Booking maps to Epicor Sales Order. The OrderNumber becomes CustomerPoNum for traceability. Ship-by dates and production deadlines map to NeedByDate. Lines with production-linked items trigger Job Entry creation via Epicor's demand-to-production linking after migration.

SAVIO ERP Production Requisition linked to Press Planning and Dryer Planning maps to Epicor Job Entry with routing operations. Press Planning sequences become Job Operations with work center assignments (Press stations, Dryer bays). D-lite (daily load) percentages and machine assignments migrate to JobOper records with setup and run hours estimated from the legacy planning data.

SAVIO ERP sheet inventory with size, thickness, finish (plate), and brand attributes maps to Epicor Part Master with a variant matrix for Dimension attributes (Length, Width, Thickness) and a Finish/Plate Code as a configurable attribute. Bar-code references from SAVIO ERP become PartLot lot numbers with lot attributes capturing per-sheet expense costing values. We stage laminate-specific item properties in a transformation table and write them to Part Master custom fields and PartLot attributes during migration.

SAVIO ERP Party records (customer type) with outstanding balances and SMS/Email alert preferences map to Epicor Customer. We preserve contact-level alert settings as custom fields on the CustomerContact record. Outstanding balance at migration date becomes an open AR aging entry that the customer's Epicor admin reconciles post-migration.

SAVIO ERP Party records (vendor type) map to Epicor Supplier. Contact information, payment terms, and bank details migrate to Supplier and SupplierPerson records. Any standing purchase arrangements keyed by laminate size or grade become Contract records in Epicor.

SAVIO ERP GST-compliant sales invoices map to Epicor AR Invoice. E-way bill reference numbers and export documentation flags migrate as custom Invoice fields (EWayBillNum__c, ExportDocRef__c) for audit traceability. Invoice line items resolve to PartNum and UOM from the Part Master mapping.

SAVIO ERP delivery challans map to Epicor Shipment records linked to the corresponding Sales Order. E-way bill compliance flags and interstate movement indicators migrate as custom Shipment fields. Challan line quantities verify against SAVIO ERP stock ledger entries during reconciliation.

SAVIO ERP Accounts module ledger structure maps to Epicor GL Account with account codes preserved. Income and expense accounts map to standard Epicor account types (Revenue, Expense, Cost of Sales). Any laminate-industry-specific account codes (e.g., pressing cost, laminate material variance) become additional GL accounts that the customer's accountant assigns post-migration.

SAVIO ERP auto E-way bill generation settings have no direct Epicor equivalent as a configured feature. We preserve the E-way bill threshold values, vehicle number templates, and GSTIN validation rules as custom fields on Customer and Shipment records and document them in a configuration guide for the customer's Epicor admin to implement via Epicor Tax Engine or a third-party E-way bill API integration.

SAVIO ERP Employee records with department assignments and basic compensation map to Epicor Employee. Standard fields (name, department, hire date, compensation) migrate. Advanced payroll configurations, attendance records, and leave management fall outside migration scope.