Migrate from Deltek Costpoint to Dolibarr ERP

Costpoint Organizations represent legal entities or business units driving billing, HR, and GL assignments. Dolibarr's Third Party module (table llx_societe) stores organizations and contacts as companies. We map Organization hierarchies 1:1 into Dolibarr Third Parties, preserving the owning-organization relationship as a parent Third Party reference. If the customer has multiple Organizations with independent GL segments, we create each as a distinct Third Party and configure Dolibarr's multi-entity accounting via the Multi-company module or a manual GL-segment dimension on accounts.

Costpoint Projects are the core work container with nested sub-projects, independent billing formulas, labor category assignments, and budget tracking. Dolibarr's Project module (llx_projet) stores a flat project with task-level line items but no native sub-project nesting. We flatten Costpoint's multi-level project tree: top-level projects map to Dolibarr Projects, and Costpoint sub-projects map to Dolibarr Tasks under the parent Project. Billing formula type (cost-plus, T&M, fixed-price) and fee overrides migrate as custom fields on the Dolibarr Project since Dolibarr does not have a native formula-driven billing engine.

Costpoint's GL Chart of Accounts includes direct cost accounts, indirect cost pools (G&A, Fringe, Overhead), and burden schedules with CAS alignment. Dolibarr's accounting module uses a standard double-entry Chart of Accounts (llx_comptes) without a native burden schedule concept. We split Costpoint cost pools into separate GL accounts: G&A pool maps to a designated indirect expense account range, Fringe burden maps to a separate liability or expense account, and Overhead maps to its own pool account. The burden rate and allocation keys are preserved as custom fields on the account records for manual allocation in Dolibarr.

Costpoint Employee records include compensation history, HR organization assignments, labor category mappings, and DCAA-required timesheet metadata. Dolibarr's User module (llx_user) stores employees with login credentials, but DCAA-specific metadata (such as timesheet approval chain and incurred cost classification) has no native Dolibarr field. We migrate Employees to Dolibarr Users, preserving effective-dated compensation history in a custom compensation table (llx_user_compensation), labor category as a User property, and DCAA timesheet metadata as custom User fields.

Costpoint GL entries are stored with source module attribution (billing, payroll, AP, AR), posting date, fiscal period, and debit/credit structure. Dolibarr's double-entry accounting stores entries in llx_accounting_bookkeeping. We extract historical GL entries by date range, map each Costpoint journal line to a Dolibarr AccountingRecord with the correct account number (cross-referenced to the Chart of Accounts mapping), debit/credit amount, and posting date. Source module attribution is preserved as a custom field on the record.

Costpoint AP records include vendor invoices, payment terms, check/EFT batch data, and approval status. Dolibarr's supplier invoice module (llx_facture_fourn) handles vendor AP with the same open/paid/closed status lifecycle. We map open AP (unpaid invoices) and historical AP records into Dolibarr Supplier Invoices, preserving vendor ID cross-references, invoice amounts, due dates, and payment terms. If Costpoint uses ACH routing for payments, those details migrate to the Dolibarr Third Party (vendor) record.

Costpoint AR records track billed and unbilled amounts linked to Projects and CLIN/SLIN structures. Dolibarr's customer invoice module (llx_facture) handles AR. The gross/net billing method flag embedded at the Costpoint invoice header level is critical: this flag controls how the GL posts at billing versus cash receipt. We preserve it as a custom field billing_method__c on each Dolibarr Customer Invoice. If the flag is lost, the customer must manually verify posting method in Dolibarr after migration.

Costpoint Open Billing Detail stores transaction-level detail feeding billing formulas (cost-based, hours-based, units-based) cross-linked to project hierarchies and CLIN/SLIN structures. Dolibarr invoices carry line items without a native formula engine. We migrate Billing Detail records as Dolibarr Invoice Line items or Project Task entries, linking each to the corresponding Dolibarr Project and preserving the Costpoint billing method (cost-plus rate, T&M hourly rate, fixed-price per unit) as a custom field on the line.

Costpoint Fixed Asset records include acquisition costs, depreciation schedules, funding sources, and asset classifications. Dolibarr's Asset module (llx_asset) handles fixed assets with depreciation tracking. We map asset records with acquisition cost, acquisition date, depreciation method (straight-line or declining), useful life, and accumulated depreciation. Funding source classification migrates as a custom asset property. Any DCAA-specific capitalisation thresholds are documented separately for the customer's compliance team to review.

Costpoint Vendors include address, tax ID, payment terms, W-9 status, and ACH routing details. Dolibarr Third Parties serve as both customers and vendors via a Tiers type flag. We extract all active Vendors and map to Dolibarr Third Parties with the Supplier property enabled, preserving tax ID as a custom field, ACH routing as a bank account record linked to the Third Party, and payment terms as a Dolibarr Payment Term reference.

Costpoint supports project-specific and warehouse inventory with multi-project traceability, lot and serial number tracking. Dolibarr's Product module (llx_product) stores item masters with on-hand quantity and cost layers. We export item masters, on-hand quantities, and cost layers. Lot and serial number traceability migrates to Dolibarr Product Lots if the Lot/Serial module is enabled; otherwise these are flagged as a gap requiring module activation or a manual reconciliation process.

Costpoint Departments drive organizational cost collection and are linked to GL segments for indirect cost allocation. Dolibarr has no native cost center object, but Department hierarchies can be mapped to User Groups (llx_usergroup) with a custom department_code field, or to Projects used as cost-collection containers. We determine the strategy during scoping based on whether the customer uses Dolibarr's project cost tracking or a pure GL-segment approach. GL-segment-based allocation is the most structurally aligned migration path.

Costpoint timesheet and expense report records include employee, project, labor category, billing status, and DCAA-required approval chain. Dolibarr's HR/Expense module stores expense reports and timesheet entries. We migrate submitted and approved entries by date range, preserving the project assignment, labor category, and expense category. The DCAA approval chain (supervisor, timesheet administrator sign-off) migrates as custom fields on the Dolibarr expense record since Dolibarr's native approval workflow does not include the same CAS-aligned chain of custody metadata.

Costpoint custom fields on Projects, Employees, Vendors, and Transactions are stored as separate database table extensions and do not surface in standard export services without deliberate configuration. We enumerate all custom fields during discovery, determine which are business-critical versus cosmetic, and configure them as parallel extraction steps alongside standard object exports. In Dolibarr, custom fields map to the Extra fields feature (champss) on each relevant object (Project, User, Third Party, Invoice). Custom field values transfer directly as long as data types are compatible (text, integer, select, date, checkbox supported natively; complex cross-references require custom mapping.