Migrate your ONES.com data

Projects are the top-level container in ONES Project, organizing Tasks, Requirements, Sprints, and Bugs. They support multiple project templates (Scrum, Kanban, general task management). We migrate Projects as the primary parent object and preserve project-level settings such as template type and member assignments.

Tasks are the core work item in ONES Project. They support subtasks, assignees, priorities, status workflows, due dates, and time tracking. We preserve the parent-child task hierarchy during migration and map custom status values explicitly to the destination platform's workflow states.

Requirements are distinct work items used to capture product specifications and link them to Tasks or TestCases. The schema is stable but linkage semantics (how Requirements relate to downstream work items) vary by project template. We preserve Requirement-to-Task associations as custom fields in the destination where a native link type does not exist.

Sprints are time-boxed iterations associated with a Project. Each Sprint holds a set of Tasks and has start/end dates, goal descriptions, and status. We map Sprint assignments and dates, but sprint-specific metrics and velocity data may not translate 1:1 to all destination platforms.

Bugs are a specialized work item type with severity, steps to reproduce, and environment fields. They can be linked to Tasks or Requirements. ONES Project supports independent Bug-tracking boards. We migrate Bugs with full field fidelity including priority, assignee, and linked parent work items.

TestCases are managed in ONES TestCase and linked to Requirements and Builds. They contain test steps, expected results, and pass/fail history. The destination must have a corresponding test-management object. Where it does not, we map TestCases to Tasks with test-step data preserved as a long-text custom field.

ONES Wiki is a team documentation workspace. Pages can be imported from Confluence (HTML) or Word (.docx), and exported as PDF or Word. We handle page trees and rich-text content, but complex tables that exceed PDF width limits are truncated on export — we flag this for review before committing the migration.

Project members are assigned roles at the project level. User profiles include name, email, and avatar. We map user assignments on Tasks, Bugs, and TestCases to the destination's user records by email, creating placeholder users where no match exists.

Both ONES Project and ONES Wiki support custom fields on work items and page metadata. Custom field types include text, number, date, dropdown, and user references. We map custom field definitions explicitly and translate values, noting that dropdown options may differ between source and destination and require manual review.

Attachments on Tasks, Bugs, and Wiki pages are stored and served by ONES. We migrate attachments by downloading from ONES storage and re-uploading to the destination. File size limits and storage availability at the destination must be confirmed before migration.

Automation rules within ONES Project (triggers and actions for task state changes, assignments, notifications) are not exposed via a documented migration API. These must be recreated manually in the destination platform after migration.

ONES Build and ONES Pipeline store CI/CD pipeline definitions that are tightly coupled to the ONES environment and code integrations. These are not portable across platforms and must be rebuilt in the destination CI/CD system.