Migrate from TeamBoard - Work Management & Project Management for Salesforce to Trello

Each TeamBoard Project maps to a Trello Board. Project name becomes Board name; Project start and end dates migrate as Board description metadata or a Card-due-date baseline, not a native board date range (Trello Boards have no start/end fields). We extract Project status (Active, On Hold, Completed) as a label on the first card in each Board so the customer can filter by project state in the Board overview. Portfolios that contain multiple Projects map to a Workspace or a grouping label applied across all child Boards.

The Work Board is TeamBoard's core organizing entity. In Trello, the closest structural equivalent is either a Board (for project-level boards) or a List (for workflow-stage boards within a single project Board). We assess the customer's usage pattern: Teams using Work Boards as project-level containers map each Work Board to a distinct Board; Teams using Work Boards as workflow stages within a Project map each Work Board to a List within the Project Board. We confirm the strategy during scoping.

Work Items map to Trello Cards. Work Item name becomes Card title; description becomes Card description (migrated as plain text or Markdown depending on formatting complexity); status maps to the target List (e.g., To Do, In Progress, Done); due date maps to Card due date; priority or urgency maps to a Card label. Sub-items attach as Checklist items on the parent Card, preserving the one-level parent-child hierarchy that TeamBoard supports. We preserve the original TB_Work_Item__c ID as a Card comment for traceability.

Tasks under a Work Item in TeamBoard map to Trello Cards in the same Board. If the customer uses TeamBoard's task-table view as a flat task list, we create one Card per task row and nest it under the parent Work Item Card via Checklist. Task assignees map to Card members, resolving Salesforce User ID to Trello member by email. Task status (Not Started, In Progress, Blocked, Complete) maps to the target List.

TeamBoard Folders group Work Boards. Trello Collections serve the same organizational function at the workspace level. We map Folder name to Collection name and associate all child Boards with the Collection. Note that Trello Collections are only available on Standard and Premium plans; we confirm the customer's Trello plan during scoping and flag the upgrade requirement if they are on the Free tier.

Resource records store team member assignments with allocation percentage and date ranges against Work Items. We extract all Resource assignments and resolve them to Trello Card members. Allocation percentage and date ranges have no native Trello equivalent; we store these as Card description metadata or as a Checklist item with the allocation details. Resource types (team member, equipment, room) map to Trello member labels or a custom Power-Up field if the customer has Premium.

Trello has no native time tracking. We export all Time Entry records as a structured JSON file keyed by TB_Work_Item__c ID, with hours, date, user reference, and task association preserved. The customer can import this into a time-tracking Power-Up (TimeCamp, Toggl, Planyo) or a downstream billing system. We do not create Cards from time entries.

Timesheet records aggregate time entries by week or period and carry approval status (Pending, Approved, Rejected). We export the full timesheet history as a JSON artifact with period, owner, total hours, and approval status preserved. Trello has no timesheet or approval concept. We flag that the customer should configure Butler automation or use an external approval tool if they need to replay approval workflows post-migration.

Vacation requests and calendar entries in TeamBoard carry approval status and date ranges. We export these as JSON records with employee name, dates, status, and approving manager. Trello has no calendar or absence management feature. This data is out of scope for Trello migration and is delivered as a reference artifact for the customer's HR or operations team.

TeamBoard Portfolios group multiple Work Boards under a single oversight entity. In Trello, this maps to either a Workspace (the top-level organizational unit) or a label taxonomy applied across all child Boards. We assess during scoping whether the customer has multiple Portfolios that should map to separate Workspaces or a single Workspace with labeled boards. Workspaces are the preferred mapping for distinct business units; label taxonomy is preferred for thematic grouping within one team.

TeamBoard extends its custom Salesforce objects with fields that vary by org (project metadata, task properties, resource attributes). We run field-level discovery on TB_Project__c, TB_Work_Item__c, and TB_Task__c to enumerate every custom field. High-value fields (priority, cost code, client name) map to Trello Card custom fields on Premium or to Card description text on Standard. The customer chooses the strategy during scoping based on their Trello plan.

TeamBoard reports are configured against Salesforce objects and include project health, resource utilization, and schedule adherence views. Report definitions are not portable. We export the underlying data (project status, task counts, time totals, resource allocations) as CSV so equivalent reports can be configured in Trello, Atlassian Analytics, or a BI tool. We scope the migration around data export, not report migration.