Migrate from Maximum Software to Epicor Prophet 21

Maximum Software Customer records map to Epicor Customer with CustNum as the dedupe key. We preserve CustomerID, Name, Address, ShipTo locations, and credit limits. ShipTo addresses become Epicor ShipTo records linked via ShipToNum. Tax information from Maximum Software custom fields maps to Epicor's Tax Region assignment on Customer or ShipTo. Tax codes require manual verification against Epicor's tax jurisdiction configuration post-migration.

Maximum Software Vendor records map to Epicor Vendor with VendorID as the dedupe key. We preserve VendorID, Name, Address, RemitTo addresses, and payment terms. 1099 flagging from Maximum Software maps to Epicor's Vendor Tax information fields. PO approval thresholds and routing from Maximum Software custom fields become Epicor VendorPP records requiring manual configuration review.

Maximum Software GL Account structure maps to Epicor GL Account with COACode as the chart identifier and Account as the segment value. Natural account classification (Asset, Liability, Equity, Revenue, Expense) maps to Epicor GL Account Type and must match the account structure definition before import. Maximum Software custom segments (Division, Department, Location) require Epicor GL Account segments configured in the Chart of Accounts maintenance before data loads.

Maximum Software Item records map to Epicor Part with PartNum as the dedupe key. We preserve PartNum, PartDescription, Unit of Measure, cost layers (Standard, Average, Last), and Item Type (Stocked, Non-Stock, Service, Virtual). Maximum Software planning data (MinQty, MaxQty, ReorderPoint) maps to PartWhse on-hand and planning fields. The customer must configure Epicor's Cost ID and UOMClass before Part records insert.

Maximum Software BOM records map to Epicor PartBom with ParentPart as the header and ComponentPart as the line. BOM quantity per assembly, scrap percent, and BOM approved flag migrate to PartBom quantity, mtlBurRate, and Approved fields. Multi-level BOMs require parent-record lookup resolution before each level loads. The customer must configure Epicor's BOM Approved check workflow before production use.

Maximum Software Routing records map to Epicor PartOpr linked to JobHead or PartRev. Operation sequence, work center, setup hours, run hours, and labor overhead rates migrate to PartOpr OprSeq, OpCode, EstSetHours, EstProdHours, and BurdenHrs. We resolve work center references by labor code match against Epicor's WC table. Job scheduling (JobHead.StartDate, JobHead.DueDate) recalculates in Epicor based on PartOpr scheduling once migration completes.

Maximum Software open AR invoices map to Epicor InvcHead with InvoiceNum as the dedupe key. We preserve InvoiceDate, DueDate, InvoiceAmt, and open balance. Line items map to InvcDtl with PartNum, OurShipQty, UnitPrice, and DocExtPrice. Locked invoices (posted, no further adjustments) migrate with their full history. InvcHead.UpdateMode set to BPM-driven or manual depending on customer reconciliation preference.

Maximum Software open AP invoices map to Epicor APInvoiceHed with VendorNum and InvoiceNum as the composite key. We preserve Vendor invoice number, invoice date, due date, and open balance. Line items map to APInvoiceDtl with GL Account, Amount, and description. Tax amounts from Maximum Software custom fields map to APInvoiceTax records if Epicor's tax integration is configured.

Maximum Software Work Orders map to Epicor JobHead with JobNum as the dedupe key. We preserve JobHead.JobNum, PartNum, StartDate, DueDate, and assembly operations. JobMtl lines carry component PartNum, required quantity, and IssueMethod (Manual, BackFlush). JobOpr lines carry operation sequence, work center, and estimated hours. Open job status (released, scheduled, complete) migrates; jobs with no remaining operations set to JobHead.JobClosed = true.

Maximum Software User records map to Epicor User with UserID as the dedupe key. We preserve Name, Email, UserID, and security role assignments from Maximum Software permission groups. User must be active in Epicor before Owner references on JobHead, InvcHead, and Part records can resolve. Provisioning new Epicor Users is a customer admin task; we flag missing Users in a reconciliation report before migration.

Maximum Software custom fields and user-defined tables do not map directly to named Epicor equivalents. We extract the schema of any UD tables present in Maximum Software, document the field names and data types, and deliver a written inventory specifying which UD table each maps to in Epicor. Epicor UD fields (UD01-UD20) must be defined in the Classic desktop client before data inserts; populating them requires a BPM to set the value at insert time, as the UD Column Map tool alone does not support automatic population from external sources. This is a pair-specific gotcha that adds scope to any migration with heavy Maximum Software custom field usage.

Maximum Software attachments linked to Parts, Work Orders, or Customers do not migrate as native Epicor attachments in standard scope. We deliver a written inventory of all file-based attachments with their parent record type and record ID, and recommend either Epicor's Document Management module or an external storage strategy (S3, SharePoint) post-migration. If the customer requires in-system attachment migration, we scope that as a separate technical task.