Migrate from Output Time to monday Work Management

Output Time Projects map directly to monday.com Boards. The project name becomes the board name, project description maps to the board description or a long-text column, and project status (Active/Archived) maps to a monday.com Status column. We create one board per project, preserving the project start date and target date as board-level metadata. Workspace assignment in monday.com is determined during scoping based on team or department grouping.

Output Time Tasks map to monday.com Items on the board. Task name becomes item title, description maps to a text column, assignee maps to the People column, due date maps to a Date column, priority maps to a Priority column or Status color-coding, and status maps to a Status column. We preserve the parent project lookup by ensuring all items land on the correct board. Task ordering is maintained based on Output Time's sort sequence.

Output Time Subtasks map to monday.com Subitems attached to their parent Item. Subtask name, description, assignee, due date, and status fields map to equivalent subitem columns. We maintain the parent-child relationship by linking each subitem to its originating item. If the parent item has not yet been created, we hold subitem creation until the parent item is confirmed in the destination.

Output Time time entries (date, duration, billable flag, user, notes) map to monday.com's native time tracking column on Pro plans or to a custom Number column on Standard plans. The date of the entry maps to a Date column, duration in hours maps to the time tracking or number field, and notes map to a text column on the item. We preserve the billable flag as a Checkbox column (is_billable) on each item since not all monday.com column types support a native billable/non-billable distinction.

Output Time Milestones (name, target date, associated project) map to monday.com Items with a Date or Timeline column set to milestone type. We create a dedicated group on each project board for milestones, populate milestone name as the item title, and set the target date on the date or timeline column. Milestone ordering is preserved based on target date sequence.

Output Time Users (name, email, role, project access) map to monday.com Users. We resolve by email match against the monday.com workspace. The customer's admin provisions monday.com users before migration, and we validate that every Output Time owner has a matching monday.com user before record import. Inactive Output Time users are mapped as inactive monday.com users to preserve historical assignment data.

Output Time Client records (name, email, phone, project associations) map to monday.com Contacts or Guest Users depending on whether the customer uses monday.com's CRM boards or a separate contact management system. Client name becomes the contact name, email maps to the email column, and project associations are preserved as a text column listing linked project names. We flag any client without an email address for manual review.

Output Time custom fields (key-value pairs stored without type enforcement) are type-inferred from their stored values and mapped to monday.com typed columns. Text values map to Text or Long Text columns; numeric values map to Numbers columns; date-formatted values map to Date columns; checkbox-like values (true/false, yes/no) map to Checkbox columns; and multi-option values map to Dropdown columns. When type inference fails or conflicts with an existing monday.com column type, we flag the conflict and provide a fallback to a text column.

Output Time tags stored as string arrays on tasks or projects map to monday.com Label columns. If the Label column is not available on the customer's plan, we map tags to a multi-select text column. We preserve all tag values and their assignment per task during migration. The customer chooses the tag strategy during scoping.

Output Time file attachments on tasks and projects cannot be migrated programmatically because Output Time exposes no API endpoint for file access. We inventory all attachments at the start of the migration, record their original filenames and Output Time storage paths, and provide a file manifest so the customer can manually re-upload files to the corresponding monday.com items post-migration. We do not delete or alter the source files during this process.

If Output Time billing features are in use, invoice records (line items, totals, status, client association) are exported as a structured CSV. We do not create invoices in monday.com because monday.com does not include a native invoicing object. We deliver the invoice CSV with all line-item data intact for manual recreation in the customer's billing tool of choice.

Output Time's automation capabilities (if any are in active use) do not migrate to monday.com because the automation logic, triggers, and actions differ fundamentally between platforms. We deliver a written inventory of every identified Output Time automation with its trigger conditions, actions, and recommended monday.com Automation equivalent (using monday.com's Standard 250-action or Pro 25,000-action automation engine). The customer's admin rebuilds automations in monday.com post-migration.