ERP migration
Field-level mapping, validation, and rollback between Deltek Costpoint and Microsoft Dynamics 365 Business Central. We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Business Central.
Deltek Costpoint
Source
Microsoft Dynamics 365 Business Central
Destination
Compatibility
16 of 17
objects map 1:1 between Deltek Costpoint and Microsoft Dynamics 365 Business Central.
Complexity
BStandard
Timeline
6-10 weeks
Overview
Moving from Deltek Costpoint to Microsoft Dynamics 365 is a project-accounting platform switch that requires careful sequencing of financial and employee data across two architecturally different ERP systems. Costpoint organizes work around Organizations, Projects with multi-level hierarchies, and a Chart of Accounts with cost pools and burden schedules; D365 separates legal entities into Business Units, organizes projects under Projects, and maps cost pools to Financial Dimensions and Cost Objects in the cost management module. We extract from Costpoint's SQL Server or Oracle-backed schema (with Oracle-to-SQL Server conversion handled separately if needed), preserve the gross/net billing method flag on every AR record that determines how receivables post at billing versus cash receipt, and map Labor Categories and burden schedules to D365 cost categories and cost object hierarchies. DCAA compliance controls, FAR/DFARS billing workflows, and workflow routing tables do not migrate; we deliver a written inventory of DCAA-required controls and routing rules for the customer's admin to rebuild in D365 Project Operations or the appropriate compliance module. Time and Expense entries preserve the DCAA approval chain metadata, and GL journal entries are sequenced by posting date to maintain period integrity in the destination.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Deltek Costpoint platform overview
Scorecard, SWOT, gotchas, and pricing for Deltek Costpoint.
Destination platform
Microsoft Dynamics 365 Business Central platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Business Central.
Data migration guide
The complete Dynamics 365 Business Central migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Dynamics 365 Business Central migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Business Central.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Deltek Costpoint object lands in Microsoft Dynamics 365 Business Central, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Deltek Costpoint
Organization
Microsoft Dynamics 365 Business Central
Legal Entity / Business Unit
1:1Costpoint Organizations represent legal entities or business units that drive billing, HR, and GL assignments. We map Organization hierarchies 1:1 to D365 Legal Entities under Organization Administration. Each Legal Entity requires its own fiscal calendar, chart of accounts, and posting profile configuration. Multi-entity migrations require separate legal entity setup in D365 before any sub-module data imports begin.
Deltek Costpoint
Project
Microsoft Dynamics 365 Business Central
Project
1:1Costpoint Projects are the core work container linked to contracts, billing formulas, labor categories, and budgets. We preserve the full project tree including sub-projects, project status, contract type (Cost-Plus, T&M, Fixed-Price), and the project-to-Organization ownership relationship. Inactive projects flag as On Hold or Closed in D365. CLIN/SLIN structures from government contracts map to D365 contract lines or project contract billing breakdowns.
Deltek Costpoint
Chart of Accounts
Microsoft Dynamics 365 Business Central
Main Account + Financial Dimensions
lossyCostpoint's GL Chart of Accounts includes direct cost accounts, indirect cost pools (G&A, Fringe, Overhead), and burden schedules. We map each Costpoint account to a D365 Main Account with the account type (Expense, Revenue, Balance Sheet) preserved, and indirect cost pools map to Financial Dimension sets (typically Department, Cost Center, Project). Burden schedules require mapping to D365 cost groups and cost categories that feed into project cost calculations.
Deltek Costpoint
Employee
Microsoft Dynamics 365 Business Central
Worker
1:1Costpoint Employee records include compensation history, HR organization assignments, labor category assignments, and DCAA-required timesheet metadata (supervisor approval, labor distribution). We extract all effective-dated compensation rows and map them to D365 Human Resources Worker records with employment details, labor union flags, and pay frequency. DCAA timesheet approval chain metadata migrates as a custom field or note for compliance reconstruction in D365.
Deltek Costpoint
General Ledger Journal Entry
Microsoft Dynamics 365 Business Central
General Ledger Entry (LedgerJournalTable / LedgerJournalTrans)
1:1Historical GL entries in Costpoint carry source module attribution (billing, payroll, AP, AR), posting date, fiscal period, and debit/credit structure. We extract entries by date range and map them to D365 General Journal lines with the correct Main Account, Financial Dimensions, and Debit/Credit amounts. Period integrity is preserved by mapping to the corresponding D365 fiscal period. Organizations with multi-entity GL require separate journal batches per legal entity.
Deltek Costpoint
Accounts Payable Invoice
Microsoft Dynamics 365 Business Central
Vendor Invoice / LedgerJournalTrans (Vendor)
1:1Costpoint AP records include vendor invoices, payment terms, and check/EFT batch data. We map vendor invoices to D365 Vendor Invoice lines with vendor number resolved to the destination vendor master, account distribution mapped to D365 Main Account and Financial Dimensions, and payment terms preserved. Open AP (unpaid invoices) and historical paid invoices are separable export sets; we recommend migrating open AP only with historical available for on-demand query.
Deltek Costpoint
Accounts Receivable Invoice
Microsoft Dynamics 365 Business Central
Customer Invoice / LedgerJournalTrans (Customer)
1:1Costpoint AR records track billed and unbilled amounts linked to Projects and CLIN/SLIN structures. The gross/net billing method flag on the invoice header must be preserved during migration because it changes how the GL posts at billing versus cash receipt. We extract this flag per invoice and set the D365 posting profile accordingly. Unbilled revenue (Open Billing Detail) maps to D365 Revenue Recognition or Work In Progress lines depending on the contract type.
Deltek Costpoint
Open Billing Detail
Microsoft Dynamics 365 Business Central
Project Invoice Proposal Line / Revenue Recognition Line
1:1Open Billing Detail records in Costpoint store the transaction-level detail that feeds billing formulas (cost-based, hours-based, units-based). These records are cross-linked to project hierarchies and labor categories. We export by project and map unbilled amounts to D365 Project invoice proposals or revenue lines, preserving the billing formula type and any fee override or ceiling controls configured in Costpoint.
Deltek Costpoint
Vendor
Microsoft Dynamics 365 Business Central
Vendor (AccountPayableVendorFacade)
1:1Costpoint Vendor records include address, tax ID, payment terms, and W-9 status. We extract all active vendors and map to the D365 vendor master, preserving ACH routing details for payment continuity. Vendor-to-Organization assignments map to D365 Business Unit assignments on the vendor record. Inactive vendors are excluded from the active migration but listed in a reconciliation report.
Deltek Costpoint
Customer / Bill To
Microsoft Dynamics 365 Business Central
Customer (AccountReceivableCustomerFacade)
1:1Costpoint Customer/Bill-To records (distinct from AR invoices) map to D365 Customer records with address, payment terms, and invoice profile. Customer-to-Project assignments are preserved as D365 project customer associations. If Costpoint stores separate Ship-To addresses, these migrate as D365 delivery addresses on the Customer record.
Deltek Costpoint
Fixed Asset
Microsoft Dynamics 365 Business Central
Fixed Asset
1:1Costpoint Fixed Asset records include acquisition costs, depreciation schedules, funding sources, and asset classifications. We map asset books to D365 depreciation calendars with depreciation method, useful life, and salvage value preserved. Any DCAA-compliant depreciation treatment (e.g., award fee asset capitalization) is flagged for manual configuration review in D365 Fixed Asset parameters.
Deltek Costpoint
Inventory Item
Microsoft Dynamics 365 Business Central
Released Product / Item Model Group
1:1Costpoint supports project-specific and warehouse inventory with multi-project traceability. We export item masters, on-hand quantities, and cost layers, flagging any lot or serial number tracking for D365 inventory dimension configuration. Item costing (Standard, FIFO, Moving Average) migrates from Costpoint item cost setup to D365 item model groups and cost price groups.
Deltek Costpoint
Department / Cost Center
Microsoft Dynamics 365 Business Central
Department / Cost Center (Financial Dimension)
1:1Departments in Costpoint drive organizational cost collection and are linked to GL segments. We map department hierarchies 1:1 to D365 Financial Dimensions of type Department, preserving the department-to-account assignments that feed indirect cost pool allocations. Cost center assignments on Projects migrate to D365 Project dimensions.
Deltek Costpoint
Time and Expense Entry
Microsoft Dynamics 365 Business Central
Project Time Transaction / Expense Report
1:1Costpoint timesheet and expense report records include employee, project, labor category, and billing status. We export submitted and approved entries by date range, preserving the DCAA-required approval chain metadata (approver, approval date, labor distribution). Entries map to D365 Project Time and Material lines or Expense reports under the Project module. Unsubmitted or rejected entries are excluded from migration.
Deltek Costpoint
Labor Category (General)
Microsoft Dynamics 365 Business Central
Cost Category
1:1Costpoint General Labor Categories (UDT06 to CP GENL_LAB_CAT) define billing and cost rates per labor type. We map these to D365 Cost Categories that feed into project billing formulas and resource cost calculations. Project Labor Categories (UDT07 to CP BIL_LAB_CAT) map to D365 Project Labor Categories with billing rate overrides preserved per project.
Deltek Costpoint
Custom Field (Project, Employee, Vendor, Transaction)
Microsoft Dynamics 365 Business Central
Custom Field / Extension
1:1Costpoint user-defined custom fields on Projects, Employees, Vendors, or Transactions are stored as separate database table extensions and must be enumerated explicitly during discovery. We determine which custom fields are business-critical versus cosmetic, configure custom field extraction as a parallel export, and map to D365 custom fields on the corresponding entity. Fields without a clear D365 equivalent are flagged for the customer to configure as extension fields or custom entities.
Deltek Costpoint
Workflow System Tables
Microsoft Dynamics 365 Business Central
N/A (not migrated)
1:1Costpoint Workflow Toolkit tables (WFPTOOL) are environment-specific and rebuilt during every Costpoint upgrade. These tables contain routing logic tied to the current version's schema and cannot be meaningfully migrated to D365. We document the workflow routing rules (approver assignments, step sequences, delegation rules) as part of migration scoping and deliver a written workflow inventory for the customer to rebuild in D365 Power Automate or the appropriate workflow module post-migration.
| Deltek Costpoint | Microsoft Dynamics 365 Business Central | Compatibility | |
|---|---|---|---|
| Organization | Legal Entity / Business Unit1:1 | Fully supported | |
| Project | Project1:1 | Fully supported | |
| Chart of Accounts | Main Account + Financial Dimensionslossy | Fully supported | |
| Employee | Worker1:1 | Fully supported | |
| General Ledger Journal Entry | General Ledger Entry (LedgerJournalTable / LedgerJournalTrans)1:1 | Fully supported | |
| Accounts Payable Invoice | Vendor Invoice / LedgerJournalTrans (Vendor)1:1 | Fully supported | |
| Accounts Receivable Invoice | Customer Invoice / LedgerJournalTrans (Customer)1:1 | Fully supported | |
| Open Billing Detail | Project Invoice Proposal Line / Revenue Recognition Line1:1 | Fully supported | |
| Vendor | Vendor (AccountPayableVendorFacade)1:1 | Fully supported | |
| Customer / Bill To | Customer (AccountReceivableCustomerFacade)1:1 | Fully supported | |
| Fixed Asset | Fixed Asset1:1 | Fully supported | |
| Inventory Item | Released Product / Item Model Group1:1 | Fully supported | |
| Department / Cost Center | Department / Cost Center (Financial Dimension)1:1 | Fully supported | |
| Time and Expense Entry | Project Time Transaction / Expense Report1:1 | Fully supported | |
| Labor Category (General) | Cost Category1:1 | Fully supported | |
| Custom Field (Project, Employee, Vendor, Transaction) | Custom Field / Extension1:1 | Fully supported | |
| Workflow System Tables | N/A (not migrated)1:1 | Not supported |
Gotchas + challenges
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
Oracle-to-SQL Server database conversion required for on-premise migrations
Gross vs. net billing method is embedded at the invoice header level
Custom fields require explicit enumeration and configuration
Workflow tables are upgrade-specific and cannot be migrated
Version parity between source and destination is mandatory for cloud migrations
Microsoft Dynamics 365 Business Central gotchas
Named-user licensing has no concurrent-use relief
API rate limits throttle large-volume migrations
Historical posted transactions require selective migration scoping
NAV-to-Business Central cloud migration requires partner coordination
Custom fields and AL extensions require separate migration handling
Pair-specific challenges
Migration approach
Discovery and architecture assessment
We audit the source Costpoint environment including version, deployment model (on-premise Oracle/SQL Server or GCCM cloud), Organizations, project count, GL account structure, open/closed AR and AP volume, fixed asset count, employee headcount, custom field inventory, and active workflow routing rules. We pair this with a D365 destination assessment: Finance, Supply Chain Management, or Business Central; Government Community Cloud requirement; organizational structure (single or multi-entity); and existing D365 licensing. The discovery output is a written migration scope with object inventory, volume estimates, and a D365 edition recommendation.
Schema design and legal entity configuration
We design the destination D365 schema based on the Costpoint chart of accounts structure. This includes provisioning Main Accounts with correct account types, Financial Dimension sets (Department, Cost Center, Project), Cost Categories for labor and burden mapping, Vendor and Customer masters with payment terms, and Project types aligned to Costpoint contract types. Multi-entity migrations require separate Legal Entity setup per Costpoint Organization before any sub-module data is loaded. We deploy the schema to a D365 Sandbox environment for validation.
Sandbox migration and reconciliation
We run a full migration into the D365 Sandbox using production-equivalent data volumes. The customer's finance lead reconciles GL balances (total debits equals total credits per period), account-level balances against Costpoint trial balance, open AR aging, open AP aging, and project billing totals. We spot-check 25-50 random records across each object type against the Costpoint source. The customer signs off on the sandbox results before production migration begins. Any mapping corrections, missing financial dimensions, or posting profile issues surface here.
Master data migration in dependency order
We migrate master data in dependency sequence: Legal Entities and Fiscal Calendars (prerequisite for all other data), Main Accounts and Financial Dimensions, Departments and Cost Centers, Cost Categories and Labor Categories, Vendors, Customers, Fixed Assets, Employees/Workers, and finally Projects with billing formula configuration. Each phase emits a row-count reconciliation report and balance verification before the next phase begins. GL journal entries run last in master data because they reference all other entities.
Transaction migration and billing flag preservation
We migrate open AP invoices, open AR invoices with the gross/net billing flag extracted and set on the D365 posting profile, open billing detail, and time and expense entries with approval chain metadata. Historical GL journal entries migrate by fiscal period with source module attribution preserved for audit. We flag any transaction with a missing parent reference (orphan records) for customer resolution before production cutover.
Cutover, validation, and workflow handoff
We freeze Costpoint writes during cutover, run a final delta migration of any records modified during the migration window, then validate D365 as the system of record. We deliver the DCAA compliance control inventory, workflow routing rule documentation, and custom field handoff list to the customer's admin team. We support a one-week hypercare window for reconciliation issues. We do not rebuild Costpoint workflows, billing formulas, or compliance controls in D365 inside the migration scope; those are separate configuration engagements.
Platform deep dives
Deltek Costpoint
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Business Central
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between Deltek Costpoint and Microsoft Dynamics 365 Business Central.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Deltek Costpoint and Microsoft Dynamics 365 Business Central.
Object compatibility
All 8 core objects map 1:1 between Deltek Costpoint and Microsoft Dynamics 365 Business Central.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Deltek Costpoint: Not publicly documented for Costpoint specifically.
Data volume sensitivity
Deltek Costpoint doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Deltek Costpoint to Microsoft Dynamics 365 Business Central migration scoping. Not seeing yours? Book a call.
Walk through your Deltek Costpoint to Microsoft Dynamics 365 Business Central migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Deltek Costpoint
Other ways to arrive at Microsoft Dynamics 365 Business Central
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.