Migrate from SmartTask to Trello

SmartTask Projects map 1:1 to Trello Boards. Project name, description, start and due dates, status, and project-level custom fields transfer. We create the Board in the target Workspace, set the Board visibility (private, workspace, public) based on the SmartTask project's access settings, and preserve the project-level custom field schema as Board-level Custom Fields on the target. Project color coding migrates to Board background color if available; otherwise a default is applied.

SmartTask Tasks map 1:1 to Trello Cards within the target Board. We transfer title, description (migrated as card description), start and due dates (as due date on card), priority (as a Label with color coding), and tags (as Trello Labels). Each SmartTask checklist item becomes a Trello Checklist item on the card. We maintain parent-child task relationships by placing child tasks as cards in the same List with a prefix label or card name convention indicating hierarchy; deep nesting beyond two levels is flattened with the admin's preferred convention.

SmartTask custom field schemas vary by project, meaning a single workspace may have inconsistent field definitions across task records. We perform schema discovery across all SmartTask projects before migration, catalog every unique custom field name and type (string, number, date, yes/no), and create matching Custom Fields on each destination Trello Board before card import. Trello Custom Field types (checkbox, date, dropdown, number, text) map from SmartTask's type system. Note that Trello checkbox Custom Fields that have never been checked cannot be copied via move operations; we flag any such records before import.

SmartTask Task Assignees resolve by email against Trello Workspace Members. We extract every distinct assignee email across all tasks, match against the target Trello's member list, and assign Members to Cards by email. Any assignee with no matching Trello Member goes to a reconciliation queue for the customer's admin to provision before card import. A single SmartTask task with multiple assignees results in multiple Member assignments on the Trello Card.

SmartTask Followers on tasks have no Trello analog. Trello Cards have Assignees (Members) but no follower or observer role beyond Board-level access. We flag all follower records for the customer's admin to review post-migration and decide whether to convert followers to Members on a per-task basis or document the follower list for reference.

SmartTask Task Comments migrate as Trello Card Comments. We preserve author, timestamp, and comment body. Project-level Discussions attach to the Board as the first Card comment or as a Board description note, depending on the customer's preference during scoping. Comment threading in SmartTask becomes a flat comment list in Trello, and we note this structural difference in the migration report.

SmartTask recurring tasks with daily, weekly, monthly, yearly, or custom recurrence rules and next-occurrence dates do not have a native Trello equivalent. We migrate the recurrence rule, original creation date, and next-occurrence date as a Card Custom Field (text or date) so that the customer's admin can configure Butler rules or a calendar Power-Up to replicate the recurrence pattern post-migration. We do not build the Butler rules within the migration scope.

SmartTask Task Templates with pre-filled fields and default assignees map to Trello Card Templates. Template names and default field values transfer to the destination Card Template, with a note that any automation triggers attached to templates in SmartTask do not carry over and require rebuilding in Trello's Butler.

SmartTask Tags map 1:1 to Trello Labels. We create Labels in the destination Board using SmartTask tag names, matching color if the source tag has a color assignment. Tags applied across multiple projects create the same Label on each target Board. New Labels are created if they do not already exist in the target Board.

SmartTask file attachments (from Google Drive, Dropbox, or direct upload) migrate as Trello Card Attachments. We export file references and URLs. Note that SmartTask file attachments stored in external storage may require re-authentication to the storage provider after migration; we flag any attachments requiring re-authentication in the migration report and note that attachment integrity is the customer's responsibility post-migration.

SmartTask Milestones group tasks under a shared deadline marker and custom status values are supported per project. We map Milestones to either a dedicated Trello List (one list per milestone) or to a Label with the milestone name, depending on the customer's preference during scoping. Custom status labels migrate as color-coded Labels or as List names if the status represents a Kanban stage. The customer chooses the convention during discovery.

SmartTask Time Entries on tasks (available on Business and Enterprise tiers) have no native Trello equivalent. We export time entries as Card Custom Fields (number or text) capturing total duration, and flag time entry records in the migration report for the customer to configure a time tracking Power-Up (Planyo, Timely, or Toggl integration) post-migration. We do not configure third-party Power-Up integrations within the migration scope.