Migrate from Stride ERP to Epicor Prophet 21

Stride COA records with parent-child hierarchy map to Epicor GL Account with AccountType and IsActive flags. We extract account codes, descriptions, and parent references, then configure Epicor's segment structure to match the account hierarchy depth. If Stride uses country-specific segment values (Nigeria vs Canada tax rules), we collapse them into a single segment or map to Epicor's Entity dimension before import. The account rollup totals are recalculated in Epicor after COA import.

Stride Customer records (contact details, billing addresses, credit terms, lifecycle stage, custom fields) map to Epicor Customer with the Party and Person/Company structure. We preserve Stride's customer codes as Epicor CustNum, resolve the Bill-To and Ship-To address relationships, and flag any customer records that have been soft-deleted in Stride to avoid importing inactive customers into Epicor.

Vendor master data maps to Epicor Vendor with AP aging balances, payment terms, and bank details preserved. We flag any Stride vendor records that have been soft-deleted or have a zero balance history to prevent inactive suppliers from cluttering Epicor's vendor list. Vendor code from Stride becomes Epicor VendorNum.

Outstanding Stride invoices, credit memos, and payment records require sequencing to match Epicor's fiscal period structure. We map Stride invoice numbers to Epicor's AP InvoiceNum and AR InvoiceNum formats, preserve payment terms, discount codes, due dates, and aging buckets. Open items are imported as posted invoices with a remaining balance rather than as open items in Epicor's AP/AR aging tracker; the customer's AP/AR team reconciles aging totals post-import.

Str Asset records carry location assignments, depreciation schedules, and accumulated depreciation balances. We extract the depreciation history table separately from the asset master, identify the depreciation method (straight-line, declining balance, sum-of-years digits) embedded in each record, and reconstruct book value using Epicor's native depreciation engine rather than importing computed book values directly. This avoids Epicor recalculating depreciation from stale in-service dates.

Stride SKU-level items with warehouse locations, reorder points, and current stock quantities map to Epicor Part records. Stride's multi-location inventory requires us to request the detailed inventory ledger with location codes rather than the standard aggregated export, then reconstruct the multi-site structure in Epicor using Epicor Warehse and PartWhse records. We flag any items where the sum of location quantities does not match the Stride aggregate total.

Employee records transfer to Epicor Employee with department assignments, job titles, employment status (active, terminated, on leave), and contact information. We handle active and terminated employees separately to preserve the employment history. Stride's employee IDs map to Epicor EmpID, and the department structure from Stride maps to Epicor's HR Organization hierarchy.

Stride payroll runs store pay periods, deduction codes, benefit enrollment flags, and compensation amounts in a format that does not map automatically to Epicor's payroll schema. We parse the payroll export row by row, map Stride deduction codes to equivalent Epicor deduction and benefit categories, and load compensation history as Labor History records with effective-dated entries. Stride on Basic tier does not include Payroll, so we confirm active module entitlement before including payroll in the export scope.

Project records with status, assignees, milestones, task hierarchies, billable rates, and project type transfer as-is to Epicor Project. Stride project custom fields map to Epicor ProjectPhase and ProjectTask custom properties. We preserve the project billing method (T&M, Fixed Price, Cost Plus) and revenue recognition settings, and flag any projects in a status that would require Epicor's revenue recognition engine to recalculate after import.

Purchase Requests are an add-on module in Stride and may not exist on Basic tier accounts. Where they exist, we map approval workflow status and line items to Epicor PurReq with line types, quantities, and unit costs preserved. Approval chain structures do not migrate and must be re-established in Epicor's workflow configuration.

Stride Ticket records including status, assignee, customer association, and conversation history map to Epicor Case. SLA configuration does not transfer and must be re-established in Epicor's Service Layer. Conversation history is imported as Case entries in chronological order, with the original timestamps preserved.

Document Management System attachments are file-level exports associated with parent objects (Project, Customer, Employee). We associate each document with its Epicor parent record by matching the Stride record identifier, then load the file metadata into Epicor's EDMS structure. File naming conventions vary by Stride customer configuration, so we clean and normalize file names during import to match Epicor's document management conventions.