Migrate from Braid to Trello

Braid Projects map to Trello boards. Each board's name carries the project name, and the project description migrates to the board description field. Braid project status (active, archived) maps to Trello board archival state; archived projects become archived boards. Braid's multi-location project tags migrate as board labels for geographic filtering. The client association on the Braid project becomes a board label or a custom field on each card within the board to preserve client linkage.

Braid Clients are organizational entities owning engagements. We map client names to Trello board-level labels or a card-level custom field called Client that appears on every card in the corresponding board. Client contact details (address, phone, billing email) migrate to a custom field group on each board. If the customer maintains a client registry separate from projects, we can map Clients to a separate Trello workspace or a dedicated board using card entries with client metadata.

Braid Resources represent people assigned to projects. We map Resources to Trello workspace members by email match. Braid capacity settings and multi-location flags migrate as custom fields on each member's profile card or as board-level labels for capacity visibility. Firm-booking versus soft-booking distinctions from Braid scheduling do not have a Trello equivalent; we document these as requiring manual board configuration post-migration.

Braid Time Entries are tied to Resources and Projects, capturing hours worked, dates, billable flags, and optional rates. We map time entry summaries to Trello card custom fields (Date, Number for hours, Text for notes) and optionally as checklist items with a standardized time-log format. Approval status from Braid migrates as a custom field or card label. We preserve the original time entry date, hours, and billable flag as typed custom field values so that totals can be calculated via Trello reporting Power-Ups or exported for reconciliation.

Braid budget-versus-actual figures per project have no native Trello equivalent. We pre-create board-level custom fields on each board (Budget Estimate as Number, Actual Spend as Number, Variance as Formula or Number) before any data migrates. Raw Braid financial figures migrate into these fields for audit purposes. Revenue recognition settings and billing cycle models do not transfer; we document these as requiring re-establishment in the customer's accounting or reporting system post-migration.

Braid custom fields scoped to Projects require pre-discovery during scoping and pre-creation in Trello before board migration begins. We run a pre-migration discovery pass against the customer's Braid instance to enumerate all custom field names, types, and picklist values. Field types map to Trello equivalents: text to Text, numeric to Number, date to Date, multi-select to Dropdown. Braid picklist values migrate as Trello Dropdown options. Fields exceeding Trello's 25-character name limit are truncated with a note in the migration report.

Braid custom fields scoped to Resources (skills, certifications, department tags) map to Trello workspace Power-Up fields or card-level custom fields. We discover the full resource custom field schema during scoping and pre-configure the destination workspace. Multi-select resource tags migrate as Trello labels on boards where that resource is assigned.

Braid employee scheduling ties availability and allocation to Resources. These do not have a native Trello equivalent. We map schedule assignments to board labels (e.g., Available, Allocated, On Leave) and card due dates where applicable. Soft-booking versus firm-booking distinctions are documented in the migration report as requiring Butler rule configuration or a third-party scheduling Power-Up post-migration.

Braid's multi-location support means Resources and Projects can be tagged by geographic location. We preserve these tags as Trello board labels with location names. Boards can be filtered by label to replicate geographic grouping that existed in Braid. If the customer requires a dedicated Locations board, we can structure a separate board with location-tagged cards per resource.

Braid work items that are not formal Projects or Time Entries map to Trello cards within the corresponding board. We preserve card title, description (as card description), due date (as due date), and assignment (as member). Checklist items within a Braid work item migrate as Trello checklists. Attachments migrate as card attachments via URL reference or Trello Power-Up integration with the customer's file storage.

Braid comments on work items and engagements migrate to Trello card comments. We preserve comment author (mapped to Trello workspace member), timestamp, and body text. Rich text formatting is preserved as plain text with basic formatting carried over where Trello comment syntax allows. Comment threading does not map directly; top-level comments migrate as individual card comments in chronological order.

Braid attachments on projects, resources, and work items migrate as Trello card attachments. We extract attachment URLs and file metadata from Braid, then upload to Trello via the Trello REST API attachment endpoint. Large attachments may require manual re-upload to the customer's connected Google Drive or Dropbox if Trello's attachment size limits are reached; we flag any attachments exceeding 10 MB in the pre-migration report.

Braid engagement meetings linked to projects map to Trello cards with a Meeting checklist template. Meeting title, date, attendees, and location migrate as card fields or checklist items. If the customer uses a connected calendar Power-Up, we note the integration path but do not configure calendar sync as part of migration scope.

Braid call engagements linked to work items migrate to Trello card checklists with call disposition and duration as checklist items or custom fields. Call recording URLs are preserved as card attachments or card description links. We do not migrate call recordings into Trello native storage; the customer retains recordings in their original Braid-connected storage or re-uploads to a supported Power-Up.

Braid email engagement metadata (subject, date, recipient, body excerpt) migrates to the corresponding Trello card description or as a card attachment with email content. Full email threading does not map natively; we document email threads as requiring a separate email integration Power-Up (e.g., Slack, email-to-board) post-migration.

Braid engagement tasks (distinct from project work items) migrate to Trello card checklist items within the corresponding board card. Task title, due date, and assignment status are preserved. Completion status maps to checklist item checked state.

Braid archived projects migrate to Trello archived boards. We identify all Braid projects with status archived or inactive during the discovery pass and set those boards to archived state in Trello. Archived boards remain accessible to workspace members but do not appear in the default board list. This prevents active team members from working in stale project boards while preserving historical record.

Braid tags applied across Projects, Resources, and Work Items migrate to Trello board labels. We preserve tag names and apply them to the corresponding cards. Braid's cross-object tagging (a tag applied to both a project and a resource) may require splitting into separate label sets per board context; we document this in the scoping report.

The Braid organization level maps to a Trello workspace as the top-level container. All boards, members, and Power-Ups live within this workspace. We configure workspace-level settings (visibility, permissions, default board) during migration setup. Enterprise customers with multiple Braid sub-organizations may require multiple Trello workspaces; we map each sub-org to a separate workspace during discovery.

Braid time entries carry billable rate and billable/non-billable flags. These migrate to Trello card custom fields (Billable as Checkbox, Rate as Number, Total as Formula or Number) for invoicing visibility. Since Trello does not natively generate invoices, we preserve the raw billing data as structured fields for export and reconciliation in the customer's accounting system.

Braid integrations with external tools (calendar, file storage, accounting) require replacement setup in Trello. We inventory all active Braid integrations during discovery and deliver a written integration map recommending Trello Power-Ups or Butler equivalents for each. Butler automations built in Braid do not migrate; we document existing automation logic for the customer's admin to rebuild in Trello Butler.