Migrate from ONES.com to monday Work Management

ONES Projects are the top-level container in ONES Project and organize Tasks, Requirements, Sprints, and Bugs. We map each ONES Project to a monday.com Workspace, then create one or more Boards within that Workspace based on the ONES Project's internal structure. If the ONES Project uses multiple task boards (e.g., a Kanban board and a backlog board), we replicate that structure in monday.com with separate Boards under the same Workspace. Project templates (Scrum, Kanban, general task) inform the Board template we select during board creation.

ONES Tasks map to monday.com Items. The task title becomes the Item name, description migrates as the Item body, assignees map by email to monday.com Board members, and status workflows map to monday.com Status columns. ONES subtasks map to monday.com Subitems (up to 100 per Item). We preserve the parent-child hierarchy by creating Subitems under the parent Item and mapping any subtask assignees and due dates. Status values in ONES (e.g., Open, In Progress, Resolved) map to the monday.com Board's Status column options.

ONES Sprints are time-boxed iterations with start dates, end dates, goals, and a set of assigned Tasks. monday.com has no native Sprint object, so we map Sprints to monday.com Groups using a naming convention that encodes sprint metadata: [Sprint Name] | [Start Date] - [End Date]. Sprint goal descriptions are stored as Group description text. Tasks are assigned to the appropriate Sprint Group during migration. Sprint velocity and burndown data from ONES do not migrate as metrics but can be reconstructed in monday.com Dashboards using the migrated Item dates.

ONES Bugs are specialized work items with severity, steps to reproduce, and environment fields. We map Bugs to Items on a dedicated monday.com Board. ONES Bug severity levels map to a monday.com Severity dropdown or label column. Steps to reproduce and environment details map to long-text Item columns. Linked Tasks or Requirements in ONES Bug records become Subitem or Related Items links in monday.com. If the customer uses a separate Bug board in ONES, we replicate that as a dedicated monday.com Board with appropriate columns.

ONES Requirements are specification documents linked to Tasks and TestCases for end-to-end traceability. monday.com has no native Requirements object, so we map Requirements to Items on a dedicated monday.com Board. The linked Task relationships become Related Items links in monday.com. The linked TestCase relationships require the TestCase to exist in monday.com first (see TestCase mapping), and we resolve the relationship at migration time. Requirements without downstream links migrate as standalone Items with the requirement text in the description column.

ONES TestCases contain test steps, expected results, and pass/fail history. monday.com has no native test management object, so we map TestCases to Items with formatted text columns for the test steps and expected results, and a Status column for the last-known test outcome. If the customer requires a structured test-step format, we use a multi-checklist or linked Subitem per test step approach. TestCase-to-Requirement linkage maps to monday.com Related Items. TestCase-to-Build linkage is noted as a data point to recreate in the customer's chosen CI/CD platform post-migration.

ONES Wiki pages contain team documentation with rich text, images, and tables. We map Wiki pages to monday.com Docs, which support rich text, images, and embedded Items. We flag wide-table Wiki pages (tables exceeding approximately 720px width) during audit and recommend exporting those as Docs rather than HTML since ONES PDF export silently truncates wide tables. Page tree hierarchy in ONES Wiki maps to a Docs folder structure in monday.com.

Project members in ONES (with roles and permissions) map to monday.com Board members by email match. ONES User profiles include name, email, and avatar. We resolve every ONES user referenced on Tasks, Bugs, Requirements, and TestCases to a monday.com User account by email. Any ONES user without a matching monday.com account is placed in a reconciliation queue for the customer's admin to provision before record import resumes. User roles (Admin, Member, Viewer) map to monday.com Workspace permission levels.

ONES Project supports custom fields on Tasks, Bugs, and Requirements, with types including text, number, date, dropdown, and user references. monday.com Boards support custom columns including Text, Numbers, Date, Dropdown, Status, Labels, Link, and Formula. We map each ONES custom field type to the closest monday.com column type. Dropdown fields in ONES map to monday.com Dropdown columns with the same option values. Date fields map directly. Multi-user reference fields in ONES map to People columns in monday.com. Custom field definitions and their current values are migrated together as column schema and column values.

Attachments on ONES Tasks, Bugs, and Wiki pages are stored and served by ONES storage. We migrate attachments by downloading from ONES storage and re-uploading to the monday.com Board's file column for the corresponding Item. We flag any attachment exceeding monday.com's 250MB per-file limit during audit and flag for the customer's admin to handle as a manual step or alternative storage (Google Drive, S3) with a link embedded in the Item. Attachment filenames and descriptions migrate alongside the file reference.

ONES Tasks support time tracking with logged hours and estimated vs. actual time. monday.com does not have a native time tracking object, so we map ONES time tracking data to Numbers columns (Estimated Hours, Logged Hours) on the corresponding Item. If the customer requires time tracking features post-migration, we note monday.com's native time tracking or a third-party integration (Toggl, Harvest) as a separate configuration step.

Automation rules in ONES Project (triggers such as task status changes, assignees, and due date notifications, with resulting actions) are not exposed via any documented migration API. We do not attempt to migrate automation rules. During discovery, we identify all active automation rules and deliver a written inventory with each rule's trigger, conditions, actions, and a recommended monday.com Automations equivalent. The customer's team rebuilds these in monday.com's Automations Center post-migration. This is the highest-severity gotcha for teams that rely heavily on ONES automation logic.