Migrate from Thrive to Microsoft Project

Thrive Projects map directly to Microsoft Project plans. Project metadata including name, description, status, start date, target date, and team assignments migrate as project-level fields. Active projects migrate as working plans; archived projects migrate as read-only plans for historical reference. We preserve the Thrive project identifier in a custom Project field for cross-system reconciliation.

Thrive Tasks map to Microsoft Project Task rows with WBS hierarchy preserved. Task name, description, status, start date, finish date, percent complete, priority, and assignee migrate. Task dependencies (Finish-to-Start, Start-to-Start, etc.) migrate as predecessor links in Microsoft Project. We validate dependency integrity during migration to avoid circular reference errors that would corrupt the schedule.

Thrive's forecasting module stores predictive data (forecast amounts, dates, confidence intervals, model parameters). These do not have a direct Microsoft Project equivalent because Project uses baseline tracking rather than a forecasting engine. We map forecast amounts to custom numeric fields on tasks and projects, forecast dates to baseline start and finish fields, and we document the full forecasting record schema in a handoff note so the customer's admin can rebuild rollup calculations in Project using Power BI or a dedicated forecasting tool.

Thrive Users and Teams map to Microsoft Project Resources. Individual named users map to Material Resources or Work Resources with their email as the resource ID. Teams that span multiple users map to a single Resource Group entry with a naming convention that preserves the team name. Resource calendars (working time, exceptions, leave) require separate mapping if Thrive stores that data; Microsoft Project resource calendars are set up manually or imported from a CSV during the resource pool configuration phase.

Thrive custom objects require field-level inspection during discovery. Each custom object field maps to a Microsoft Project custom field of equivalent type (Text, Number, Date, Flag, Cost, or Outline Code). Enterprise-level custom objects with lookup relationships map to Enterprise Custom Fields with look-up tables configured in the destination Project Online instance. We pre-create the custom field schema in the destination before data migration begins.

Thrive historical activity logs (timestamps, status changes, comments, operational events) migrate as Task Notes in Microsoft Project, ordered by timestamp. For projects with heavy activity history, we create a Summary Task at the top of each project plan titled 'Historical Activity Log' with the relevant events as notes on that task. This preserves the audit trail without cluttering the working schedule.

Thrive's Power BI integration connects operational data to Power BI dashboards. This integration does not migrate because it is a platform-level connection, not a data record. We document the active Power BI reports, dataset queries, and dashboard IDs connected to Thrive so the customer's Power BI admin can re-establish connections to the migrated Microsoft Project data after cutover.

Thrive integrations with external accounting and POS platforms (documented during discovery) require re-establishment in Microsoft Project's ecosystem. We deliver a written inventory of every active integration point, its trigger and action, and recommended replacement configuration using Power Automate or direct API connection. We do not configure Power Automate flows as part of the standard migration scope.

If Thrive Learning variants are in use, SCORM packages and course metadata do not map directly to Microsoft Project objects. We export SCORM packages and learning content as a zip archive during extraction and deliver it alongside the migration handoff. The customer's LMS admin re-uploads content to the destination learning platform. Project-level training requirements migrate as tasks or milestones with due dates.

Thrive sync jobs for large inventories or complex datasets run for hours and use hard-overwrite semantics. Microsoft Project does not have a live sync equivalent. We extract the final Thrive dataset as a structured export and import it into Microsoft Project as an MPP file or CSV schedule. The import runs outside business hours to avoid production disruptions, matching the approach used for Thrive's own sync scheduling.