Migrate from Work as Team to monday Work Management

Work as Team Projects map directly to monday.com Boards. The project name, description, start date, and end date transfer to the board name, description, and Timeline span respectively. We use monday.com's Board API to create the board structure before any items are imported. Project-level status (Active, Completed, Archived) maps to the board's archive state or a status Group label.

Work as Team Lists are a top-level structural container with no direct monday.com equivalent. We map each List to a monday.com Group within the destination Board, preserving List order as Group sequence. List-level permissions (if any restricted Lists exist) cannot map natively to Group-level permissions in monday.com; we document these as an access-gap requiring admin redesign post-migration.

Work as Team Tasks map to monday.com Items. Task name becomes Item name; description migrates to the Text column; due date maps to the Date column; priority maps to the Priority column; assignee maps to the Person column. Subtasks in Teamwork map to Subitems in monday.com if the destination plan supports Subitems (Standard and above). We resolve the parent-task reference during import so that subtask hierarchy is preserved.

Work as Team Milestones are date-bound markers on a project timeline. We map them to monday.com Timeline columns spanning the milestone date, or to a Status label (e.g., 'Milestone Reached') on the relevant Item, depending on how the customer uses milestones. If Teamwork milestones have dependencies, we document those as a prerequisite list for the customer's admin to rebuild using monday.com's dependency column post-migration.

Work as Team time entries with log date, duration, billable flag, and notes map to monday.com's Time Tracking column on Pro plans and above. For customers on monday.com Standard (no native time tracking), we migrate time-entry data into a numeric Duration column and a Text notes column as structured records, flagging that the destination plan lacks time-tracking and a rebuild decision is needed. Time entries without a linked task are stored as board-level notes for admin review.

Work as Team team members map to monday.com Workspace members by email match. Role (Admin, Member, Guest) maps to monday.com permission levels. Any Work as Team team member without a matching monday.com account goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Work as Team tags stored at the task level migrate to monday.com Labels on the equivalent Items. Label color and name are preserved. If a Work as Team task has multiple tags, each tag becomes a separate Label on the monday.com Item.

Work as Team task statuses (Not Started, In Progress, Waiting, Deferred, Completed, etc.) map to monday.com Status column values. We create custom Status labels in monday.com that match the source status names and colors during migration setup. The customer confirms the mapping during scoping, as status sets vary by Work as Team project template.

Work as Team file attachments linked to tasks migrate to monday.com File column values. We download each file, upload it to the destination board's file storage, and link it to the corresponding Item. Files without a parent task are stored in a board-level Documents section. Note: Work as Team's client portal file-sharing permissions do not migrate; we document the file-access gap separately.

Work as Team task comments migrate to monday.com Updates on the equivalent Items. Comment author maps to the monday.com update author; comment body and timestamp are preserved. Comment threading in Work as Team (replies to comments) is flattened in monday.com because Updates do not have a native reply structure.

Work as Team custom fields (text, number, date, checkbox, dropdown, currency, URL) map to equivalent monday.com column types. We create the destination column in each board before import and preserve the field name. Dropdown options in Work as Team map to monday.com Dropdown or Status column options. Any custom field type with no direct monday.com equivalent (e.g., Work as Team's formula fields) is documented as a gap for manual re-creation.

If the Work as Team account includes the CRM module with Companies, we map them to a dedicated monday.com Board (for standalone company records) or to Contact items linked via a Connect Boards column, depending on whether the customer uses monday.com's Contacts integration. Company name, website, phone, and address fields migrate to equivalent text columns.

Work as Team invoices and billing records do not have a migration path to monday.com. monday.com has no native invoicing or billing module in its Work Management product. We extract invoice records as a CSV export for the customer's finance team to review and do not load them into monday.com. If the customer needs billing tracking in monday.com, we document it as a separate board-building exercise.

Work as Team project templates are not migrated as reusable templates in monday.com. monday.com's own template library (200+ templates) serves as the starting point. We deliver a written map of the source template structure (Lists, task fields, status sets, milestones, default assignees) so that the customer's monday.com admin can manually build equivalent templates using monday.com's duplicate-board feature if desired.

Work as Team's native Client Portal with granular project-level permissions, client-specific views, and file sharing has no direct monday.com equivalent. We map the portal-accessible projects to monday.com boards with Guest seat provisioning (available on Standard and above). Client-specific views map to board filters or saved views. We document the access-gap per project so the customer's admin can redesign client visibility in monday.com settings post-migration.