Migrate from Artemis 7 to monday Work Management

Artemis 7 Projects (top-level container with name, description, status, dates, owner) map directly to monday.com Boards. We create one Board per Artemis 7 Project and set the Board name, description, and status from the corresponding Project fields. Board privacy defaults to Workspace visibility; the customer specifies restricted Boards during scoping if needed. If the customer uses Artemis 7 client-facing portals, we document the equivalent monday.com sharing settings for the admin to configure.

Artemis 7 Tasks (name, status, assignee, start/end dates, estimated hours) map to monday.com Items on the target Board. The Artemis 7 task status values map to the monday.com Status column states. Start and End dates map to a Date column or Timeline column depending on whether the customer uses Gantt-style visualization. Estimated hours map to a Numbers column. Subtasks in Artemis 7 (child records with a parent reference) map to monday.com Subitems attached to the parent Item.

Artemis 7 child tasks with a parent_task_id reference map to monday.com Subitems. The parent-child relationship is preserved by linking each Subitem to its parent Item using monday.com's Subitem structure. Subitem-level assignees, due dates, and status flags map directly from the Artemis 7 child record fields. Subitems do not have a native subtask-of-subtask level in monday.com; deeply nested Artemis 7 hierarchies beyond two levels flatten to Subitems with an informational note field.

Artemis 7 Milestones are date-driven markers with a name and due date associated with a Project. We create a Date column on the target Board and set the Milestone name as the Item name with the due date mapped to the Date column. For milestone groups (milestones that span multiple tasks), we create a dedicated Board with Date items and document the grouping for the customer to configure in monday.com's Group Date feature.

Artemis 7 Gantt dependencies (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish) are stored as relationship metadata in the export. monday.com's native Dependencies feature supports Finish-to-Start and Start-to-Start natively. We map Finish-to-Start and Start-to-Start directly to monday.com dependency arrows. Finish-to-Finish and Start-to-Finish are not natively supported in monday.com; we flag these as unsupported dependency types and document them as manual dependency setup items in the handoff inventory.

Artemis 7 Resource records (user name, role, availability hours) map to the monday.com Person column on Items. We resolve the resource name to an email address from the Artemis 7 export and map it to the corresponding monday.com workspace member. Availability hours from Artemis 7 (capacity-based) map to a Numbers column for reference; the monday.com Workload view (available on Pro and Enterprise) handles capacity visualization separately. Role information maps to a Text or Tags column on the Item.

Artemis 7 Time Entries (hours logged against a task and user) map to a Numbers column on the target Item. The hours value migrates directly. Billable flag and billing rate require explicit customer confirmation during scoping because Artemis 7 stores these as optional fields and monday.com does not have a native billing-rate column. We ask the customer to confirm whether to create a separate Numbers column for rate and a Checkbox column for billable, or to omit these fields. Time Entry dates are preserved as a secondary Date column for chronological reporting.

Artemis 7 custom fields exist per-project and are not centrally managed. We export all unique custom field names across active projects during scoping, consolidate by data type, and create equivalent monday.com Columns on the corresponding Boards. Duplicate field names with conflicting data types (e.g., a text field called Priority in one project and a number field called Priority in another) are the most common source of import errors; we flag these during scoping and ask the customer to resolve or accept a type-picking decision before migration. monday.com column types (Text, Numbers, Date, Timeline, Status, Checkbox, Dropdown, Link, File) map from Artemis 7 data types.

Artemis 7 Project status values (Active, On Hold, Complete, Archived) map to monday.com Status column states. We configure the Status column with the customer's active status labels and map the historical status values to the corresponding states. If the customer uses custom status labels in Artemis 7, we create a mapping table during scoping and apply it consistently across all Boards.

Artemis 7 Project budget fields (if present in the export) map to a Numbers column on the monday.com Board. Budget tracking in monday.com is a column-level feature rather than a native module; the customer uses the Numbers column for budget values and optionally the Formula column for variance calculations. We do not migrate budget alerts or threshold rules; these require manual configuration in monday.com's Automation or Formula features post-migration.

Artemis 7 Risk records (if stored as project-level or task-level fields) map to a monday.com Status column with risk severity states (Critical, High, Medium, Low) or a Tags column depending on the customer's Artemis 7 risk model. Risk assignment and due date map to the Person and Date columns respectively. Risk probability and impact scores map to Numbers columns if the customer used structured risk fields in Artemis 7.

Artemis 7 attachments are stored as URLs pointing to the platform's own internal file service. These URLs are not portable across systems and expire or break when a user account is deprovisioned. We do not include attachment URLs in the migrated dataset. We extract all attachment URLs from the Artemis 7 export and produce a flag list organized by Board and Item, which the customer uses to manually re-upload files to monday.com's Files column post-migration. This is a pair-specific high-severity limitation documented in the Artemis 7 source page.

Artemis 7 Owners (user name, email, role) map to monday.com Workspace members. We resolve each Artemis 7 Owner by email and map to the corresponding monday.com user account. Owners without a matching monday.com account go to a reconciliation queue for the customer's admin to provision before the Board migration phase begins. Role information from Artemis 7 maps to a Text or Tags column on Items if the customer requires role visibility at the task level.

Artemis 7 Project description fields migrate to the monday.com Board description. Board descriptions in monday.com support rich text and are visible in the Board header. We preserve formatting where possible and flag any non-migratable formatting (e.g., embedded images) as manual re-entry items.

If the Artemis 7 export includes tag-style fields (multi-value labels attached to Tasks or Projects), these map to the monday.com Tags column. Tags migrate as a multi-select tag set and are available for filtering and grouping in monday.com views immediately after migration.