Migrate from Teamwork.com to monday Work Management

Teamwork Projects map 1:1 to monday.com Boards with the Project name becoming the Board title and Project status (Active, On Hold, Completed) mapped to a Status column on the Board. Project start and end dates migrate as date filters on the Board timeline or as column values in a Date column. We create one Board per Teamwork Project. Project-level custom fields (Premium-only on Teamwork) map to monday.com column equivalents by type, but only if the source account held an active Premium-equivalent subscription during extraction; we verify this during scoping.

Teamwork Task Lists map directly to monday.com Groups within the target Board. The Task List name becomes the Group name, and Group-level ordering within the Board is preserved. Task Lists with their own milestones carry those milestone dates as group-level Date columns in the destination. If a Teamwork project has more than 20 groups, we split across multiple Boards or use monday's Folder structure for organization.

Teamwork Tasks map 1:1 to monday.com Items within their corresponding Group. Task name becomes Item name, due date maps to a Date column, assignee maps to Person column, priority maps to a Status or Labels column, estimated time maps to a Numbers or Workload column, and description maps to the Item's text body. We preserve the full task hierarchy by referencing the parent task ID as an Item relation column for cross-group dependencies.

Teamwork Subtasks map to monday.com Subitems on Items, but Subitems are gated behind monday.com Standard and Pro plans. During scoping we verify the destination account's plan tier; if the account is on a Basic or Free plan we recreate Subtasks as separate Items within the same Group and reference them via a dependency relation. We preserve subtask assignees, due dates, and completion status. Note that Teamwork's non-cascading parent completion behavior is replicated in monday.com by setting Subitems as independently-complete records.

Teamwork Milestones are date-driven project markers. We map milestone names to a dedicated Labels or Status column value, and milestone dates to a Date column filtered to the milestone date. For projects using the Timeline column in monday, we create timeline entries representing milestone dates as single-day ranges with the milestone name as the label. Linked task associations from Teamwork milestones are preserved as Item relation entries or notes on the milestone record.

Time entries are first-class records in Teamwork.com linked to Tasks or Projects with billable/non-billable flags, hourly rates, and durations. monday.com has no native equivalent that supports billable rates and client budget visibility simultaneously. We map time entry data as follows: duration maps to a Numbers column (hours as decimal), date maps to a Date column, billable flag maps to a Labels or Status column (Billable / Non-Billable), and hourly rate maps to a Numbers column. For clients that rely on client-facing budget transparency, we create a Workdoc per project capturing the time summary table for manual sharing. We flag this gap as a high-severity gotcha for any customer using recurring support budgets.

Teamwork Clients are top-level entities owning multiple Projects with associated contact info and client portal access. We map Client records to monday.com Contacts (available on Standard and Pro plans) or Guest user profiles. Client contact info (name, email, phone) maps to the Contact's name and email fields. Client-level billing rates are preserved as Numbers columns on the Contact record. Client portal visibility for budget tracking does not have a direct monday.com equivalent; we document the workaround using shared Workdocs.

Teamwork Custom Fields exist at both project and site-wide levels with dropdown, text, number, date, and checkbox types. We read all custom field definitions via the Teamwork V3 API (V2 required for custom field reads), preserve the options array for dropdown types, and map them to equivalent monday.com column types: dropdown options map to monday Labels or Dropdown columns, dates map to Date columns, numbers map to Numbers columns, and checkboxes map to Checkbox columns. Project-level and site-wide fields are merged before writing to prevent duplication. Custom Fields require Teamwork Premium on the source; if the subscription tier does not support them, we document the field definitions for manual recreation.

Teamwork Tags are simple string labels applied across Projects and Tasks. We preserve tag names and apply them as monday.com Labels on the corresponding Items. monday Labels are flat tags without hierarchy, matching Teamwork's tag model directly. Tag color assignments from Teamwork map to Label color options in monday.com where applicable.

Teamwork Comments attach to Tasks with author attribution, timestamps, and @mentions. We map comments to monday.com Item Updates preserving the full comment text, author name, and creation timestamp. Threaded replies in Teamwork map as sequential Updates in monday. @mentions are preserved as text references but do not trigger notifications since monday's mention model differs.

Teamwork Attachments on Tasks and Projects carry file name, type, size, and uploader metadata plus the file URL. We extract file URLs and metadata, then create monday.com file attachments on the corresponding Items or Boards. Large binary files may require separate blob migration handling depending on destination storage limits. Inline images in task descriptions are preserved as separate file attachments in monday.

Teamwork Invoices are generated from billable time entries and carry client associations, line items, tax configuration, and payment status. monday.com has no native invoicing or billing object. We export invoice header data (client name, invoice number, date, total amount) and line item summaries as a structured Workdoc per invoice. The customer's accounting team uses this as a reference for reissuing invoices in their accounting tool of record. This is a functional gap that teams relying on Teamwork's invoicing must address outside the monday.com platform.