Migrate from Spectrum ERP to Epicor Prophet 21

Spectrum Jobs map to Epicor Project records with the phase and cost-code hierarchy preserved as Epicor Phase and Task records. The Spectrum Job number becomes the Epicor Project Number; Job phase descriptions map to Phase descriptions. Cost codes from Spectrum become either Task-level cost categories or UD fields on Phase depending on the destination configuration. Historical job cost summaries migrate as Phase Actuals against the project. We validate the project start and end dates from Spectrum's Job Master and flag any overlapping or duplicate job numbers for reconciliation before import.

Spectrum Work Orders attached to Jobs map to Epicor MES Work Orders. The Job-to-Work Order linkage in Spectrum becomes the parent Job reference in Epicor. Labor, materials, and equipment allocations from the Spectrum work order migrate to Epicor JobMtl, JobOper, and JobEquip records. Any notes or attachments on the Spectrum work order transfer as JobHead checkboxes or Document Reference records in Epicor. We validate the work order-to-job relationship integrity before inserting child records.

Spectrum G/L Accounts migrate to Epicor GL Account with segment mapping resolved during the pre-migration mapping session. Spectrum's account structure (segment count, segment meanings, rollup hierarchies) maps to Epicor's account segments and account groups. The Add G/L Journal Entries web service in Spectrum surfaces both debit and credit lines per entry; we use these to reconstruct the full journal entry in Epicor's G/L Journal Entry form. Account numbers and descriptions migrate directly; the account type and posting definitions map to Epicor GL Account categories.

Both sides of every journal entry migrate together to preserve trial balance integrity. Epicor requires that debits and credits balance within a journal entry batch. We extract journal entry data from the Spectrum Add G/L Journal Entries web service which returns both debit and credit lines per entry, and insert the balanced batch into Epicor GL Journal Entry with the same entry date, description, and source module reference. Historical entries are posted as Adjusting entries with a migration-source reference flag for audit. Trial balance reconstruction is validated after this phase before sub-ledger migration begins.

Spectrum's Chart of Accounts with Excel template bulk import maps to Epicor's GL Account Master with segment definitions. The number of segments (typically 1-6 in Spectrum) maps to Epicor GL Account segments, and the rollup hierarchies map to Epicor Account Groups. We conduct a pre-migration mapping session to confirm segment count and meaning, then bulk-load the account structure before any transaction data moves.

Spectrum Employee records migrate to Epicor Employee with personal data, dependents, and insurance records. Certified payroll and union rule compliance fields require remapping because Spectrum stores these in configuration-specific fields that vary by customer. We extract the union rule set, deduction codes, and pay group assignments during scoping, then map them to Epicor's Pay Group, Deduction, and Tax Configuration during migration. Any training certifications migrate as Employee Training records in Epicor HR.

Spectrum payroll is one of its strongest modules, supporting multi-union rules and certified payroll. Pay stubs, pay groups, and deduction codes carry over but deduction code remapping is required because Epicor's deduction model uses different code structures. We identify all active deduction codes, benefit codes, and garnishment codes in Spectrum and map them to Epicor equivalents during the mapping session. Historical pay stub records migrate as Payroll History with full earning and deduction detail. Union rule sets are preserved in Epicor Pay Groups as pre-configured rules.

Spectrum Equipment Tracking records migrate to Epicor Equipment Master with the same equipment ID, description, serial number, and classification. Preventive maintenance schedules and work orders attached to equipment migrate as Epicor JobMtl/JobOper with the maintenance type flagged. Equipment Work Order components and notes carry over as Job records with the maintenance-type flag set. Any equipment images from Spectrum's Document Imaging service transfer as Equipment attachments in Epicor.

Spectrum Equipment Work Order records migrate to Epicor Field Service Work Orders or Plant Maintenance Work Orders depending on the destination configuration. The work order-to-equipment linkage is preserved as the EquipID reference. Labor hours, parts, and notes migrate to the corresponding work order detail records. If the customer uses Epicor's Field Service module, the work order migrates as an FS-Project-linked Work Order.

Spectrum A/R customer records and open invoice data migrate to Epicor Customer and AR Invoice records. Customer addresses, payment terms, and credit limits transfer directly. Open invoices (unpaid at migration date) migrate as Open AR invoices with the original invoice date and aging preserved. Historical paid invoices migrate as AR Invoice history records. The Spectrum invoice number becomes the Epicor InvoiceNum with a source-reference field for audit traceability.

Spectrum A/P vendor records and open invoice data migrate to Epicor Vendor and AP Invoice records. Vendor addresses, payment terms, and 1099 settings transfer directly. Open invoices (unpaid at migration date) migrate as Open AP invoices with the original invoice date and aging preserved. Historical paid invoices migrate as AP Invoice history records. The Spectrum invoice number becomes the Epicor InvoiceNum with a source-reference field for audit traceability.

Spectrum Inventory records migrate to Epicor Part records with the same part number, description, uom, and on-hand quantities by warehouse. Bin locations from Spectrum map to Epicor WarehseBin records. Part classes and commodity codes map to Epicor Product Group or UD fields. If Spectrum maintains lot or serial number tracking, those records migrate as PartLot entries with expiry dates and quantity balances.

Spectrum Service Request custom fields (up to 4 per form) migrate to Epicor UD (User-Defined) fields on the relevant business object. We extract the field definitions (label, data type, required flag) and current values during scoping, then create Epicor UD columns via the Kinetic Data Model before migration. If the destination allows fewer than 4 UD fields on a specific object, we flag the constraint during scoping for the customer to resolve before migration.

Project Log Images, Work Order Images, and Employee Images from Spectrum's Document Imaging web services migrate as Epicor Document Management attachments linked to the corresponding business object (Project, Job, Employee). Binary image data requires a separate transfer pass after relational records are inserted because image files must be uploaded after the parent record ID is known. We sequence document migration as the final pass after all primary records are committed.