Migrate from Allfred to Trello

Allfred Projects map directly to Trello Boards within a Trello Workspace. We create one Workspace per Allfred data export or per agency client grouping, then create a Board per Allfred Project. Project name, description, status, start date, and due date migrate as Board metadata. Allfred project team assignments map to Trello Board members. The Workspace is created first so Board creation references a valid Workspace ID. This mapping is 1:1 and stable across all Allfred and Trello tiers.

Allfred Tasks map to Trello Cards on the corresponding Board. Title, description, assignee, due date, priority, and status migrate as Card fields. Task hierarchy (parent task to subtask) is preserved by nesting subtasks under their parent as Trello checklist items. Status mapping uses Allfred task status values mapped to the target Board list names we configure during scoping. Open tasks land in the first list (e.g., To Do), in-progress tasks in the second (Doing), and completed tasks in the final list (Done).

Allfred Subtasks flatten into Trello Checklist items attached to the parent Card. Each Subtask title becomes a Checklist item; Subtask assignee and due date are appended to the checklist item text as a formatted note. Checklist item completion state migrates from Allfred subtask status. If Allfred subtasks have their own subtasks (nested depth), we flatten all levels into a single checklist hierarchy. Trello imposes a 200-item checklist limit per card; deeply nested Allfred subtask trees exceeding this threshold require splitting across multiple cards, flagged during scoping.

Allfred Client records have no native Trello equivalent. We discuss the preferred strategy during scoping: Option A creates a dedicated Trello Board per Client with project boards linked via card URLs; Option B stores Client name and contact details in a card description on a Client board with Cards representing individual engagements. Client-to-Brand relationships are preserved as card labels or linked Card descriptions. Allfred contact fields (phone, email, address) migrate to Trello Card descriptions in a structured format. This object does not exist natively in Trello; post-migration workflow changes are required.

Allfred Brand records (brand name, logo URL, color palette, guidelines) have no native Trello equivalent. We apply the same strategy as Client mapping: either a dedicated Brand Board with linked project cards or brand fields stored in Card descriptions. Brand logo and color palette are stored as card attachments or in the card description as structured text. The Client-to-Brand parent relationship migrates as card labeling (Brand name as label) or as a cross-board Card URL link.

Allfred Contractor records contain name, contact details, hourly rate, and assignment history, with no direct Trello object. We add contractors as Trello Workspace members (or Board members if the contractor should not access all boards) and store their hourly rate in a Trello custom field on the cards they are assigned to. The assignment history (which projects and tasks a contractor worked on) is preserved as the contractor's Card assignee role across the relevant cards. Archived contractors migrate as inactive Workspace members. Trello does not support billing rate fields natively; we use a custom number field on cards to carry rate data, or document the rate in the card description.

Allfred Team Member records (name, email, role, avatar) map to Trello Workspace members. Role information is preserved in a Trello custom text field on Cards or in the card description. Team Member assignment history on tasks and projects migrates as Card assignee records. Active team members are invited to the Workspace before migration; archived or deactivated Allfred users are migrated as inactive Workspace members. Allfred role distinctions (Admin, Member, Contractor) must be manually re-established in Trello Workspace settings after migration.

Allfred Kanban board column names and card-to-column assignments map to Trello Board list names and Card positions within those lists. Column order is preserved. Allfred column states (active, archived, color-coded) are stored as Trello list names and optional list colors. Column naming conventions vary by Allfred project; we extract all distinct column names during discovery and configure the target Board with matching list names before cards are placed. If a card in Allfred exists in multiple column states, the most recent state determines the destination list.

Allfred per-project custom fields require explicit mapping against Trello's supported types: dropdown, date, number, text, checkbox, and rating. Any Allfred field type not in this list (currency, percentage, URL, etc.) is converted to the closest Trello type and flagged for customer review. Custom fields in Allfred exist per-project with no global schema; we extract all unique field definitions across all projects, deduplicate by name and type, and create Trello Board-level custom fields on the corresponding target Board. Trello custom fields require Premium ($10/user/month) or Enterprise; Standard tier does not support them. We confirm the destination tier during scoping and alert the customer if the target account's tier does not support custom fields.

Allfred file attachments linked to Projects, Tasks, and Clients migrate as Trello Card attachments. Allfred's 2 GB per-file limit is larger than Trello's Standard tier limit of 250 MB per attachment; we identify files exceeding this threshold during discovery and present three options: chunking (for supported file types), storing as an external URL reference (SharePoint links preserved as-is), or excluding from migration with a manifest provided to the customer. Trello Enterprise raises the limit to 2 GB. File attachment links on Cards preserve the original file name and URL for reference.

Allfred workspace configuration, notification preferences, and integration settings cannot migrate as a data record because Trello stores workspace settings separately from card data. We export Allfred settings as a JSON manifest during the discovery export and present it as a setup guide for the customer to manually reconfigure in Trello Workspace settings post-migration. This includes notification preferences, SharePoint integration settings, and any Allfred-specific workspace-level configurations that do not have a Trello equivalent.

Allfred deal pipelines and project pipelines map to Trello Board structures. Each Allfred pipeline becomes a separate Trello Board, and each stage within the pipeline becomes a Trello list in column order. Allfred pipeline-level custom fields map to Trello Board-level custom fields on the corresponding Board. If the customer uses Allfred for project and deal tracking simultaneously, we create separate Workspace sections for project Boards and deal Boards to maintain logical separation. Pipeline-level reporting requires Trello Power-Ups (such as Corrello or Screenful) post-migration.