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

TeamBoard Projects map to Microsoft Project plan files (.mpp) or Project for the Web projects. The Project Name, Start Date, Finish Date, Status, and Description fields map directly. TB_Portfolio__c relationships (stored as junction object records linking a Portfolio to its Projects) map as separate Project Online projects within a shared enterprise resource pool, with the Portfolio name preserved as a grouping tag. We sequence Project as the first record type imported because all subordinate Task, Resource, and Time Entry records require a valid Project reference.

Work Items are TeamBoard's core work-planning record and map to Microsoft Project tasks. Sub-items map to sub-tasks under the parent Work Item. The Work Item's start date, finish date, status, priority, and percent complete transfer directly. Work Item hierarchy (parent-child relationships) maps to Microsoft Project's outline structure, preserving the WBS level. The drag-and-drop sequence order in TeamBoard's Work Board is preserved as the task sort order in Microsoft Project.

TeamBoard Tasks are child records under Work Items and map directly to Microsoft Project task rows. Assignee, due date, estimated hours, and custom task fields transfer as typed fields. TeamBoard's task status (To Do, In Progress, Done) maps to Microsoft Project's task percent complete and status fields. Any custom fields on TB_Task__c discovered during schema discovery map to Microsoft Project custom fields (Text, Number, Date, or Flag types depending on source data type).

TeamBoard Resources (team members and equipment) map to Microsoft Project resources. Allocation percentage and assignment dates transfer to Resource Assignments in Microsoft Project. We resolve the Salesforce User reference in TB_Resource__c by email match to a Microsoft Project resource entry. Capacity (hours per day) maps to the resource Max Units field. Material resources map as material resources in Microsoft Project with the Units field set to the quantity.

The TeamBoard assignment record links a Resource to a Work Item or Task with allocation percentage and date range. Microsoft Project Assignment rows capture Resource, Task, Units (allocation %), Start, and Finish. We create one Assignment per TB_TaskAssignment__c record, resolving the Task reference to the migrated Microsoft Project task ID and the Resource reference to the migrated Microsoft Project resource. This preserves who was assigned and at what allocation level.

Time entries logged against Work Items or Tasks in TeamBoard map to Actual Work on the corresponding Task Assignment in Microsoft Project. The hours, date, and user reference transfer as actual work logged on the task assignment row. TeamBoard's time entry notes map as assignment remarks. Because Microsoft Project does not have a timesheet approval workflow, the approval status from TeamBoard (Pending, Approved, Rejected) is preserved in a custom column field for admin reference but does not replicate an approval state in the destination.

TeamBoard timesheets aggregate time entries into weekly or period-based views with an approval workflow. Microsoft Project does not have a native timesheet object; we export the timesheet records with their weekly totals, approval status, and linked time entries as a structured CSV and JSON deliverable alongside the project plan. The customer's admin can import this into Microsoft 365 Timesheet (part of Project Online) or a third-party time tracking system.

TeamBoard Portfolios group multiple projects for oversight and are stored with a junction object linking to TB_Project__c. In Microsoft Project Plan 5 or Project Online, portfolio-level grouping maps to Enterprise Project Types or Programs within Project Web App. We preserve the Portfolio name and the set of projects assigned to each Portfolio as a structured mapping deliverable. The customer configures the enterprise project structure in Project Online after migration.

TeamBoard vacation approval workflow creates calendar entries linked to Resources representing approved time off. Microsoft Project Resource Calendars support calendar exceptions (holidays and non-working time). We map approved vacation entries to Resource Calendar Exceptions so that resource availability in Microsoft Project reflects the same non-working periods as TeamBoard. Pending and rejected vacation requests are excluded from the calendar mapping and flagged in the reconciliation report.

TeamBoard custom fields extend its Salesforce custom objects with additional properties. We perform field-level discovery during schema enumeration, then map each custom field to the equivalent Microsoft Project custom field type: Text fields to Text, numeric fields to Number, date fields to Date, and checkbox fields to Flag. Custom fields that do not have a direct Microsoft Project equivalent are included in the migration as an XML column tag so the customer can map them post-import. The custom field mapping document is part of the handoff package.

TeamBoard reports are configured as Salesforce report types against TeamBoard custom objects. Report definitions cannot be exported as structured data. We export the underlying data that feeds each report as CSV so the customer can rebuild equivalent reports in Microsoft Project (using Project Online native reporting or Power BI with the Project Data Connector). We deliver a report inventory listing every TeamBoard report by name, its source object, and the recommended Power BI or Project Online rebuild approach.