Migrate your Project Insight data
Portfolio-first project and program management platform with AI scheduling and enterprise automation. The migration story centers on reporting exports and cross-tool integrations rather than a full API data dump.
In its favor
Why people choose Project Insight
The signal that keeps Project Insight on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Free tier with unlimited projects and tasks gives small teams a way to validate the platform before committing to a paid plan.
Weekly live office hours and free training sessions reduce the perceived risk of adoption for teams without a dedicated administrator.
Cross-software time tracking lets distributed teams log time from multiple external tools into a single project timeline.
Microsoft Project Online migration documentation and import guides make it a natural destination for teams leaving that ecosystem.
Configurable reports aggregate project performance and resource allocation across the entire portfolio in one view.
Performance and reliability complaints — users report the UI being slow, glitching, and unresponsive during normal use.
Limited customization outside the free tier — custom fields are restricted to Pro, and many configuration choices are constrained by plan edition.
Steep onboarding and setup time — reviewers describe spending weeks learning the system before extracting full value from it.
Inability to attach video files to project templates, limiting certain types of project documentation workflows.
Integration with non-Microsoft tools requires manual configuration and is less well-documented than the Microsoft integration.
Reasons to switch
Why people leave Project Insight
The recurring reasons buyers give for replacing Project Insight. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Project Insight fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Project Insight pricing overview
Project Insight uses a per-user, per-month pricing model. A free tier with unlimited projects and tasks is available. Paid tiers unlock custom fields at Pro ($9/user/month), resource management and API access at Standard, and AI-powered scheduling and capacity planning at Enterprise. Pricing is custom for Enterprise seats.
Free
Tier 1 of 4
$0
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Project Insight's schedule — see our quote-based pricing →
What gets migrated
Project Insight object support
Object-by-object support for Project Insight migrations. Per-pair details surface during scoping.
Projects
Fully supportedProjects are the primary container in Project Insight. They export cleanly via the built-in report export to Excel or CSV. We map the project record including status, dates, and description fields to the target project's standard fields.
Tasks
Fully supportedTasks export via the task-level report with hierarchy (parent-child relationships) preserved through a flattened path or indent structure. We reconstruct the WBS tree in the target system using predecessor and successor references.
Resources
Fully supportedResource records map to the target system's people or resource pool objects. We pull name, role, availability, and allocation percentage from Project Insight's resource management reports.
Custom Fields
Mapping requiredCustom fields are available on the Pro plan and above. Their values export within the same row as the parent object (Project or Task). We map each named custom field to an equivalent custom property in the destination, flagging any fields with unsupported data types for manual handling.
Time Entries
Fully supportedTime tracking is a named feature area with its own report type. We export time entries linked to their parent Project and Task, preserving hours, date, and resource attribution. Not all plans include time tracking — we confirm feature availability during scoping.
Constraints
Mapping requiredProject Insight supports scheduling constraint types (ASAP, Finish No Earlier Than, Finish No Later Than, and others) set per task. These export as a constraint type field. We carry them as metadata into the destination task; the target system's constraint handling may require interpretation or manual reapplication.
Portfolios
Mapping requiredPortfolios and programs group multiple Projects in Project Insight. The grouping structure exports as a portfolio-to-project association table. We map this to the destination's portfolio or program object, preserving the hierarchy where the target supports it.
Attachments
Not in this platformFile attachments stored within Project Insight are not accessible via the report export. We do not migrate binary attachments directly. We recommend a parallel document migration workflow for files stored in Project Insight.
Dependencies
Mapping requiredTask-to-task predecessor relationships export via the dependency report. We translate these into the target system's dependency format, noting any destination that does not support the same constraint-based dependency logic.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Projects are the primary container in Project Insight. They export cleanly via the built-in report export to Excel or CSV. We map the project record including status, dates, and description fields to the target project's standard fields. |
| Tasks | Fully supported | Tasks export via the task-level report with hierarchy (parent-child relationships) preserved through a flattened path or indent structure. We reconstruct the WBS tree in the target system using predecessor and successor references. |
| Resources | Fully supported | Resource records map to the target system's people or resource pool objects. We pull name, role, availability, and allocation percentage from Project Insight's resource management reports. |
| Custom Fields | Mapping required | Custom fields are available on the Pro plan and above. Their values export within the same row as the parent object (Project or Task). We map each named custom field to an equivalent custom property in the destination, flagging any fields with unsupported data types for manual handling. |
| Time Entries | Fully supported | Time tracking is a named feature area with its own report type. We export time entries linked to their parent Project and Task, preserving hours, date, and resource attribution. Not all plans include time tracking — we confirm feature availability during scoping. |
| Constraints | Mapping required | Project Insight supports scheduling constraint types (ASAP, Finish No Earlier Than, Finish No Later Than, and others) set per task. These export as a constraint type field. We carry them as metadata into the destination task; the target system's constraint handling may require interpretation or manual reapplication. |
| Portfolios | Mapping required | Portfolios and programs group multiple Projects in Project Insight. The grouping structure exports as a portfolio-to-project association table. We map this to the destination's portfolio or program object, preserving the hierarchy where the target supports it. |
| Attachments | Not in this platform | File attachments stored within Project Insight are not accessible via the report export. We do not migrate binary attachments directly. We recommend a parallel document migration workflow for files stored in Project Insight. |
| Dependencies | Mapping required | Task-to-task predecessor relationships export via the dependency report. We translate these into the target system's dependency format, noting any destination that does not support the same constraint-based dependency logic. |
Gotchas
What to watch for in Project Insight migrations
Issues we've hit on past Project Insight migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Report-based export is the only migration path
Custom Fields are Pro-plan gated
Attachment files are not exported via reports
Constraint types require manual reapplication
Performance reviews suggest stability concerns
| Severity | Issue |
|---|---|
| High | Report-based export is the only migration path |
| High | Custom Fields are Pro-plan gated |
| Medium | Attachment files are not exported via reports |
| Medium | Constraint types require manual reapplication |
| Low | Performance reviews suggest stability concerns |
Leaving Project Insight?
Where Project Insight customers move next
5 destinations Project Insight can migrate to.
How a Project Insight migration works
Four steps, Project Insight-specific
Connect
Not publicly documented in the developer resources into Project Insight. Scopes limited to read-only on the data we move.
Map
We translate Project Insight-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Project Insight quirks before production.
Migrate
Full migration with Project Insight rate-limit handling. Rollback available throughout.
FAQ
Project Insight migration FAQ
Answers to the questions buyers ask most during Project Insight migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Project Insight migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate Project Insight.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Project Insight setup and destination — written quote back within a business day.