Migrate your actiTIME data

Customers are the top-level organizational unit in actiTIME, containing Projects. The API exposes GET/POST/PUT/DELETE for Customers with properties including name, description, archived flag, and creation timestamp. We perform a direct read of all active and archived customers and map them to the equivalent top-level entity in the destination system.

Projects belong to a Customer and contain Tasks. The API exposes full CRUD operations with properties such as name, customerId, status, estimatedTime, and deadline. We preserve the customer-project relationship during migration by mapping to the equivalent hierarchy in the destination.

Tasks are the leaf nodes of the actiTIME hierarchy, assigned to a Project. The API exposes task properties including name, projectId, status, estimatedTime, deadline, and custom workflow status. We map tasks including their estimates and deadline values directly into the destination project's equivalent task object.

Time-Track records represent logged work hours and are the core data object in actiTIME. The API supports GET for retrieving entries by user, date range, task, project, or customer. Entries include hours, billable flag, type of work, and comments. We export the full time-track history and map it to time-entry objects in the destination, preserving dates, hours, and billability flags.

The Users resource exposes user properties including first/last name, username, email, active/inactive status, and time zone group assignment. We export the complete user roster and map to owner or assignee fields in the destination, handling active/inactive status as appropriate.

Departments are an optional feature gated by the Departments parameter in the /info endpoint. Not all actiTIME instances have this feature enabled. We check the instance's feature flags before attempting to read or create Department records; if disabled, we skip the object and log the exclusion.

Time Zone Groups group users by timezone for reporting across distributed teams. The /info endpoint exposes the timeZoneGroups feature flag. We export the TZG roster and user assignments, then map them to the equivalent timezone grouping mechanism in the destination if supported.

Types of Work categorise time-track entries (e.g., 'Development', 'Meeting', 'Research'). The API exposes a read-only list of Types of Work per instance. We preserve the full type-of-work taxonomy and map each time-track entry's type to the destination's equivalent categorization field.

Workflow Statuses are a feature-gated capability controlled by the taskWorkflow flag in the instance info. Custom workflow stages vary by instance, so we export the current status definitions and apply a value-mapping step at import time to ensure entries land in the correct stage in the destination system.

Leave time tracking is controlled by the leavetimeRegistration feature flag and may not be enabled on all instances. We check this flag before reading leave records. Where enabled, we export leave entries including type, start/end dates, and status, then map them to the destination's PTO or leave-management object.

Task estimates (planned hours per task) are an optional feature controlled by the taskEstimates flag. Where this feature is disabled, no estimate data exists in the instance even though the task object exists. We verify the flag before including estimates in the migration payload.