Migrate from Deltek Costpoint to Epicor Prophet 21

Costpoint Organizations represent legal entities or business units driving billing, HR, and GL assignments. Epicor ERP uses Company as the legal entity container and Site to represent operating locations. We map Organization hierarchies 1:1 and preserve the owning-organization relationship as the Epicor Company-Site hierarchy. If the customer operates multiple Costpoint Organizations, each maps to a distinct Epicor Company within the same tenant or a separate Epicor tenant depending on whether inter-company billing is required.

Costpoint Projects are the core work container linked to contracts, billing formulas, labor categories, and budgets. Epicor ERP Projects support task hierarchies and project templates but do not have native CLIN/SLIN billing structures. We preserve the full project tree including sub-projects, project status, billing method (cost-plus, T&M, fixed-price), and the project-manager assignment. Billing formula details (fee overrides, ceiling controls) are captured as custom fields on Epicor Project since Epicor's native billing engine operates differently from Costpoint's billing module.

Costpoint's GL includes direct cost accounts, indirect cost pools (G&A, Fringe, Overhead), and burden schedules. Epicor ERP uses a standard Chart of Accounts with account types (Asset, Liability, Equity, Revenue, Expense) and segment structure. We map Costpoint direct cost accounts directly to Epicor GL accounts by type. Indirect cost pools require a crosswalk to Epicor GL segments, and burden schedule rates are documented as a lookup table for the customer's admin to configure in Epicor's rate setup rather than migrated as live calculation rules.

Costpoint Employee records include compensation history, HR organizations, labor category assignments, and DCAA-required timesheet metadata. Epicor ERP Employee records support personal data, employment history, and organizational assignments. We extract all active employee records with effective-dated compensation rows preserved as a historical compensation report. DCAA timesheet metadata (approval chain, required versus non-required) is mapped to a custom field set for manual configuration in Epicor Time and Expense since Epicor's time tracking does not include DCAA-specific approval routing.

Historical GL entries in Costpoint are stored with source module attribution (billing, payroll, AP, AR) and must preserve posting date, period, and debit/credit structure. We extract entries by date range and map to Epicor GL Journal Entry with the source module stored as a reference field. Entries are posted to the Epicor GL accounts mapped from the Costpoint Chart of Accounts crosswalk. Full historical entry migration is standard unless the customer elects a go-live snapshot approach (post go-live entries only) to reduce migration scope.

Costpoint AP records include vendor invoices, payment terms, and check/EFT batch data. Open AP (unpaid invoices) and payment history are separable export sets. We map Costpoint vendor IDs to Epicor Vendor records, preserve payment terms, and import open AP invoices as Epicor AP Invoices in Open status. Payment history is imported as posted AP Invoices with payment reference. ACH routing details for payment continuity migrate as part of the Vendor record.

Costpoint AR records track billed and unbilled amounts linked to Projects and CLIN/SLIN structures. The gross/net billing method flag embedded at the invoice header level must be preserved — this determines whether Epicor posts the receivable as gross or net and how the GL is affected at billing versus cash receipt. We extract the flag per invoice and configure Epicor AR to match; if the flag is lost, the receivable posts incorrectly and creates billing misstatements that are difficult to reverse after period close.

Costpoint Open Billing Detail records store the transaction-level detail feeding billing formulas (cost-based, hours-based, units-based) cross-linked to project hierarchies and CLIN/SLIN. Epicor ERP does not have a native equivalent to Costpoint's billing module. We export Billing Detail as a project transaction report, map unbilled amounts to Epicor Project Billing or AR Invoice lines depending on the Epicor edition, and preserve the billing formula type and fee parameters as custom fields on the Project record.

Costpoint Fixed Asset records include acquisition costs, depreciation schedules, funding sources, and asset classifications. We map asset books to Epicor depreciation calendars, preserve depreciation method and useful life, and flag any DCAA-specific funding source attribution as a custom field for the customer's admin to configure in Epicor Fixed Asset management.

Costpoint Vendor records include address, tax ID, payment terms, and W-9 status. We extract all active vendors and map to Epicor Vendor, preserving ACH routing details for payment continuity. W-9 status and 1099 reporting flags migrate to Epicor Vendor tax settings.

Costpoint supports project-specific and warehouse inventory with multi-project traceability. Epicor ERP uses Part as the inventory item master with warehouse tracking, lot/serial number management, and BOM/routing structures. We export item masters, on-hand quantities, and cost layers, flagging any lot or serial number tracking for Epicor Part lot/serial configuration. BOM data migrates to Epicor Part BOM if the customer licenses Epicor Manufacturing.

Costpoint Departments drive organizational cost collection and are linked to GL segments. We map department hierarchies 1:1 and preserve the department-to-account assignments that feed indirect cost pool allocation. Epicor Business Unit or Department serves the same organizational scoping function.

Timesheet and expense report records in Costpoint include employee, project, labor category, and billing status. We export submitted and approved entries by date range, preserving the DCAA-required approval chain as a documentation note for Epicor Time and Expense configuration. Epicor's time tracking does not include native DCAA compliance routing; the approval workflow is rebuilt post-migration.

Costpoint stores user-defined custom fields on Projects, Employees, Vendors, and Transactions as separate table extensions. Epicor ERP exposes UD fields (fields with _c suffix on standard tables) that require explicit configuration in the Epicor customization tools. We enumerate all Costpoint custom fields during discovery, determine which are business-critical versus cosmetic, and configure Epicor UD fields to match before migration. Epicor UD field logic (such as BPM-triggered field population) is documented separately for the customer's admin to rebuild.

Costpoint's internal workflow routing tables are rebuilt during every upgrade via the Workflow Toolkit (WFPTOOL) and are environment-specific. These tables cannot be migrated to Epicor ERP. We do not migrate them. Instead, we document the active workflow routing rules (approval chains, escalation paths, routing conditions) as part of migration scoping and deliver a written inventory with recommended Epicor BPM equivalents for the customer's admin to rebuild post-migration.