Migrate from Deltek WorkBook to Jira

WorkBook Projects map 1:1 to Jira Projects. Each WorkBook Project name, status, start date, end date, and description transfer to the Jira Project metadata. Project templates in WorkBook do not migrate as templates; we document the template structure for the customer's admin to recreate as Jira Project templates post-migration.

WorkBook Tasks map 1:1 to Jira Issues (typically Story or Task issue types depending on the customer's scoping). We preserve task hierarchy by creating Jira child Issues with a parent link, assignees via email-to-Jira-user resolution, due dates, and status. WorkBook's custom task fields map to Jira custom fields of matching type (text, date, picklist, number). Subtasks map as child Issues with the parent relationship maintained.

WorkBook Workers (team members with skills, availability, and capacity data) map to Jira User accounts by email lookup. WorkBook skill tags and capacity settings do not have Jira equivalents; we preserve skill data as Jira user properties or a custom Jira user picker field and document the original WorkBook capacity values for the customer's resource manager to reference. Archived Workers migrate as inactive Jira users if historical task assignment matters.

WorkBook's 21 built-in Dimensions and 10 custom Dimensions require explicit mapping to Jira custom fields because Jira uses a flat custom field model with no dimensional tagging. Multi-value Dimensions (tags on a single transaction) map to Jira multi-select custom fields; single-value Dimensions map to single-select or text fields. We present a dimension-mapping matrix to the customer during scoping before committing to the plan.

WorkBook CRM Contacts are people records outside the project context. Jira does not have a native CRM; contacts that are project stakeholders (external collaborators, clients) can be added as Jira users with external access or captured as part of the Issue description/comment history. Contact lifecycle stages and CRM custom fields have no Jira equivalent and are flagged for manual capture.

WorkBook CRM Companies have no Jira equivalent. We can tag Jira Issues with the Company name as a Label (for filtering) or add the company name to the Project description, but the full company record (industry, size, address, revenue) does not migrate. The customer receives a CSV export of all CRM Companies for manual CRM re-entry in a dedicated tool if needed.

WorkBook Pipeline stages with win/loss probability percentages map to Jira Issue statuses within a configured Workflow. We create Jira statuses that correspond to WorkBook pipeline stages and configure the Workflow transitions. Probability percentages are documented for the customer's admin to rebuild in Jira's native reporting or a third-party plugin.

WorkBook Time Entries (linked to Projects and Tasks with billable/non-billable flags, hourly rates, and dates) map to Jira Issue Worklogs. Billable flag maps to Jira's worklog visibility setting. Approved/pending status from WorkBook is preserved as a custom worklog field. Jira does not support hourly rate billing per worklog; rate data is documented for the customer's finance team to reconcile externally.

WorkBook Expenses (mileage, material, personal categories with receipt attachments) have no Jira equivalent. Receipt binary files can be extracted and attached to the relevant Jira Issue manually or via file storage migration, but the expense record structure (category, reimbursement status, approval workflow) does not map. We deliver a structured CSV export of all expense records for the customer's finance team to process in their preferred expense management tool.

WorkBook's full financial stack has no Jira equivalent. Jira is not an accounting system. We do not migrate the Chart of Accounts, invoice records, purchase order records, accounts payable/receivable data, or journal entries. We deliver a written inventory of all financial record types present in the WorkBook instance with record counts and recommended alternatives (dedicated accounting software, spreadsheet export, or ERP re-implementation) so the customer's finance team can plan the financial data separately.

WorkBook System and Company Variables control numbering sequences, workflow flags, and integration settings. These are not standard data records and cannot migrate to Jira. We extract these as a structured JSON settings bundle, flag any variables that reference IDs no longer present post-migration, and hand the bundle to the customer for manual review. Jira's project settings and issue schemes replace some configuration but require manual rebuild.