Migrate from Deltek Costpoint to Odoo ERP

Costpoint Organizations represent legal entities or business units driving billing, HR, and GL assignments. Odoo uses Companies for multi-entity setups. During scoping, we determine whether each Costpoint Organization maps to a separate Odoo Company, a Department within a single Company, or a tag-based classification, based on whether the entities share a chart of accounts, fiscal year, or currency. Organizations that share a fiscal structure map to Departments; those with independent ledgers map to Companies. The owning-organization relationship on Projects and Employees is preserved as a Many2one reference to the mapped Company or Department.

Costpoint Projects are the core work container linked to contracts, billing formulas, labor categories, and budgets. We map the full project tree including sub-projects and flag any inactive projects that should archive rather than import as active. In Odoo, each Project can link to a Sale Order (for billing) or stand alone (for internal work). CLIN/SLIN structures from Costpoint contracts map to Odoo project tasks or milestones. Billing formula type (cost-plus, T&M, fixed-price) is preserved as a custom field on the Odoo Project so that the Odoo administrator can configure the corresponding invoicing policy post-migration.

The GL Chart of Accounts in Costpoint includes direct cost accounts, indirect cost pools (G&A, Fringe, Overhead), and burden schedules. We map these by account type to Odoo's account.account model, preserving account codes and account type assignments (expense, revenue, asset, liability). The primary challenge is mapping Costpoint's indirect cost pool accounts to Odoo's analytic account model. We create a parallel set of analytic accounts mirroring the cost pool structure so that Odoo's cost analysis reports can reproduce the indirect rate distribution from the Costpoint burden schedule.

Costpoint burden schedules define how indirect costs (fringe, overhead, G&A) are applied to direct labor and materials per project and labor category. Odoo does not have a native burden schedule engine. We map burden schedules to a combination of Odoo analytic accounts (for cost collection) and analytic distribution rules on project tasks, which apply a percentage split of labor costs to the relevant indirect pool. DCAA contractors must validate that the resulting analytic distributions reproduce the indirect rate structure required for incurred cost submissions. This is a configuration step that requires a GovCon specialist to review post-migration.

Costpoint Employee records include compensation history, HR organization assignments, labor category mappings, and DCAA-required timesheet metadata. We extract all effective-dated compensation rows and preserve them as historical records in Odoo. Timesheet approval rules in Costpoint (supervisor, organizational) are documented for rebuild in Odoo using Odoo Timesheets approval flows or hr_approval rules. Odoo's Employee model requires a linked User account for timesheet entry; we map Costpoint employee IDs to Odoo user accounts by email or employee number.

Costpoint Vendors include address, tax ID, payment terms, and W-9 status. We extract all active vendors and map to Odoo contacts with the Vendor flag enabled, preserving ACH routing details for payment configuration. Vendor type (1099 vs. direct pay) migrates as a custom field on the contact record. Payment terms from Costpoint map to Odoo account.payment.term records created during configuration.

AP records in Costpoint include vendor invoices, payment terms, and check or EFT batch data. Open AP (unpaid invoices) and payment history are exported as separate sets. We map Costpoint vendor invoice records to Odoo account.move records of type in_invoice, preserving invoice number, invoice date, due date, and line-item amounts against the mapped vendor and GL accounts. Payment history maps to Odoo account.move records of type payment, linked to the corresponding vendor bill.

AR records in Costpoint track billed and unbilled amounts linked to Projects and CLIN/SLIN structures. Open AR and historical invoices are exported separately. The gross/net billing method flag from the Costpoint Configure Billing Settings screen is extracted and preserved as a custom field on the Odoo account.move record; without this flag, Odoo will post the receivable differently than Costpoint, creating material billing misstatements for T&M and cost-plus contracts. Unbilled AR (Open Billing Detail) maps to Odoo project milestones or sale order lines pending invoicing.

Historical GL entries are stored with source module references (billing, payroll, AP, AR) and must preserve posting date, period, and debit/credit structure. We extract entries by date range and map to Odoo account.move records of type entry within the corresponding journal. GL entries from Costpoint must be imported in date order within each period to preserve Odoo's period-sequence integrity. Organizations migrating historical GL data (typically 2-5 years) should expect extended timeline and reconciliation effort; we recommend a focused GL migration scope reviewed by the customer's controller before final load.

Fixed asset records in Costpoint include acquisition costs, depreciation schedules, funding sources, and asset classifications. We map asset books to Odoo account.asset models with matching depreciation tables (straight-line, declining balance). Acquisition cost, in-service date, and useful life migrate directly. DCAA categorization flags (funding source, asset category for incurred cost allocation) are preserved as custom fields on the Odoo asset record. Assets under construction or pending capitalization are flagged for Odoo administrator review before activation.

Timesheet and expense report records in Costpoint include employee, project, labor category, and DCAA-required approval chain. We export submitted and approved entries by date range and map them to Odoo account.analytic.line (timesheets) and hr.expense (expense reports). The Costpoint approval chain (employee timesheet submitted, supervisor approved, posted to GL) is documented for rebuild in Odoo using hr_approval rules or project-level validation workflows. Entries still in draft or pending approval at migration time are flagged in a separate reconciliation report for manual disposition.