Migrate from Deltek WorkBook to Trello

WorkBook Projects map to Trello Boards. Each WorkBook Project (with its name, status, dates, budget, and description) becomes a Board. We use the Project name as the Board title and the WorkBook project ID stored in a Board custom field as a cross-reference for reconciliation. If the customer uses Project templates in WorkBook, we document the template structure as a Board copy guide for their admin to replicate in Trello.

WorkBook Tasks map to Trello Cards within the appropriate Board. Task name becomes Card title, description maps to Card description, due date maps to the due date field, and assignee resolves to a Board Member. Parent-child Task relationships in WorkBook have no native equivalent in Trello — we represent sub-tasks as Cards with a checklist named 'Sub-tasks' on the parent Card, preserving the hierarchy as a checklist structure rather than a native parent-child record relationship.

WorkBook Pipeline Stages become Trello Lists within a Board. Stage name, order, and win/loss probability percentage migrate to List name, Card position, and a custom field (Probability %) on Cards in that List. Pipeline stages used for CRM opportunities map to a dedicated CRM Board; project task stages map to a separate PM Board. The customer defines the Board-List structure during scoping so we can route the correct stage data to the correct Board.

WorkBook CRM Contacts migrate as Trello Board Members invited to Cards where they are a stakeholder, and as a Contact custom field on Cards storing the contact name, email, and phone. Contact-Company associations are preserved by linking Cards to the Board representing the associated Company, or via a Company custom field on each Card. Multi-address and multi-phone contact records are stored in Card description for reference.

WorkBook Companies map to Trello Cards on a dedicated Company Board, with each Company record as a Card containing company name, industry, address, and size in Card description and custom fields. Alternatively, the Company name becomes a Card Label (with a consistent colour mapping) on Cards linked to that company, and a Company custom field holds the full company name reference. The customer chooses the strategy during scoping.

WorkBook Time Entries (linked to Projects and Tasks with hourly rates, billing status, and date) have no native Trello equivalent. We export time entries as a structured JSON file per Card (referencing the parent WorkBook Task Card) and attach the JSON file to the corresponding Trello Card as a file attachment. Billable vs non-billable flags and approved/pending status are included in the JSON. Customers needing visible time tracking in Trello use a time-tracking Power-Up post-migration.

WorkBook Expense records (with mileage, material, and personal expense categories, receipt attachments, project linkage, and reimbursement status) export as a JSON snapshot attached to the relevant Trello Card. Receipt binary files from WorkBook's file storage are re-attached to the corresponding Card as Card attachments. Trello has no native expense management; customers needing expense tracking post-migration configure a finance Power-Up or use a separate expense tool.

WorkBook Workers (team members with skills, availability calendars, and utilisation data) map to Trello Board Members. We resolve Workers by email address to Trello member accounts. Skill tags, capacity settings, and booking assignments from WorkBook export as a JSON resource profile attached to a Board-level 'Resources' Card or as custom fields on individual Cards. Active vs archived worker status is preserved by Board membership scope.

WorkBook's 21 built-in Dimensions and up to 10 custom Dimensions per organisation require explicit type-mapping to Trello native custom field types. Text dimensions map to Trello text fields; numeric dimensions map to number fields; date dimensions map to Trello date fields; picklist-based dimensions map to dropdown or label fields. A dimension-mapping matrix is presented to the customer during scoping. Free-tier Trello workspaces have limited native custom field support; Standard tier or above is recommended when migration scope includes more than three custom field types.

Files saved to WorkBook Projects, Tasks, or Companies extract via WorkBook's file storage and re-attach to the corresponding Trello Card. We preserve file name, binary content, and original upload date. Large file volumes may require chunking or a file-size pre-check against Trello's per-Board attachment limits. Documents that are not directly task-linked (e.g. org-level policy documents) are attached to a Board-level 'Documents' Card as a reference archive.

WorkBook Invoices (generated from time, expenses, and fixed fees against a Project) have no Trello equivalent. Trello has no native invoice management, billing, or AR tracking. We export invoice records as a structured JSON snapshot including line items, payment status, and age, and deliver this as a written invoice inventory document for the customer's finance team to re-enter manually or migrate to a dedicated accounting tool post-migration.

WorkBook Purchase Orders (tied to Projects with vendor commitments, line items, amounts, and status) have no Trello equivalent. We export open and historical PO records as a JSON snapshot and deliver it as a written PO inventory document. Closed POs migrate as read-only historical records in the document. The customer re-enters active PO data manually or uses a separate procurement tool.

WorkBook's Chart of Accounts with 21 built-in Dimensions and up to 10 custom Dimensions cannot map to Trello, which has no financial accounting schema. We export the full Chart of Accounts and dimension definitions as a structured JSON settings bundle. This bundle is delivered to the customer's finance team for reference if they adopt a dedicated accounting tool alongside Trello. The bundle includes any variables that reference deprecated or migrated IDs, flagged for manual review.

WorkBook System Variables and Company Variables (numbering sequences, workflow flags, and integration settings) export as a structured JSON settings bundle separate from the primary data migration. We flag any variables that reference IDs no longer present post-migration. The bundle is handed to the customer for manual import review; Trello has no native equivalent for system configuration variables.