Migrate your ProjectFlow data
Project and portfolio management platform from Fortes Nordic with Microsoft 365 and AI integration, supporting both agile and traditional methods across grow, professional, and enterprise tiers.
In its favor
Why people choose ProjectFlow
The signal that keeps ProjectFlow on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Lowest visible per-seat cost among Danish PPM tools with enterprise-tier features like multicompany structure and resource planning available on higher tiers.
Native support for both agile and traditional project management methods in a single environment, avoiding the need for multiple tools.
Strong Microsoft 365 integration including Power BI reporting, appealing to organisations already invested in the Microsoft ecosystem.
Three-tier model lets small teams start with the Grow tier and expand to Professional or Enterprise as project complexity grows without changing platforms.
Positive review themes cite the intuitive interface and ease of use as primary reasons for adoption on G2, with 91% of reviewers rating it above 4 stars.
CSV export is currently the only documented export mechanism, making migrations of large portfolios time-consuming and error-prone without dedicated tooling.
Workflow export produces a zip file rather than a machine-readable format, requiring manual re-creation of complex workflow definitions in the destination system.
No public API documentation was found during research, limiting integration options and preventing automated migration pipelines for customers with real-time data requirements.
Enterprise tier required for multicompany structures and advanced resource planning, pushing smaller teams toward platforms with these features included at lower tiers.
Reasons to switch
Why people leave ProjectFlow
The recurring reasons buyers give for replacing ProjectFlow. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where ProjectFlow 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
ProjectFlow pricing overview
ProjectFlow uses a per-user per-month model with at least three tiers. The Grow tier is visible at approximately $7.91/user/month. Professional and Enterprise tiers require a sales contact for pricing. All tiers include a 14-day free trial with no payment information required upfront.
Grow
Tier 1 of 3
$7.91/user/month
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on ProjectFlow's schedule — see our quote-based pricing →
What gets migrated
ProjectFlow object support
Object-by-object support for ProjectFlow migrations. Per-pair details surface during scoping.
Projects
Fully supportedProjects are the primary container in ProjectFlow, containing all tasks, documents, and schedules. The standard Project object with dates, status, and metadata migrates cleanly to most destination platforms.
Tasks
Fully supportedTasks within projects map 1:1 to destination task objects. We preserve assignee, due date, status, and priority. Custom task fields are mapped individually during the scoping phase.
Subtasks
Mapping requiredSubtask nesting depth varies by tier. We flag when subtask hierarchies exceed the destination's supported depth and flatten or re-parent records accordingly during migration.
Milestones
Fully supportedMilestones are standalone date-driven markers within a project. We preserve the milestone name, target date, and linked tasks across the migration.
GanttCharts
Mapping requiredGantt structure—task bars, start/end dates, dependencies—is extracted and reconstructed in the destination. Dependencies that do not exist in the target are linked as custom dependency fields.
Documents
Fully supportedDocuments are linked to projects and can be nested inside DocumentFolders. We export document metadata and file references; actual file transfer uses the customer's preferred storage path.
DocumentFolders
Fully supportedThe folder hierarchy is preserved as a flat list of parent-child relationships and recreated in the destination using the same folder structure conventions.
DailyReports
Mapping requiredDailyReports are a construction-industry-specific object recording daily progress notes. We map these to the destination's closest equivalent (notes, journal entries, or comments) and flag any loss of structured fields.
Alerts
Mapping requiredAlert thresholds and notification rules are platform-specific. We extract alert configurations and attempt to recreate them in the destination as task reminder settings or automation rules where supported.
ProjectShares
Mapping requiredProjectShares control which users or external parties have access to a project. We map these to the destination's sharing or permission model, noting where role definitions differ.
Assignees
Fully supportedUser assignments on tasks and projects map to the destination's assignee field. Enterprise multicompany structures may require disambiguation of duplicate user records.
Custom Fields
Mapping requiredCustom fields on Projects and Tasks vary by tier and configuration. We enumerate all custom fields during discovery and map them to equivalent custom fields or note where the destination lacks the field type.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Projects are the primary container in ProjectFlow, containing all tasks, documents, and schedules. The standard Project object with dates, status, and metadata migrates cleanly to most destination platforms. |
| Tasks | Fully supported | Tasks within projects map 1:1 to destination task objects. We preserve assignee, due date, status, and priority. Custom task fields are mapped individually during the scoping phase. |
| Subtasks | Mapping required | Subtask nesting depth varies by tier. We flag when subtask hierarchies exceed the destination's supported depth and flatten or re-parent records accordingly during migration. |
| Milestones | Fully supported | Milestones are standalone date-driven markers within a project. We preserve the milestone name, target date, and linked tasks across the migration. |
| GanttCharts | Mapping required | Gantt structure—task bars, start/end dates, dependencies—is extracted and reconstructed in the destination. Dependencies that do not exist in the target are linked as custom dependency fields. |
| Documents | Fully supported | Documents are linked to projects and can be nested inside DocumentFolders. We export document metadata and file references; actual file transfer uses the customer's preferred storage path. |
| DocumentFolders | Fully supported | The folder hierarchy is preserved as a flat list of parent-child relationships and recreated in the destination using the same folder structure conventions. |
| DailyReports | Mapping required | DailyReports are a construction-industry-specific object recording daily progress notes. We map these to the destination's closest equivalent (notes, journal entries, or comments) and flag any loss of structured fields. |
| Alerts | Mapping required | Alert thresholds and notification rules are platform-specific. We extract alert configurations and attempt to recreate them in the destination as task reminder settings or automation rules where supported. |
| ProjectShares | Mapping required | ProjectShares control which users or external parties have access to a project. We map these to the destination's sharing or permission model, noting where role definitions differ. |
| Assignees | Fully supported | User assignments on tasks and projects map to the destination's assignee field. Enterprise multicompany structures may require disambiguation of duplicate user records. |
| Custom Fields | Mapping required | Custom fields on Projects and Tasks vary by tier and configuration. We enumerate all custom fields during discovery and map them to equivalent custom fields or note where the destination lacks the field type. |
Gotchas
What to watch for in ProjectFlow migrations
Issues we've hit on past ProjectFlow migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No documented public REST API for automated exports
DailyReports object is construction-industry specific
Enterprise multicompany structure complicates user deduplication
| Severity | Issue |
|---|---|
| High | No documented public REST API for automated exports |
| Medium | DailyReports object is construction-industry specific |
| Medium | Enterprise multicompany structure complicates user deduplication |
Leaving ProjectFlow?
Where ProjectFlow customers move next
5 destinations ProjectFlow can migrate to.
How a ProjectFlow migration works
Four steps, ProjectFlow-specific
Connect
Not publicly documented into ProjectFlow. Scopes limited to read-only on the data we move.
Map
We translate ProjectFlow-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate ProjectFlow quirks before production.
Migrate
Full migration with ProjectFlow rate-limit handling. Rollback available throughout.
FAQ
ProjectFlow migration FAQ
Answers to the questions buyers ask most during ProjectFlow migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your ProjectFlow 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 ProjectFlow.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your ProjectFlow setup and destination — written quote back within a business day.