Migrate your Output Time data

Projects are the primary container in Output Time, holding tasks, team members, and time entries. We extract all project metadata including name, description, status, dates, and custom fields. The export is 1:1 for standard fields; custom fields require a pre-migration field mapping review.

Tasks sit inside projects and include name, description, assignee, due date, priority, and status. We preserve the task hierarchy and link each task to its parent project and owner during migration. Subtasks are migrated as child task records.

Subtasks inherit all standard task fields and maintain their parent-child relationship to the parent task. We transfer subtask hierarchy intact and flag any subtask that has an unassigned parent so it can be re-linked post-migration.

Time entries record hours worked per task or project. Output Time stores entry date, duration, billable flag, user, and notes. We map these to the destination time tracking object but note that billable/non-billable flags and hourly rate assignments vary between platforms and require field-level mapping.

Users represent team members with roles, email addresses, and project access. We export all active and inactive users and map them to contacts or members in the destination system, preserving display names and email addresses as identifiers.

Clients in Output Time are contact records associated with projects. Some destination CRMs use Companies or Accounts for this concept. We map Client records to the equivalent contact object but flag that the client-to-project linkage must be re-established in the destination.

Output Time supports custom fields on projects and tasks. These are stored as key-value pairs per record. We extract custom field definitions and their values, then map them to destination custom properties, renaming and re-typing where the target schema requires it.

Milestones are dated checkpoints within a project. We export milestone name, target date, and associated project, mapping them to the destination milestone or phase concept. Ordering is preserved based on the due date sequence.

Tags applied to tasks or projects are exported as string arrays. Since not all destination platforms support a native tag object, we map them to labels, categories, or a custom text property depending on what the target system supports.

Output Time stores file attachments on tasks and projects, but the file storage mechanism is not exposed via a documented public API. We do not migrate attachments; we flag their presence and provide a file inventory so they can be manually transferred or re-uploaded post-migration.

If Output Time billing features are in use, invoice records (line items, totals, status) can be exported. We map invoice data to the destination billing or invoice object, noting that tax treatment and payment status fields require manual verification after import.