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

TeamBoard Projects map directly to Asana Projects. Each TB_Project__c record carries Name, StartDate, EndDate, Status, and Portfolio reference. We map Project Name to the Asana Project name, StartDate and DueDate to the Project's start and deadline dates, and Status to an Asana Project color indicator (green for On Track, yellow for At Risk, red for Off Track). Portfolio linkage migrates to Asana Portfolio membership. We use Asana's bulk project creation endpoint for batches of up to 100 projects per request.

TeamBoard Work Items map 1:1 to Asana Tasks within the corresponding Project. TB_Task__c fields (Name, Description, StartDate, DueDate, Status, Assignee) map to Asana name, notes, start_on, due_on, completion, and assignee. Sub-items (TB_SubItem__c) map to Asana Subtasks nested under the parent Task. The parent Work Board reference resolves to the containing Project during transform. Task ordering within a Section preserves the TeamBoard sequence order.

TeamBoard Work Boards represent a Kanban-style organizing view with configurable columns. Asana has no Work Board equivalent, so we decompose the board into Project Sections (representing columns) and a custom-field taxonomy for column-specific metadata. Board-level configuration objects migrate as a JSON-encoded custom field on the Project for audit. If the TeamBoard org uses multiple board views per project, each board becomes a separate Section set within the same Project.

TeamBoard Resource records link a Salesforce User to a TB_Task__c with allocation percentage and date range. We resolve TB_Resource__c assignments by matching the Salesforce User email to an Asana User (by workspace member invitation), then write the allocation percentage to an Asana custom numeric field on the Task and set the Task assignee to the resolved Asana User. The date range for allocation becomes the Task start_on and due_on. If an Asana User does not yet exist, it enters a reconciliation queue for the admin to provision.

TeamBoard time entries linked to TB_Task__c migrate to Asana Task-level time tracking entries. Each TB_TimeEntry__c record carries Hours, LoggedDate, User reference, and Task reference. We set the Asana Task to have time tracking enabled and create a time entry with the original date and hours value. The logged User resolves via email lookup. Total hours per task aggregate in Asana's time tracking summary. Entries spanning multiple days create separate Asana time entries per day.

TeamBoard Timesheets aggregate weekly or period-based time entries with an approval workflow (Pending, Approved, Rejected). Asana has no native timesheet approval routing. We migrate the timesheet records as tagged groupings of the underlying time entries, preserving the original period dates and the last-known approval status in a custom-field text value. We flag to the customer that approval routing must be rebuilt in Asana's native approval flows (available on Business and Enterprise) or via a third-party integration post-migration.

TeamBoard Portfolio records group multiple Work Boards (Projects) under a single oversight entity. Asana Portfolios at Business and Enterprise tiers serve the same function: a collection of Projects with progress, status, and workload views. We map TB_Portfolio__c Name to the Asana Portfolio name and link all migrated Projects that reference the Portfolio. Portfolio-level metadata (owner, description) migrates to Portfolio-level custom fields.

TeamBoard vacation approval records carry employee, start date, end date, status, and approver. Asana has no native vacation or absence management object. We extract vacation entries as date-range records attached to the relevant User's workspace as a tagged custom-field set (vacation_start, vacation_end, vacation_status). For organizations using a dedicated HR tool, we document the mapping for integration. Vacation approval workflow is not portable and must be configured in the destination HR system.

TeamBoard extends Salesforce standard and custom objects with additional fields for project metadata, task classification, and resource attributes. We perform Salesforce field-level discovery against the source org to enumerate all TB_-prefixed custom fields, their API names, data types, and picklist values. Each field maps to an equivalent Asana custom field of matching type (text, number, date, enum) created at the Project or Task level. Picklist values migrate as custom field options.

TeamBoard reports are configured as Salesforce report types against TeamBoard custom objects. These report definitions cannot be exported as structured data. We export the underlying record data (Projects, Tasks, Time Entries, Resource allocations) in CSV and JSON formats so that equivalent Asana dashboards and reports can be configured. We deliver a written report inventory listing each TeamBoard report's metric, filter, and visualization type for the customer's admin to rebuild in Asana's native reporting or a BI tool.

TeamBoard's timesheet and vacation approval workflows are Salesforce Flow-based or declarative approval configurations attached to TB_Timesheet__c and TB_Vacation__c. These workflow definitions cannot be extracted as transferable automation code. We document the current approval chain (approver role, conditions, escalation path) and deliver a written recommendation for rebuilding in Asana's approval flows (Business and above) or a dedicated approval tool. The migration does not include post-migration workflow rebuild.

TeamBoard organizes Work Boards into Folders within a WorkZone hierarchy. Asana has no native folder concept within a workspace; projects exist as a flat list or within Teams. We map Folders to Asana Teams (for orgs that use Teams as the top-level grouping) or to a tagging convention that the customer defines during scoping. WorkZone-level metadata becomes workspace-level custom fields.