Migrate from Advantage to Trello

Advantage Projects map directly to Trello Boards. Project name becomes the Board name, project description migrates as the Board description. We create boards in the destination Workspace matching the Advantage project hierarchy. Board visibility (public or private) is set based on Advantage project sharing settings, or defaults to Workspace visibility on Trello.

Advantage Tasks map to Trello Cards. Task name becomes the Card title, description migrates as Card description, due date maps to Card due date, and the assignee field maps to Card members. Status (Active, Complete) maps to whether the Card exists in the appropriate List (To Do, In Progress, Done) rather than a status field. We resolve assignees by email against Trello Workspace members before card creation.

Advantage subtasks under a parent Task map to Checklist items on the corresponding Trello Card. Each subtask becomes a checklist item with its own completion status preserved. Since Trello does not support nested checklists, all subtasks flatten to the top-level checklist named after the original parent task. Long subtask titles truncate at Trello's 512-character card name limit with a note added.

Advantage custom objects defined in Schema Manager with pick list values and relationship fields map to Trello Custom Fields using the Custom Fields power-up. We match field types: Advantage text fields become Trello text fields, pick lists become dropdowns, dates become date fields, and checkboxes become checkbox fields. Relationship lookups between custom objects are documented as text fields in Trello since Trello does not support cross-object relationships.

Custom fields on standard Advantage objects (Projects, Tasks) map to Trello Custom Fields on the corresponding Cards. We apply the same type matching logic. Any required-field constraints in Advantage are noted and enforced during migration rather than enforced in Trello (where required fields are a power-up feature on Enterprise).

File attachments linked to Advantage Tasks migrate as Card attachments on the corresponding Trello Cards. We download source files, re-upload to Trello using the API, and preserve the original filename and upload date. Trello free plan limits attachments to 10MB per file; Standard and Premium allow 250MB per file. Files exceeding the destination plan limit are flagged for customer review before migration.

Advantage Users are matched to Trello Workspace members by email address. The migration user must have admin access to the Trello Workspace to invite members during migration if not all users exist. We generate an invitation list for any Advantage users without a Trello account, and the customer provisions those accounts before the record migration phase begins.

Advantage task assignments (Owner field on Tasks) map to Card members in Trello. Multiple assignees on a single Advantage task become multiple members on the corresponding Card. The lookup uses the User-to-Workspace Member email resolution from the previous step.

Advantage Comments on Tasks migrate as Card comments in Trello with the original comment author mapped to the Trello member with the matching email. Comment body and timestamp are preserved. Comments on Projects migrate to the Board description or a designated informational Card at the customer's choice during scoping.

Advantage project-level tags or categories map to Trello Board Labels. We create a label set on each Board with names and colors matching the Advantage categories, and apply labels to Cards based on the Advantage project category field. Label mapping is documented in the scoping phase.

Advantage workflow rules and automation conditions are exported as a written inventory. We do not migrate them as executable code. The inventory includes the rule name, trigger condition, and recommended Butler command equivalent for the customer's admin to implement in Trello post-migration.

Automation rules triggering on record creation, field change, or assignment in Advantage are documented with their trigger type, conditions, and actions. We do not rebuild these in Trello Butler. The written automation inventory serves as the rebuild guide for the customer's admin.