Migrate from Artemis 7 to Trello

Artemis 7 Projects map to Trello Boards. Project name becomes the board name, description maps to the board description field, status (Active/On Hold/Complete) maps to board archival or a status label. We create one board per Artemis 7 project during migration, preserving the original project owner as the board's first admin member.

Artemis 7 Tasks map to Trello Cards. Task name becomes card title; description maps to card description (markdown preserved). Status maps to a Trello label (e.g., 'To Do', 'In Progress', 'Done') or list position depending on whether the destination board uses labels or lists to represent task states. We resolve the assignee email from Artemis 7 to a Trello member and add them to the card.

Artemis 7 subtasks with a parent Task reference become either checklist items within the parent Trello card (preferred for fewer than 15 subtasks) or child cards linked via a Power-Up like Card Dependencies (for complex hierarchies or subtasks with independent assignees and due dates). We flag subtasks exceeding 15 items for explicit customer choice during scoping.

Artemis 7 Milestones (date-driven markers) map to Trello Cards created in a dedicated Milestones list. The milestone name becomes the card title, the due date migrates as the card due date, and a 'Milestone' label is applied. Milestones without an explicit task association are standalone cards; milestones attached to a specific task are applied as due dates on the corresponding card.

Artemis 7 Resources (user name, role, availability) map to Trello Board Members. We resolve by email match; any Artemis 7 resource without an email is flagged for the customer to provide an email or create a placeholder Trello account. Role names map to Trello label colors or a dedicated role label on the member's cards. Availability and capacity percentage do not migrate as native Trello fields; we note them in a card custom field or the card description for manual tracking.

Artemis 7 Time Entries (hours, user, task) migrate as card activity comments or custom field entries in Trello. We extract the total hours per task and append as a formatted comment (e.g., 'Time logged: 3.5h by j.smith on 2025-03-12'). For customers with time-tracking Power-Ups pre-configured, we map directly to the Power-Up's API. Native billable flags and billing rates require explicit confirmation during scoping and map to a Trello custom field if the destination board has the Custom Fields Power-Up active.

Artemis 7 Gantt dependency metadata (Finish-to-Start, Start-to-Start, Finish-to-Finish) cannot map natively to Trello, which has no built-in dependency graph. We map to Trello card links (one card linking to another) using the Card Dependencies Power-Up if the customer has it active, or manual card URL references if not. We flag all dependencies with unsupported types (Finish-to-Finish, Start-to-Start) as items requiring admin review post-migration.

Artemis 7 custom fields are defined independently per project. During scoping we ask the customer to identify all active projects and consolidate unique custom field names. Fields with identical names across projects map to a single Trello Custom Field definition on the target board. Fields with identical names but different data types (e.g., text in Project A, number in Project B) are the most common source of import errors and are flagged as a reconciliation step requiring customer decision before data load.

Artemis 7 attachments are stored as URLs referencing the platform's own file storage service. These URLs expire or break when the Artemis 7 account is deprovisioned. We do not include attachment URLs in the migrated dataset. We extract and deliver a flag list of every attachment URL with its associated card name and original Artemis 7 project so the customer can manually re-upload files to Trello as card attachments post-migration.

Artemis 7 project status values (Active, On Hold, Complete, Archived) map to Trello's board archival feature. Projects with status 'Archived' or 'Complete' are migrated as archived Trello boards. Projects with 'On Hold' receive a status label 'On Hold' on all cards or are moved to an archived list within the active board.

Artemis 7 priority values (Critical, High, Medium, Low) map to Trello label colors. We apply a consistent label color scheme (e.g., red for Critical, orange for High, yellow for Medium, green for Low) across all boards migrated. If the destination Trello workspace already uses labels for another purpose, we coordinate with the customer to define a non-conflicting label schema during scoping.

Artemis 7 start and end dates map to Trello card due dates. Trello natively supports due dates on cards; start dates require a Power-Up (Custom Fields 'Start Date' type) or can be stored in the card description. We map the Artemis 7 end date to Trello due date; if start date tracking is required, we create a custom field of type date on boards that have the Custom Fields Power-Up active.