Migrate from Husky to Trello

Husky Projects map directly to Trello Boards. We extract the project name, description, status (active/archived), start date, and end date and create a corresponding Board in Trello. The board description field carries the Husky project description. Active versus archived status in Husky maps to an open versus closed Board in Trello, with archived boards made private or archived at the customer's discretion.

Husky Tasks map to Trello Cards within the target Board. Task name becomes the card title, description migrates as the card description (markdown preserved), due date maps to the card due date field, and the task status (pending, in progress, complete) maps to list membership in Trello (e.g., To Do, In Progress, Done). The owner assignment maps to a Card member in Trello, resolved by email against the customer's Trello workspace members.

Husky subtasks map to Checklist items within the parent Trello Card. Each subtask's name becomes a Checklist item; completion status maps to the checked state of the item. If a Husky subtask has an assigned owner or due date, we append this information to the checklist item title as a note or create a sub-card in Trello depending on the customer's preference during scoping. The parent-child hierarchy is preserved within the card.

Husky Client records have no direct Trello equivalent because Trello has no client or contact object. We offer two strategies during scoping: (1) Create a dedicated Trello Board named Clients where each client is a Card containing contact details, billing address, and associated project links as card description; or (2) Use Trello Labels (available on Standard plan and above) to tag project Cards by client name, allowing filtering across boards. The choice depends on whether the customer needs to track client-level history versus project-level assignments.

Husky Time Entries link a user, a project or task, and a duration or start/end time. Trello has no native time tracking field. We create Trello Custom Fields on Cards — a Number field for duration (minutes) and a Checkbox field for billable/non-billable — and set a date filter for the migration window to avoid mid-billing-period imports. For time entry groups spanning multiple tasks, we aggregate duration onto the parent Card or create a summary Card in the project Board. Customers needing full time tracking capability should enable a Trello Time Tracking Power-Up as a post-migration step.

Husky Recurring Jobs store a frequency, interval, and last-run date but these rules do not export as re-triggerable schedules. We extract the job template name, description, frequency metadata, and last-run date and create a Trello Card per recurring job in a designated Recurring Tasks board, with the recurrence details captured in the card description as a structured note (e.g., 'Schedule: Every 2 weeks, last run: 2025-11-15'). The customer manually recreates the recurrence in Trello Butler or a Power-Up post-migration. We document the recurrence logic in the post-migration handoff checklist.

Husky custom project fields vary by tenant configuration and can include text, number, date, picklist, or boolean types. We enumerate all custom project fields during discovery and map them to Trello Board Custom Fields if the customer's Trello plan supports them (Standard and above), or to a structured Board Description section if not. Picklist values map to Trello Labels or a dropdown Custom Field type.

Husky custom task fields migrate to Trello Custom Fields on Cards. We handle type mapping: Husky text fields map to Trello Text custom fields, date fields to Trello Date fields (available on Standard+), number fields to Trello Number fields, and picklist fields to Trello Dropdown custom fields. The customer's Trello plan must support custom fields (Standard, Premium, or Enterprise) for this mapping to apply; on the Free plan, custom task fields are documented as a manual-entry gap.

Husky custom client fields (e.g., tax ID, billing terms, industry) map to either card description fields in the Client board (strategy from object mapping entry 4) or to Trello Labels if the client is represented as a label across project boards. We apply the same strategy decision agreed upon during scoping for the Client mapping.

Husky Users and Owners map to Trello workspace members. We resolve by email match against the customer's Trello workspace. Inactive or archived Husky users are flagged during scoping; the customer decides whether to invite them as Trello workspace members (with optional deactivation post-migration) or to assign their records to an active workspace member. Owner assignment on Husky Tasks carries through to Card members on Trello.

Husky task attachments migrate as Card attachments in Trello. We extract attachment URLs or file references and upload them to the target Card via the Trello API. File size limits (10MB on Free, 250MB on Standard+) apply; files exceeding the destination plan limit are flagged and handled per the customer's preference (upload to a linked cloud storage URL or exclude).

Husky task comments map to Trello Card Comments. We extract the comment author (resolved by email to the Trello workspace member), the comment body, and the timestamp. Comments are inserted in chronological order on the target Card. If a Husky comment references an attachment, the attachment reference is preserved as a link within the comment body.

Husky tags on Tasks and Projects map to Trello Labels on Cards. Label colors are assigned from the Trello standard palette during migration; the customer can re-color labels post-migration. Tags that represent project categories (e.g., 'client-facing', 'internal') map cleanly to Trello Labels, while tags used for numeric or boolean data (e.g., 'budget: 5000') map to custom fields instead to preserve data type.

Finalized Husky invoices are locked financial records and are not imported into Trello. Trello has no financial object equivalent and importing finalized invoices would create duplicate entries in the customer's accounting system. We export invoice history as a CSV reconciliation report containing invoice number, client, amount, date, and status. The customer shares this report with their accounting team or CPA for financial record continuity.