Migrate from Deltek WorkBook to monday Work Management

WorkBook Projects map directly to monday.com Boards. We preserve Project name as Board name, start/due dates as Board date ranges, project status as a Board-level status column, and budget as a Numbers column. WorkBook project templates map to monday.com Board templates if the customer chooses to create template boards post-migration. Projects without linked tasks migrate as empty Boards that the team populates.

WorkBook Tasks map to monday.com Items within the corresponding Board. Task hierarchy (parent/subtask relationships) migrates as Items with sub-Items or as Items grouped under a parent Item. Assignee, due date, priority, and status migrate as standard monday.com columns (People, Date, Status). Custom task fields map to monday.com column types (Text, Number, Date, Dropdown, etc.) chosen during scoping.

WorkBook Pipeline stages (with win/loss probability percentages) map to Groups on a monday.com CRM Board. Stage names and order migrate; probability percentages do not have a native monday.com field and are stored as a Numbers column or a custom formula column if the customer licenses the Pro plan with formulas. Pipeline convert-to-project rules have no monday.com equivalent and are documented as a manual rebuild item.

WorkBook CRM Contacts migrate to monday.com People entities. Contact name, email, phone, address, lifecycle stage, and any custom fields map to equivalent monday.com Person columns. Contact-to-Company linkage migrates as a relation or Link to Item column if the customer uses monday.com's CRM board structure. WorkBook Contact owner maps to the monday.com team member responsible for the Person.

WorkBook Companies migrate to monday.com Organization records in the CRM Board. Company name, industry, size, address, and custom fields map to Organization column types. Organizations are imported before Contacts so that the Contact-to-Company relationship is satisfied at insert time.

WorkBook Workers with skills, availability calendars, and utilisation data migrate to monday.com Team Members. Skill tags map to Tags columns or custom Dropdown columns. Active worker capacity and utilisation data do not have a native monday.com equivalent; we store utilisation percentages as Numbers columns on a Resource Board that the customer populates manually or via integration. Archived workers migrate as inactive team members or to a separate Archive Board.

WorkBook Time Entries linked to Projects and Tasks map to monday.com Items using the Time Tracking integration (available on Pro and above) or as structured data in custom Number columns for hours and Date columns for date. Billable vs non-billable flags map to a Label column; approved/pending status maps to a Status column. Historical time entry volumes over 50,000 records require batch processing and date-range filtering to stay within monday.com API limits.

WorkBook Expenses migrate to Items on a dedicated Expense Board. Expense categories (mileage, material, personal) map to Group columns; amount, currency, and reimbursement status map to Numbers, Currency, and Status columns. Receipt attachments migrate as file links on the Item. The approval workflow status from WorkBook migrates as a Status column but the actual approval action does not; monday.com Automations can replicate simple approval chains if the customer licenses the required plan.

Open Purchase Orders migrate as Items on a PO Board with vendor name, PO number, line item amounts, and status. Closed POs migrate as read-only historical records with status set to Closed. PO-to-Project linkage migrates as a Link to Item column or a Relation column. Multi-vendor PO structures map to Grouped Items by vendor.

WorkBook Invoices migrate to an Invoice Board as Items with invoice number, client name, line item amounts, payment status, and age data. Payment status (Paid, Overdue, Outstanding) maps to a Status column. Full AR balance ageing data migrates as a snapshot Numbers column. Invoice PDFs do not migrate natively; we extract PDF binary content as file attachments on the corresponding Item where monday.com storage limits permit.

WorkBook's 21 built-in Dimensions plus 10 custom Dimensions have no structural equivalent in monday.com. We create a Financial Board with a structured column layout that represents the most critical Dimension values (Department, Project, Cost Type, Region) as Dropdown or Label columns. The full dimensional mapping is delivered as a structured JSON export and a written Dimension-mapping matrix for the customer to refine in their chosen accounting tool post-migration.

WorkBook System Variables and Company Variables (numbering sequences, workflow flags, integration settings) are extracted as a structured JSON bundle and handed to the customer for manual review. These cannot be imported into monday.com because monday.com has no equivalent configuration store. We flag any variables that reference IDs no longer present post-migration.

Files saved to Projects, Tasks, or Companies in WorkBook are extracted as binary content and re-attached to the corresponding monday.com Item or Board. Large file volumes require pre-migration storage assessment against monday.com's file size limits per plan. Files exceeding the limit are flagged and delivered as a download link document for manual re-upload.