Migrate your Deltek WorkBook data
Agency management platform integrating project management, CRM, resource planning, and full financial accounting for mid-to-large creative and professional services firms.
In its favor
Why people choose Deltek WorkBook
The signal that keeps Deltek WorkBook on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
All-in-one agency ERP eliminating separate systems for project management, time tracking, resource planning, and finance — customers consolidate CRM, PM, and accounting into a single platform.
Implementation team provides hands-on onboarding and customisation, with documented go-lives as short as three weeks for mid-market agencies.
Built-in resource scheduling with worker skills, availability, and utilisation views helps agencies balance capacity against demand in real time.
Agency-specific pipeline management converts leads to projects with integrated budgeting, reducing handoff friction between sales and delivery teams.
Comprehensive finance stack — full AR/AP, multi-currency, inter-company transactions, and subscription billing — means billing errors decrease and profitability visibility improves.
Non-intuitive interface and steep learning curve create adoption friction, especially for non-technical team members unfamiliar with dense project-based ERP systems.
Limited custom reporting, particularly in the finance module, frustrates finance leads who need tailored financial statements and profitability views.
Regular users experience information overload due to the breadth of the platform — multiple modules, dashboards, and configuration options without guided workflows.
Occasional Danish words appearing in the English interface signal localisation inconsistencies that erode confidence in multi-language deployments.
Dashboards and the mobile expense app have been described as not production-ready by reviewers, leading teams to use workarounds for reporting and field expenses.
Reasons to switch
Why people leave Deltek WorkBook
The recurring reasons buyers give for replacing Deltek WorkBook. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Deltek WorkBook fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Deltek WorkBook pricing overview
Deltek WorkBook does not publish pricing publicly. Quotes are issued per organisation based on user count, feature tier, and contract length. Mid-market agencies with 50–200 users typically see quotes in the range of $30–50/user/month on annual plans, but exact pricing requires engaging a Deltek sales representative.
Core
Tier 1 of 4
Custom quote (per user/month, annual)
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Deltek WorkBook's schedule — see our quote-based pricing →
What gets migrated
Deltek WorkBook object support
Object-by-object support for Deltek WorkBook migrations. Per-pair details surface during scoping.
Projects
Fully supportedProjects are the primary container in WorkBook, linking Tasks, Resources, Time, and Finance. We migrate Projects 1:1 including status, dates, budget, and linked custom Dimensions. Project templates export as standard Projects and require re-linkage in the destination.
Tasks
Fully supportedTasks support Kanban board and calendar views natively. We preserve task hierarchy, assignees, due dates, and status. Subtask relationships map as child Tasks with a parent reference. Custom task fields migrate as standard key-value pairs.
Pipeline Stages
Mapping requiredPipeline stages and CRM pipeline data use a stage-based model in WorkBook. Stage names, order, and win/loss probability percentages vary by organisation. We map each stage to an equivalent destination stage and flag any probability overrides for review.
CRM Contacts
Fully supportedContacts in the CRM module are distinct from project stakeholders. We migrate Contacts including company linkage, lifecycle stage, and custom fields. Contact-to-Company associations must be preserved to maintain relationship data integrity.
CRM Companies
Fully supportedCompanies/Accounts represent client organisations in the CRM. We migrate company records with industry, size, address, and linked Contact associations. Multi-company configurations in WorkBook require careful tenant-level scoping during migration.
Time Entries
Fully supportedTime entries link to Projects and Tasks with hourly rates, billing status, and date. We map billable vs non-billable flags and preserve the approved/pending status. Historical time entries carry audit context that we retain where the destination schema allows.
Expenses
Fully supportedExpenses include mileage, material, and personal expense categories with receipt attachments. We migrate expense records with project linkage, reimbursement status, and approval workflow flags. Receipt files are exported separately and re-attached in the destination.
Purchase Orders
Fully supportedPurchase Orders are tied to Projects and track vendor commitments. We migrate open and historical PO records including line items, amounts, and status. Closed POs migrate as read-only historical records.
Invoices / Accounts Receivable
Fully supportedInvoices are generated from time, expenses, and fixed fees against a Project. We migrate invoice records including line items, payment status, and age. AR balance ageing data is preserved as a snapshot at migration time.
Chart of Accounts
Mapping requiredWorkBook's Chart of Accounts includes 21 built-in Dimensions and up to 10 custom Dimensions. Account codes, names, and dimension tags require field-level mapping to the destination's account structure. Inter-company and multi-currency settings must be explicitly carried over.
Resources / Workers
Fully supportedWorkers represent team members with skills, availability calendars, and utilisation data. We migrate resource profiles including skill tags, capacity settings, and booking assignments. Active vs archived status determines whether a resource record is live or deactivated at destination.
Custom Fields / Dimensions
Mapping requiredWorkBook supports 21 built-in Dimensions and up to 10 custom Dimensions per organisation. Custom field names, data types, and picklist values require manual mapping to destination custom fields. We flag any custom fields with no direct destination equivalent for customer resolution.
Attachments / Documents
Mapping requiredFiles saved to Projects, Tasks, or Companies export via WorkBook's file storage. We extract file metadata and binary content and re-attach to the corresponding destination record. Large file volumes may require chunked download and upload cycles.
System and Company Variables
Mapping requiredSystem Variables and Company Variables control global settings, numbering sequences, and configuration flags. We export these as a structured settings bundle and flag any that reference deprecated or version-specific IDs for manual review before import.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Projects are the primary container in WorkBook, linking Tasks, Resources, Time, and Finance. We migrate Projects 1:1 including status, dates, budget, and linked custom Dimensions. Project templates export as standard Projects and require re-linkage in the destination. |
| Tasks | Fully supported | Tasks support Kanban board and calendar views natively. We preserve task hierarchy, assignees, due dates, and status. Subtask relationships map as child Tasks with a parent reference. Custom task fields migrate as standard key-value pairs. |
| Pipeline Stages | Mapping required | Pipeline stages and CRM pipeline data use a stage-based model in WorkBook. Stage names, order, and win/loss probability percentages vary by organisation. We map each stage to an equivalent destination stage and flag any probability overrides for review. |
| CRM Contacts | Fully supported | Contacts in the CRM module are distinct from project stakeholders. We migrate Contacts including company linkage, lifecycle stage, and custom fields. Contact-to-Company associations must be preserved to maintain relationship data integrity. |
| CRM Companies | Fully supported | Companies/Accounts represent client organisations in the CRM. We migrate company records with industry, size, address, and linked Contact associations. Multi-company configurations in WorkBook require careful tenant-level scoping during migration. |
| Time Entries | Fully supported | Time entries link to Projects and Tasks with hourly rates, billing status, and date. We map billable vs non-billable flags and preserve the approved/pending status. Historical time entries carry audit context that we retain where the destination schema allows. |
| Expenses | Fully supported | Expenses include mileage, material, and personal expense categories with receipt attachments. We migrate expense records with project linkage, reimbursement status, and approval workflow flags. Receipt files are exported separately and re-attached in the destination. |
| Purchase Orders | Fully supported | Purchase Orders are tied to Projects and track vendor commitments. We migrate open and historical PO records including line items, amounts, and status. Closed POs migrate as read-only historical records. |
| Invoices / Accounts Receivable | Fully supported | Invoices are generated from time, expenses, and fixed fees against a Project. We migrate invoice records including line items, payment status, and age. AR balance ageing data is preserved as a snapshot at migration time. |
| Chart of Accounts | Mapping required | WorkBook's Chart of Accounts includes 21 built-in Dimensions and up to 10 custom Dimensions. Account codes, names, and dimension tags require field-level mapping to the destination's account structure. Inter-company and multi-currency settings must be explicitly carried over. |
| Resources / Workers | Fully supported | Workers represent team members with skills, availability calendars, and utilisation data. We migrate resource profiles including skill tags, capacity settings, and booking assignments. Active vs archived status determines whether a resource record is live or deactivated at destination. |
| Custom Fields / Dimensions | Mapping required | WorkBook supports 21 built-in Dimensions and up to 10 custom Dimensions per organisation. Custom field names, data types, and picklist values require manual mapping to destination custom fields. We flag any custom fields with no direct destination equivalent for customer resolution. |
| Attachments / Documents | Mapping required | Files saved to Projects, Tasks, or Companies export via WorkBook's file storage. We extract file metadata and binary content and re-attach to the corresponding destination record. Large file volumes may require chunked download and upload cycles. |
| System and Company Variables | Mapping required | System Variables and Company Variables control global settings, numbering sequences, and configuration flags. We export these as a structured settings bundle and flag any that reference deprecated or version-specific IDs for manual review before import. |
Gotchas
What to watch for in Deltek WorkBook migrations
Issues we've hit on past Deltek WorkBook migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
WorkBook REST API is versioned with deprecation cycles
Data Export requires Finance & Administration access
System Variables and Company Variables are not migrated automatically
21 built-in Dimensions plus 10 custom ones require explicit mapping
| Severity | Issue |
|---|---|
| High | WorkBook REST API is versioned with deprecation cycles |
| Medium | Data Export requires Finance & Administration access |
| Medium | System Variables and Company Variables are not migrated automatically |
| Low | 21 built-in Dimensions plus 10 custom ones require explicit mapping |
Leaving Deltek WorkBook?
Where Deltek WorkBook customers move next
5 destinations Deltek WorkBook can migrate to.
How a Deltek WorkBook migration works
Four steps, Deltek WorkBook-specific
Connect
Bearer token (API key-based authentication via Access Roles) into Deltek WorkBook. Scopes limited to read-only on the data we move.
Map
We translate Deltek WorkBook-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Deltek WorkBook quirks before production.
Migrate
Full migration with Deltek WorkBook rate-limit handling. Rollback available throughout.
FAQ
Deltek WorkBook migration FAQ
Answers to the questions buyers ask most during Deltek WorkBook migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Deltek WorkBook migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate Deltek WorkBook.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Deltek WorkBook setup and destination — written quote back within a business day.