Migrate from Certinia ERP Cloud to Epicor Prophet 21

Certinia Accounts (extended Salesforce Account objects) map to Epicor Customer records. We preserve the billing address, shipping address, and any multi-entity assignment fields. Customer type (prospect, customer, competitor) maps to Epicor's Customer Type code. The Certinia Account Name becomes the Epicor Customer Name, and we preserve Account Number as a reference field for audit continuity. Dedupe resolution uses Company + Tax ID as the Epicor key.

Certinia Contacts (standard Salesforce Contact objects) map to Epicor Person records linked to the corresponding Epicor Customer. We preserve contact roles, email addresses, phone numbers, and any custom fields. The primary Contact relationship in Certinia maps to the Primary Ship To Person in Epicor. We note that Epicor's Person object does not have an Opportunity attachment model; opportunity linkage happens at the Order level rather than at the Contact level.

Certinia PSA Project records have no native Epicor equivalent because Epicor is not a PSA platform. We map Projects to Epicor Project (job costing) or Estimate records depending on the project type. Time-and-materials project budgets map to Epicor Estimate with quantity and cost breakdowns. Fixed-fee projects map to Epicor Project with revenue recognition milestones tracked as Project Phase milestones. We preserve project status, start and end dates, and the multi-dimensional analysis fields (region, department) from Certinia as Epicor Project Phase or Task codes.

Certinia PSA Budget records (rate-based, fixed, expense-only) map to Epicor Estimate lines or Project budget allocations depending on type. Rate-based budgets with resource cost rates become Epicor labor and material Estimate lines with pricing. Fixed budgets preserve the total contract value and phase distribution. Expense-only budgets map to Epicor miscellaneous charge Estimate lines. We flag any budget types with custom approval thresholds for manual review because Epicor's budget approval workflow requires separate configuration.

Certinia PSA Assignment records (Resources linked to Projects with booking dates and allocation percentages) map to Epicor Project Labor records or Resource Group allocations. We preserve booking dates, allocation percentage, and skill assignments as Epicor Resource Skill codes. We note that Epicor's resource scheduling is calendar-based rather than percentage-based; the translation requires a duration and hours model that may differ from Certinia's allocation model. Customer-specific billing rates from Certinia assignments map to Epicor Quote or Order pricing rules.

Certinia PSA Milestone objects (project deliverable due dates and completion status) map to Epicor Project Phase records with Task sub-records. Milestone dependencies (successor/predecessor) are captured as Certinia relationship records and translated to Epicor Task predecessors using the project's WBS structure. Due dates, completion status, and milestone type (billing, deliverable, review) map to Epicor Phase percent complete and Task comments. Milestones without a corresponding Epicor Project (Estimate-based billing) are staged for review before import.

Certinia PSA Billing Events (time-entry driven or milestone-driven invoice generation) map to Epicor Invoice records for recognized revenue and to Epicor Order records for billing events tied to project phases. We preserve the billing event header, line items (hours, expenses, materials), and the billing rule type. Recognized revenue from Certinia Billing Events maps to Epicor AR Invoice records. We flag any custom billing rule configurations (progress billing percentages, hold-back terms) for manual review because Epicor's billing rule setup is separate from the invoice record.

Certinia GL Entries (with multi-dimensional analysis fields for region, department, project) map to Epicor GL Journal records. We stage the data after entity and account code setup in Epicor to prevent undefined entity reference errors. Multi-currency entries from Certinia are translated using Epicor's currency conversion rules configured at the Company level. We flag any Certinia account codes that do not have a corresponding Epicor GL account number and generate a remapping table for the customer's finance team to validate before posting.

Certinia Invoices (generated from Billing Events or contracts) map to Epicor AR Invoice records with header and line items preserved. Open invoices migrate with their payment status and aging; paid invoices migrate as historical records. Linked payment records require AR record migration in the same run to maintain open-invoice integrity. We preserve invoice numbers, invoice dates, due dates, and all line item descriptions and amounts. Tax codes are mapped to Epicor Tax Usage codes.

Certinia Financial Management Fixed Asset records map directly to Epicor Fixed Asset records with depreciation schedules, asset categories, and book values preserved. We transfer asset acquisition date, depreciation method (straight-line, declining balance), useful life, and current book value. Asset categories map to Epicor Asset Class codes. Accumulated depreciation transfers as a separate GL journal entry to the accumulated depreciation account.

Certinia Purchase Orders and AP records map to Epicor PO and AP Invoice records. We migrate open POs with vendor assignments and approval status. Approval history is not accessible via Certinia's API and does not transfer; we document this gap in the handoff inventory so the customer's AP team can re-enter approval records if required for audit. Closed POs migrate as historical records without line-item detail reactivation.

Certinia SCM Product Mapping records from the SCM Accounting Connector require remapping to Epicor Part (or Product) records. The line type renaming from Certinia's internal migration (Freight and Handling to Freight, Customer Deposit to Deposit) is handled during this mapping phase. We capture the exact line type values at export time and apply the new names at import. Part numbers, descriptions, and unit of measure migrate to Epicor Part Master records.

Certinia Salesforce Users with PSA Resource Management attributes (skills, utilization targets, cost rates) map to Epicor User records. We map the user email, name, and active status. PSA-specific attributes (skills, utilization targets) have no Epicor native equivalent; we preserve these in a supplemental data file (CSV export) for the customer's team to reference when configuring Epicor resource groups and labor rates. Resource cost rates from Certinia migrate to Epicor Labor Rate codes.

Certinia custom objects built within the FinancialForce managed package are accessible via Salesforce API. We export custom object definitions and data together and map them to Epicor UD (User-Defined) tables or custom Erp.Tables as appropriate for the destination version. Lookup relationships between custom objects map to Epicor foreign key references using the same relationship structure. We note that Epicor UD table schema requires manual setup in Epicor Administration before data import; we provide the schema definition in the handoff package.