Migrate from YouGile to Trello

YouGile Projects map directly to Trello Boards as the top-level container. Project name, description, and creation date migrate as Board name, Board description, and a pinned card noting the original creation timestamp. We set the Board visibility to private by default unless the customer specifies otherwise during scoping.

YouGile Columns within a Project map to Trello Lists within a Board. Column names (e.g., To Do, In Progress, Done) migrate as List names verbatim. Custom column names beyond the standard set require explicit mapping confirmation from the customer during scoping to ensure no list is inadvertently dropped.

YouGile Tasks migrate as Trello Cards. We preserve title (Card name), description (Card description as markdown), assignee (Card member), due date (Card due date), priority (mapped to a Label or a custom field depending on tier), and creation/modification timestamps. Task IDs are recorded in a custom Card field for reconciliation during validation.

YouGile Subtasks migrate as Trello Checklist items within the parent Card. Subtask completion state (boolean) maps to checklist item checked/unchecked status. Parent-child relationship is preserved by nesting all extracted subtasks under a single Checklist titled 'Subtasks' on each Card. Trello's Standard tier (or above) is required for checklists; Free tier supports checklists with a 100-item limit per card.

YouGile's per-task chat thread has no direct Trello equivalent, so we extract each message as a Card Comment with author name, timestamp, and message body preserved. We format the comment header as 'Chat entry from YG-username on YYYY-MM-DD HH:MM:SS' to distinguish migrated chat from manual comments added post-migration. Thread ordering is preserved chronologically.

YouGile task attachments are referenced by URL in the source data model. We download each attachment file, re-upload it to the destination Trello Card via the Trello API, and link it with the original filename preserved. Large files exceeding Trello's 10 MB per-file limit on Free tier require the customer to either upgrade to Standard or use a Power-Up like Google Drive integration for file linking. We flag any oversized files during scoping.

YouGile team members map to Trello Workspace members. We extract member email and display name from YouGile and invite them to the Trello Workspace by email. Role mapping is approximate since YouGile has no documented role hierarchy; all migrated members receive Standard Workspace member access. Members without valid email addresses go to a reconciliation queue for the customer to resolve.

YouGile embeds time-tracking entries as structured numeric values (hours logged) within tasks. We extract logged hours as a numeric value and map it to a Trello Custom Field named 'Hours Logged' (type: number) on each Card. Trello Standard tier or above is required for custom fields. Rate and billing data are not available in YouGile and do not migrate. The customer rebuilds any rate calculations in Trello or a separate billing tool.

YouGile Labels and tags migrate to Trello Labels on each Card. We preserve label name and color metadata where available. Trello supports 25 labels per Board, which is sufficient for most migration scopes. If YouGile uses more than 25 distinct labels across the account, we consolidate by color group and document the remainder for manual relabeling.

YouGile exposes a Gantt-chart view of task timelines but the underlying Gantt data is not stored as a structured field in the export. Task start and end dates migrate as Card due dates, but the visual Gantt layout cannot be reproduced in Trello without a Power-Up such as Timeline or Card Board. We flag this explicitly in the migration report as a manual rebuild item for the customer's admin to address post-migration.

YouGile's automation configurations (webhook URLs, Albato trigger settings, and any outbound HTTP integrations) are platform-specific configuration objects that are not portable across platforms. We do not migrate them. We deliver a written inventory of every active YouGile webhook and Albato automation with its trigger conditions, target URLs, and action summary so the customer's admin can rebuild equivalent automations in Trello Butler or reconfigure Albato connections to Trello.

YouGile custom fields migrate to Trello Custom Fields where Trello supports equivalent types. Text fields map to Trello text custom fields; number fields map to Trello number fields; date fields map to Trello date fields. Dropdown or multi-select custom fields in YouGile require a Trello Standard tier (or above) custom field setup. We handle type mismatches on a case-by-case basis during scoping and flag any YouGile custom field types (e.g., file attachment fields) that cannot map to Trello native types.