Migrate from Agilean to Trello

Agilean Projects map directly to Trello Boards. During discovery we enumerate every Agilean project and confirm whether each maps to a standalone board or should be consolidated into a single board with multiple lists. Agilean's project-level custom fields migrate as Board-level Custom Fields displayed on all cards within the board. Note that Trello does not support sub-projects; any Agilean project with nested sub-projects flattens to a single board per project, and sub-project relationships are documented as a written hierarchy for the customer's admin to model as separate boards in a Workspace or as labels within a single board.

Agilean Tasks map to Trello Cards. The Agilean task title becomes the card name; the task description becomes the card description field. Agilean task hierarchy (parent tasks, sub-tasks) maps to Trello card checklists, with each Agilean sub-task becoming a checklist item under the parent card. If Agilean supports task dependencies, we document the dependency graph as a written inventory because Trello does not have a native dependency model. Task status (Agilean workflow state) maps to the card's current List position on the destination board.

Agilean workflow states (e.g., Not Started, In Progress, Review, Done) map to Trello Lists within each board. During discovery we collect every distinct workflow state used in the Agilean project and create a corresponding List in Trello. The card is placed in the List matching its Agilean workflow state at migration time. If Agilean uses more than 25 distinct workflow states, we consolidate to a maximum of 25 Lists per board (Trello soft limit) and document the overflow states as Card labels for the customer's admin to reconcile post-migration.

Agilean Custom Fields map to Trello Custom Fields. We apply Trello's constraints during mapping: field names are truncated to 25 characters, field types are preserved (text, number, date, dropdown, checkbox), and dropdown options are migrated as Trello dropdown choices. If Agilean uses a field type not supported by Trello (e.g., rich text blocks, multi-user selectors), we flag these as unmappable and document them in the schema inventory with a recommendation for Trello Power-Up alternatives. Custom fields on Agilean's Project object become Board-level Custom Fields in Trello.

Agilean file attachments associated with tasks migrate as Trello card attachments. We extract attachments via the source system's export mechanism (enumerated during discovery), validate file types against Trello's supported formats, and upload each file to the corresponding card. Files exceeding Trello's 10 MB per-attachment limit are flagged and delivered as a separate download package with a link stored in the card description. Image attachments render inline on Trello card faces; other file types render as attachment links.

Agilean task assignees map to Trello board Members. We extract all distinct user IDs from Agilean task assignments and match by email address against the Trello Workspace membership list. We flag any Agilean assignee without a corresponding Trello member in a reconciliation queue; the customer's admin provisions missing Workspace members before the migration proceeds. Trello's free plan supports unlimited Workspace members but limits board visibility controls, which we document as a post-migration admin note if the customer plans to use Standard plan member permissions.

Agilean task tags or labels map to Trello Labels. We enumerate all distinct tag values during discovery and create corresponding Labels in each destination board with the same color scheme where possible. If Agilean uses more than 25 distinct tags per project, we consolidate to 25 Labels per board (Trello limit) and document the overflow tags as card description keywords for manual label assignment post-migration.

Agilean task comments and notes migrate as Trello card Comments. We preserve the comment author (mapped to Trello member), comment timestamp, and comment body text. Rich-text formatting in Agilean comments is simplified to plain text for Trello compatibility. If Agilean supports @mentions in comments, we convert them to plain-text @username strings in Trello and document them as a manual reconciliation item if mention threading is critical for the customer.

Agilean sub-tasks that are represented as checklists within a parent task map to Trello card Checklists. We migrate each checklist item with its completion status preserved. If Agilean's sub-task model is independent (not scoped to a parent), we flatten each sub-task to a Trello checklist item under its parent card. Any Agilean sub-task that has its own attachments, comments, or custom fields is flagged as a complex sub-task requiring manual follow-up.

Agilean task due dates migrate to Trello card Due Dates. The due date and, if available, due time transfer directly. If Agilean tracks due date changes over time (audit history), we migrate only the current due date; historical due date changes are documented as a written log for the customer's records. Trello's Due Date field supports a date-only or date-and-time variant; we set the appropriate granularity based on Agilean's source field type.

Agilean task watchers or subscribers map to Trello card watchers. We extract the distinct watcher list per Agilean task, resolve each watcher email to a Trello Workspace member, and subscribe the corresponding members to the migrated card. If a watcher has no Trello membership, we skip the subscription and flag the record in the reconciliation report. Trello Free plan shows watchers to board admins only, which we document for the customer's admin if visibility controls are a concern.

If Agilean's data model includes custom object types beyond standard Projects and Tasks (e.g., Consulting Deliverables, Contract Records, Client Notes), we do not migrate these as functional records into Trello because Trello does not support custom object schemas. Instead, we extract the data as a structured CSV and JSON export, document the schema in the migration inventory, and deliver the export to the customer's admin for import into a dedicated Trello board, a Google Sheet, or a separate system. We flag any lookup relationships between custom objects and standard Agilean records for manual relationship reconstruction.