Migrate your BrightWork data
SharePoint-native PPM layer that adds portfolio dashboards, templates, and RAID tracking to Microsoft 365. Built for enterprises already invested in SharePoint who need structured project visibility without leaving the Microsoft ecosystem.
In its favor
Why people choose BrightWork
The signal that keeps BrightWork on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
BrightWork extends SharePoint with structured PPM templates and dashboards, making it natural for Microsoft 365 shops that want project management without leaving the Office ecosystem.
Customers like Police Credit Union and County of Wellington chose BrightWork because the ability to roll up multiple projects into a single executive status report gave senior leadership visibility without manual consolidation.
AmSurg selected BrightWork for its portfolio-level reporting, where multiple projects all roll up to one dashboard viewable by executives and project sponsors.
Organizations with existing SharePoint infrastructure chose BrightWork to add project and program management capabilities on top of a platform they already administered without additional licensing costs.
BrightWork's structured templates and RAID logging provide a repeatable framework for project managers who need consistency across project teams.
Some customers find BrightWork too tightly coupled to SharePoint—upgrades, permissions management, and site administration become complex and require SharePoint expertise.
G2 reviewers note that BrightWork provides only marginal improvements over vanilla SharePoint, leading teams to question the value of the premium over a well-configured SharePoint intranet.
Customers report that many financial and advanced reporting features are locked behind higher pricing tiers, making the entry-level plan limiting for mid-sized PMOs.
Organizations outgrowing SharePoint-native project management look for platforms with stronger native API support, more modern UX, and built-in resource management.
Reasons to switch
Why people leave BrightWork
The recurring reasons buyers give for replacing BrightWork. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where BrightWork 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
BrightWork pricing overview
BrightWork does not publish pricing on its website and requires prospective customers to contact sales. Pricing is tiered with Essential, Professional, and Enterprise levels, and supports both per-user and site-license models depending on deployment type.
Essential
Tier 1 of 3
Contact sales
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on BrightWork's schedule — see our quote-based pricing →
What gets migrated
BrightWork object support
Object-by-object support for BrightWork migrations. Per-pair details surface during scoping.
Projects
Fully supportedBrightWork Projects are the primary container. They map cleanly to Projects in most destination platforms. We preserve the project name, description, start/end dates, assigned Project Manager, and custom field values exported from SharePoint lists.
Project Areas
Mapping requiredProject Areas are SharePoint subsites that serve as the project workspace. Where the destination does not have an equivalent concept, we flatten the area structure into the parent Project record and preserve area-level settings as custom fields.
Programs
Mapping requiredPrograms group multiple Projects and roll up to a portfolio-level Status Report. We map Programs to Programs or Portfolios in the destination and link their child Projects accordingly.
Portfolio Status Reports
Mapping requiredBrightWork aggregates project status into a single portfolio-level report. We extract the report data and write it to the destination as a summary record linked to the associated Projects.
Tasks and Subtasks
Fully supportedTasks carry standard fields: name, start date, due date, % complete, priority, assigned owner, and predecessor links. We map these 1:1 into Tasks in the destination platform, preserving the parent-child hierarchy.
Custom Fields
Mapping requiredBrightWork allows per-project custom fields defined within SharePoint lists. We export all custom field definitions and values alongside the parent object and map them to equivalent custom fields or properties in the destination.
RAID Logs (Risks, Assumptions, Issues, Dependencies)
Mapping requiredRAID is a named log object in BrightWork with separate entries for Risks, Assumptions, Issues, and Dependencies. We map these to equivalent Risk/Issue/Dependency objects in the destination or to a custom tracker if the platform does not have a native RAID concept.
Attachments
Fully supportedBrightWork stores file attachments within SharePoint document libraries. We extract the binary files and re-upload them to the destination platform, preserving folder structure and linking them to the parent Project or Task record.
Time Tracking
Mapping requiredTime entries in BrightWork are logged against Tasks. We map these to Time Entries or Work Logs in the destination, preserving the hours, date, and user association.
Document Libraries
Mapping requiredSharePoint document libraries within a Project Area are exported as file sets. We map these to Documents or Files attached to the corresponding Project record in the destination.
SharePoint Lists (general export/import)
Mapping requiredBrightWork supports list export and import including attachments for migrating data between lists. We leverage this for structured data extraction but handle the target-side loading directly to avoid SharePoint-only re-imports.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | BrightWork Projects are the primary container. They map cleanly to Projects in most destination platforms. We preserve the project name, description, start/end dates, assigned Project Manager, and custom field values exported from SharePoint lists. |
| Project Areas | Mapping required | Project Areas are SharePoint subsites that serve as the project workspace. Where the destination does not have an equivalent concept, we flatten the area structure into the parent Project record and preserve area-level settings as custom fields. |
| Programs | Mapping required | Programs group multiple Projects and roll up to a portfolio-level Status Report. We map Programs to Programs or Portfolios in the destination and link their child Projects accordingly. |
| Portfolio Status Reports | Mapping required | BrightWork aggregates project status into a single portfolio-level report. We extract the report data and write it to the destination as a summary record linked to the associated Projects. |
| Tasks and Subtasks | Fully supported | Tasks carry standard fields: name, start date, due date, % complete, priority, assigned owner, and predecessor links. We map these 1:1 into Tasks in the destination platform, preserving the parent-child hierarchy. |
| Custom Fields | Mapping required | BrightWork allows per-project custom fields defined within SharePoint lists. We export all custom field definitions and values alongside the parent object and map them to equivalent custom fields or properties in the destination. |
| RAID Logs (Risks, Assumptions, Issues, Dependencies) | Mapping required | RAID is a named log object in BrightWork with separate entries for Risks, Assumptions, Issues, and Dependencies. We map these to equivalent Risk/Issue/Dependency objects in the destination or to a custom tracker if the platform does not have a native RAID concept. |
| Attachments | Fully supported | BrightWork stores file attachments within SharePoint document libraries. We extract the binary files and re-upload them to the destination platform, preserving folder structure and linking them to the parent Project or Task record. |
| Time Tracking | Mapping required | Time entries in BrightWork are logged against Tasks. We map these to Time Entries or Work Logs in the destination, preserving the hours, date, and user association. |
| Document Libraries | Mapping required | SharePoint document libraries within a Project Area are exported as file sets. We map these to Documents or Files attached to the corresponding Project record in the destination. |
| SharePoint Lists (general export/import) | Mapping required | BrightWork supports list export and import including attachments for migrating data between lists. We leverage this for structured data extraction but handle the target-side loading directly to avoid SharePoint-only re-imports. |
Gotchas
What to watch for in BrightWork migrations
Issues we've hit on past BrightWork migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No public REST API for programmatic data access
SharePoint versioning can break list export formats
Custom fields are SharePoint list columns, not a defined schema
| Severity | Issue |
|---|---|
| High | No public REST API for programmatic data access |
| Medium | SharePoint versioning can break list export formats |
| Medium | Custom fields are SharePoint list columns, not a defined schema |
Leaving BrightWork?
Where BrightWork customers move next
5 destinations BrightWork can migrate to.
How a BrightWork migration works
Four steps, BrightWork-specific
Connect
Not publicly documented into BrightWork. Scopes limited to read-only on the data we move.
Map
We translate BrightWork-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate BrightWork quirks before production.
Migrate
Full migration with BrightWork rate-limit handling. Rollback available throughout.
FAQ
BrightWork migration FAQ
Answers to the questions buyers ask most during BrightWork migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your BrightWork 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 BrightWork.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your BrightWork setup and destination — written quote back within a business day.