How long does a Deltek Costpoint to Acumatica migration take?

Small-to-mid migrations covering one entity, fewer than 25,000 transactional records, and standard Costpoint modules (Projects, AP/AR, Time, GL) typically complete in 7–14 days of active migration time. Larger setups with multiple Costpoint GFMORG entities, active government contracts with CLIN structures, or over 100,000 records extend to 4–8 weeks. Pre-migration schema planning and Acumatica branch/subaccount configuration typically add 1–2 weeks before data begins moving. The longest single step is usually validating GL account crosswalk integrity and resolving subaccount segment overflow before loading transactional data.

Will my Costpoint approval workflows and notification rules migrate to Acumatica?

No. Costpoint approval routing, escalation timers, and notification rules are stored in Costpoint's internal workflow tables and do not export through the API. These must be rebuilt in Acumatica using Acumatica's Notification Templates, Approval Maps, and Screen-Level Approval workflows. FlitStack exports your Costpoint workflow rule definitions as a structured configuration reference document so your Acumatica admin can rebuild each rule systematically. Automated approval chains for government contracting (DCAA timesheet certification routing) require specific Acumatica customization and should be scoped with your Acumatica implementation partner.

What happens to Costpoint CLIN and SLIN line items in Acumatica?

Costpoint CLIN/SLIN line items are a government contracting billing construct with no direct Acumatica equivalent. We map each Costpoint CLIN to a Project Task in Acumatica and store the original CLIN identifier in a custom field on the task (CLIN_Reference__c). The billing formula (e.g., Cost Plus Fee on Cost) is preserved as a description note and must be configured as an Acumatica Project Billing Rule before the project goes live for billing. If your Costpoint contracts use provisional billing rates or rate adjustments tied to CLIN performance, those require a pre-migration rate matrix workshop to ensure Acumatica billing rules produce equivalent results.

Can I migrate Costpoint custom fields built with Extensibility Designer to Acumatica?

Yes, but Extensibility Designer fields need type-aware translation. FlitStack inventories every custom field created in Costpoint Extensibility Designer — including field type, pick-list values, and whether it is calculated or user-maintained — and produces an Acumatica field mapping recommendation for each. Date, text, and numeric UDFs translate directly to equivalent Acumatica custom fields. Pick-list UDFs typically become Acumatica Segmented Keys or custom selector fields. Calculated formula UDFs cannot be replicated in Acumatica without a customization project and are flagged as reference-only fields for manual rebuild.

How does the Costpoint three-way account crosswalk translate to Acumatica's subaccount model?

Costpoint's account code structure (Account-Organization-Department) with an optional GFMORG hierarchy splits into Acumatica's Account segment (the main GL account) and Subaccount segments (one per dimension such as department, cost type, and project). FlitStack analyzes every unique Costpoint account combination, calculates the maximum character length required for each subaccount segment, and pre-configures Acumatica's subaccount mask to avoid overflow. Multi-segment subaccounts with more than four dimensions require an Acumatica Customized Subaccount schema and are flagged before migration loads begin.

Does the migration affect my Costpoint account during the cutover?

No. FlitStack uses read-only API access to extract data from Costpoint — no records are modified, deleted, or locked in Costpoint during the migration. Your team continues working in Costpoint throughout the process. A delta-pickup window of 24–48 hours after the full load captures any records created or modified in Costpoint during the cutover window, ensuring Acumatica reflects Costpoint's final state at go-live. Open purchase orders, pending invoices, and in-progress timesheets are all included in the delta pickup.

What DCAA compliance data can FlitStack migrate from Costpoint, and what requires manual setup in Acumatica?

FlitStack migrates the DCAA compliance flag (DCCA_Compliant__c) from Costpoint Employee records as a custom boolean field on Acumatica Employees, preserves original timesheet submission timestamps for each time entry, and carries over incurred cost submission metadata as custom fields on Projects. However, Acumatica does not natively enforce DCAA timekeeping controls — required note text on time entries, future-period entry blocking, and manager timesheet certification routing must be configured manually as screen-level validation rules or Acumatica customization projects. A DCAA compliance workshop is recommended before go-live.

Deltek Costpoint to Acumatica Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Deltek Costpoint and Acumatica both handle project-based financials, but their schemas diverge significantly at the billing and compliance layers. Costpoint organizes data around contracts with embedded DCAA compliance fields, government billing rate tables, and CLIN/SLIN structures that Acumatica represents differently — Projects linked to branches, AR/AP with tax zones, and subaccounts keyed by cost type. FlitStack AI extracts Costpoint master records, transactional history, and open documents via the Costpoint REST API, transforms labor distribution rows into Acumatica labor items, maps contract billing formulas to Acumatica's Projects billing configuration, and loads GL account balances into the Chart of Accounts with subaccount masks intact. For data destined for Acumatica, FlitStack uses Acumatica OData v4 endpoints to write records and leverages Acumatica's branch-and-subaccount segmentation, ensuring that each entity's legal entity structure is preserved. Approval workflows, notification rules, and custom Costpoint Extensibility Designer screens are not portable — we export the definitions as configuration reference for manual rebuild in Acumatica's Customization Project editor. The migration runs against a scoped Acumatica API connection while your Costpoint instance stays fully operational, and a 24‑48 hour delta pickup captures any changes made during cutover.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Object mapping

How Deltek Costpoint objects map to Acumatica

Each row shows how a Deltek Costpoint object lands in Acumatica, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Deltek Costpoint

Project / Project Header

maps to

Acumatica

Project

1:1

Fully supported

Costpoint projects map directly to Acumatica Projects. The project description, status, start/end dates, and customer reference transfer as-is. Costpoint's project hierarchy (parent/child) maps to Acumatica's Project Template or parent project linkage. Budget amounts from Costpoint become Project Budget records in Acumatica.

Deltek Costpoint

Contract / Agreement

maps to

Acumatica

Customer + Project Billing Rule

1:1

Fully supported

Costpoint contract records contain funding limits, award type (T&M, FP, CP), and CLIN definitions. These split into an Acumatica Customer record (for billing terms) and a Project Billing Rule configuration (for rate/schedule setup). CLIN line items from Costpoint are preserved as Project Task billing notes or custom fields on Acumatica.

Deltek Costpoint

Employee

maps to

Acumatica

Employee + Employee Class

1:1

Fully supported

Costpoint employees transfer to Acumatica Employees with name, email, hire date, and employment status. Labor category from Costpoint maps to the Employee Class in Acumatica, which controls default billing rates and GL labor accounts. DCAA timesheet flag from Costpoint becomes a custom field on Acumatica Employee.

Deltek Costpoint

Vendor

maps to

Acumatica

Vendor

1:1

Fully supported

Costpoint vendors migrate to Acumatica Vendors with name, address, payment terms, and 1099 flag. CAGE codes and SAM registration status are stored as custom fields in Acumatica since they have no native equivalent. EDI settings from Costpoint require manual reconfiguration in Acumatica's Vendor Details.

Deltek Costpoint

Timesheet / Time Entry

maps to

Acumatica

Time Entry

1:1

Fully supported

Costpoint timesheet rows (employee, date, project, labor task, hours, status) map to Acumatica Time Entries linked to the corresponding Project and Task. Approval status from Costpoint is preserved as a reference flag; Acumatica approval workflows require separate configuration. Original submitted timestamps are retained for audit trail.

Deltek Costpoint

Expense Report

maps to

Acumatica

Expense Receipt + Employee Expense

1:1

Fully supported

Costpoint expense reports with line items (date, vendor, amount, project, GL account) transfer to Acumatica Expense Receipts linked to the Project. Receipt images attached to Costpoint expense records are downloaded and reattached to the corresponding Acumatica records. Per-diem and mileage calculations from Costpoint are preserved as custom fields for reference.

Deltek Costpoint

Purchase Order

maps to

Acumatica

Purchase Order

1:1

Fully supported

Open Costpoint POs with line items (item, quantity, unit cost, GL account, vendor) transfer to Acumatica POs. Received quantities to date are reflected in Acumatica PO receipts. Closed POs are logged as historical records in a custom table. PO approval workflows are not carried over.

Deltek Costpoint

Invoice / AR Billing

maps to

Acumatica

AR Invoice

1:1

Fully supported

Costpoint AR invoices map to Acumatica AR Invoices with customer, invoice number, date, amount, and project reference. Line items include description, quantity, and billing amount. Retainage amounts from Costpoint are preserved as custom fields on Acumatica. Invoice templates and print formats require rebuild in Acumatica.

Deltek Costpoint

GL Account

maps to

Acumatica

Account + Subaccount

1:1

Fully supported

Costpoint's three-way account code (Account-Org-Department) splits into Acumatica Accounts (main segment) and Subaccounts (branch/dimension segments). The Costpoint GFMORG hierarchy maps to Acumatica Branches, each representing a legal entity or cost center. FlitStack validates subaccount masks before loading to avoid dimension overflow errors.

Deltek Costpoint

AP Invoice / Voucher

maps to

Acumatica

AP Invoice

1:1

Fully supported

Costpoint AP vouchers with vendor, invoice number, amount, and distribution lines transfer to Acumatica AP Invoices. GL distribution from Costpoint maps to the corresponding Acumatica Account + Subaccount combination. Prepaid invoices and retainage payable from Costpoint carry over as separate Acumatica AP adjustment records.

Deltek Costpoint

Billing Rate Table

maps to

Acumatica

Employee Class Billing Settings + Project Rate Matrix

1:1

Fully supported

Costpoint billing rate tables (per employee class, labor category, and contract) translate to Acumatica Employee Class billing rates and Project-specific rate overrides. The mapping requires a rate matrix crosswalk since Costpoint rates can be contract-scoped while Acumatica rates are project-task-scoped.

Deltek Costpoint

Custom Fields (UDf)

maps to

Acumatica

Custom Fields on respective screens

1:1

Fully supported

Costpoint user-defined fields (UDFs) added via Extensibility Designer or the UDEF screen transfer to Acumatica as custom fields on the equivalent screen. Field type translation is required: Costpoint date UDFs become Acumatica date fields, pick-list UDFs become Acumatica segmented keys or custom selectors, and numeric UDFs become Acumatica float fields.

Deltek Costpoint

Costpoint Workflow Tables

maps to

Acumatica

Not migrated

1:1

Fully supported

Costpoint approval routing, escalation rules, and workflow states stored in internal Costpoint workflow tables have no direct Acumatica equivalent. FlitStack exports the Costpoint workflow rule definitions as a configuration document; Acumatica notification maps and approval maps are built manually from that reference.

Deltek Costpoint

Attachment / Document

maps to

Acumatica

Files / Notes on respective records

1:1

Fully supported

Documents attached to Costpoint records (contracts, projects, invoices) are downloaded by FlitStack and reattached to the corresponding Acumatica records using the Files module. File size limits from Acumatica apply (default 25MB per file). Inline images in Costpoint notes are extracted and re-hosted.

Deltek Costpoint	Acumatica	Compatibility
Project / Project Header	Project1:1	Fully supported
Contract / Agreement	Customer + Project Billing Rule1:1	Fully supported
Employee	Employee + Employee Class1:1	Fully supported
Vendor	Vendor1:1	Fully supported
Timesheet / Time Entry	Time Entry1:1	Fully supported
Expense Report	Expense Receipt + Employee Expense1:1	Fully supported
Purchase Order	Purchase Order1:1	Fully supported
Invoice / AR Billing	AR Invoice1:1	Fully supported
GL Account	Account + Subaccount1:1	Fully supported
AP Invoice / Voucher	AP Invoice1:1	Fully supported
Billing Rate Table	Employee Class Billing Settings + Project Rate Matrix1:1	Fully supported
Custom Fields (UDf)	Custom Fields on respective screens1:1	Fully supported
Costpoint Workflow Tables	Not migrated1:1	Fully supported
Attachment / Document	Files / Notes on respective records1:1	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Deltek Costpoint gotchas

High

Oracle-to-SQL Server database conversion required for on-premise migrations

High

Gross vs. net billing method is embedded at the invoice header level

Medium

Custom fields require explicit enumeration and configuration

Medium

Workflow tables are upgrade-specific and cannot be migrated

Medium

Version parity between source and destination is mandatory for cloud migrations

Acumatica gotchas

High

API user licenses cap concurrent sessions and request throughput

High

Multi-tenant filtering requires CompanyID awareness

Medium

Custom fields require separate discovery before field mapping

Medium

Notes and attachments use a separate linked table structure

Low

Implementation timelines frequently run 3–9 months end-to-end

Deltek Costpoint gotchas		Acumatica gotchas
Severity	Issue	Severity	Issue
High	Oracle-to-SQL Server database conversion required for on-premise migrations	High	API user licenses cap concurrent sessions and request throughput
High	Gross vs. net billing method is embedded at the invoice header level	High	Multi-tenant filtering requires CompanyID awareness
Medium	Custom fields require explicit enumeration and configuration	Medium	Custom fields require separate discovery before field mapping
Medium	Workflow tables are upgrade-specific and cannot be migrated	Medium	Notes and attachments use a separate linked table structure
Medium	Version parity between source and destination is mandatory for cloud migrations	Low	Implementation timelines frequently run 3–9 months end-to-end

Pair-specific challenges

DCAA compliance fields require manual Acumatica configuration

Costpoint stores DCAA timekeeping controls — compliant/non-compliant flag, timesheet certification requirements, and incurred cost submission fields — as native properties on labor records. Acumatica has no equivalent native fields. We preserve the DCAA flag as a custom Employee field (DCCA_Compliant__c) and carry the original submitted timestamp for each timesheet row, but Acumatica's time entry screen validation rules (required note text, future-period blocking, manager approval routing) must be configured manually in the Time Entry screen's行-level validation or via a customization project before go-live.
Costpoint CLIN/SLIN billing formulas split across Acumatica Projects and custom fields

Costpoint contract billing formulas operate at the CLIN line level with cost-pool burdens, provisional billing rates, and fee overrides. Acumatica's Project Billing Rule engine handles rate schedules and billing cycles at the Project-Task level but does not natively support CLIN structures. We map each Costpoint CLIN to a combination of Acumatica Project Tasks (for the deliverable) and a custom CLIN reference field on the task. The actual fee calculation formulas (e.g., Cost Plus Fee on Cost as documented in Costpoint Billing) require a pre-migration workshop so Acumatica billing rules can be configured to produce equivalent results before transactional data lands.
Three-way account crosswalk creates subaccount segment complexity

Costpoint's three-way account code structure (Account-Organization-Department) with an optional GFMORG hierarchy can generate account codes that exceed Acumatica's default 30-character subaccount segment length. FlitStack inventories every unique Costpoint account code combination before migration, calculates the maximum segment length required, and pre-configures Acumatica's subaccount mask to accommodate the widest combination. If Costpoint uses more than 4 subaccount segments, we flag this and recommend an Acumatica Customized Subaccount schema before data loads begin.
Costpoint custom Extensibility Designer fields need type-aware translation

Custom fields created in Costpoint Extensibility Designer can use field types that do not map directly to Acumatica: date/time with timezone offsets, integer pick-lists with external ID sources, or multi-select text fields. FlitStack's pre-migration audit enumerates every Extensibility Designer field, classifies its type, and generates an Acumatica field type recommendation (Date, Segmented Key, LongText, etc.) for each. Some Costpoint calculated fields (formula UDFs) cannot be replicated in Acumatica without a customization project — these are flagged as reference-only custom fields with a note that the formula logic must be rebuilt in Acumatica's calculation framework.
Intercompany and multi-entity Costpoint setups require Acumatica branch consolidation

Government contractors running Costpoint with multiple GFMORG entities or intercompany billing pools face a structural challenge in Acumatica: each Costpoint GFMORG entity must map to either an Acumatica Branch (for legal entity separation) or a Customer record (for intercompany billing), depending on whether the organizations are separate legal entities. FlitStack produces an entity mapping worksheet during discovery. If Costpoint uses intercompany elimination entries, Acumatica's Elimination Subsidiary feature must be enabled and configured before the migration loads — this is a pre-flight requirement, not a post-migration task.

Migration approach

Six steps for a successful Deltek Costpoint to Acumatica data migration

Map Costpoint schema to Acumatica screen equivalents

FlitStack inventories all Costpoint modules in use — Projects, Contracts, Employees, Vendors, GL, AP, AR, Time & Expense, and any Extensibility Designer custom fields — and produces a schema mapping document that assigns each to the nearest Acumatica screen. We document the three-way account crosswalk transformation, CLIN-to-task splitting logic, and custom field type recommendations. This document is the shared reference for your Acumatica admin to pre-create branches, subaccount masks, and custom fields before any data loads.
Extract master data and transactional history via Costpoint API

Using Costpoint's REST API endpoints (Projects, Employees, Vendors, Contracts hubs) and the Integration Console bulk export, FlitStack extracts all active records and open transactions in a single pass. Historical closed records (completed projects, paid invoices older than a configurable cutoff) can be excluded or summarized based on your preference. Extensibility Designer field definitions are exported separately for the Acumatica customization reference package. Costpoint remains fully operational during this read-only extraction.
Transform data and load master records first

FlitStack applies the field mapping rules — transforming account codes into Acumatica Account + Subaccount pairs, mapping labor categories to Employee Classes, splitting CLINs into Project Tasks with custom reference fields, and translating billing rate tables into Acumatica rate matrix rows. Master records (Vendors, Employees, GL Accounts, Customers) are loaded first so that transactional records can reference them by ID. We run validation queries against Acumatica after each master load to confirm referential integrity before proceeding.
Run sample migration with field-level diff

A representative sample — typically 200–500 records across Projects, Employees, open POs, recent invoices, and time entries — migrates to a staging Acumatica company. FlitStack generates a field-level diff comparing source values against the loaded Acumatica records, highlighting any truncated subaccount codes, unmapped pick-list values, or missing vendor references. Your team reviews the diff and approves or adjusts the mapping rules before the full migration commits.
Full migration with delta pickup and rollback plan

The full transactional load runs — Projects, Contracts, Employees, Vendors, GL balances, AP/AR, POs, and time/expense entries — against the target Acumatica company. A delta-pickup window of 24–48 hours captures any new Costpoint entries created during the cutover. FlitStack generates a reconciliation summary comparing total record counts, GL trial balance totals, and open PO/invoice balances between Costpoint and Acumatica. One-click rollback is available if reconciliation fails; the audit log captures every operation for post-mortem if needed.

Platform deep dives

Context on both ends of the pair

Deltek Costpoint

Source

Strengths

Built-in DCAA compliance with CAS-aligned cost structures and incurred cost submission generation.
Multi-level project hierarchy supporting contracts, tasks, and sub-projects with independent billing formulas.
Integrated AP/AR, billing, payroll, and GL on one platform with shared cost pool architecture.
Oracle/SQL Server database foundation provides reliable transaction storage and audit capability.
FedRAMP Moderate designation on GCCM meets federal security baselines required by many government contracts.

Weaknesses

Windows-client interface is dated and significantly slower than modern SaaS ERP alternatives.
Pricing is opaque — no public pricing, no free trial, forcing prospects into a sales cycle before evaluation.
Reporting is powerful but inaccessible — users require specialized training to build and interpret complex queries.
Steep learning curve drives up training and support costs, especially for smaller teams or new hires.
Limited public API documentation constrains custom integrations and modern automation approaches.

Acumatica

Destination

Strengths

Unlimited named-user licensing eliminates per-seat cost scaling as teams grow.
Modular architecture lets companies deploy Financials first and add Distribution, Manufacturing, or CRM incrementally.
Cloud-native with automatic updates removes infrastructure patching and version management from IT responsibilities.
Flexible customization framework (UDFs, extensions) supports vertical-specific workflows without forking core code.
Multi-tenant architecture with CompanyID isolation enables safe data segregation across subsidiaries.

Weaknesses

Steep learning curve and complex initial setup create significant onboarding friction.
Report Designer is widely cited as unintuitive and difficult to use for non-developers.
Feature gaps require customizations or third-party add-ons, adding implementation cost and complexity.
Implementation timelines frequently exceed initial estimates, especially for multi-module deployments.
API rate limits and concurrent session caps are tied to license tier, creating throughput constraints for bulk data operations.

	Deltek Costpoint Source	Acumatica Destination
Strengths	Built-in DCAA compliance with CAS-aligned cost structures and incurred cost submission generation. Multi-level project hierarchy supporting contracts, tasks, and sub-projects with independent billing formulas. Integrated AP/AR, billing, payroll, and GL on one platform with shared cost pool architecture. Oracle/SQL Server database foundation provides reliable transaction storage and audit capability. FedRAMP Moderate designation on GCCM meets federal security baselines required by many government contracts.	Unlimited named-user licensing eliminates per-seat cost scaling as teams grow. Modular architecture lets companies deploy Financials first and add Distribution, Manufacturing, or CRM incrementally. Cloud-native with automatic updates removes infrastructure patching and version management from IT responsibilities. Flexible customization framework (UDFs, extensions) supports vertical-specific workflows without forking core code. Multi-tenant architecture with CompanyID isolation enables safe data segregation across subsidiaries.
Weaknesses	Windows-client interface is dated and significantly slower than modern SaaS ERP alternatives. Pricing is opaque — no public pricing, no free trial, forcing prospects into a sales cycle before evaluation. Reporting is powerful but inaccessible — users require specialized training to build and interpret complex queries. Steep learning curve drives up training and support costs, especially for smaller teams or new hires. Limited public API documentation constrains custom integrations and modern automation approaches.	Steep learning curve and complex initial setup create significant onboarding friction. Report Designer is widely cited as unintuitive and difficult to use for non-developers. Feature gaps require customizations or third-party add-ons, adding implementation cost and complexity. Implementation timelines frequently exceed initial estimates, especially for multi-module deployments. API rate limits and concurrent session caps are tied to license tier, creating throughput constraints for bulk data operations.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Deltek Costpoint to Acumatica

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision