Migrate your Forecast data
AI-augmented project management and resource planning platform for professional services teams that want integrated scheduling, time tracking, and financial visibility in one tool.
In its favor
Why people choose Forecast
The signal that keeps Forecast on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
All-in-one integration replaces separate tools for project planning, resource allocation, and financial tracking, cutting context-switching for project managers.
AI-assisted resource allocation and utilization reporting surface over- and under-loaded team members without manual spreadsheet work.
Clean, modern interface makes it easy to onboard new project managers and share schedule views with non-technical stakeholders.
Visual availability grid displays team capacity at a glance, helping managers staff projects without drilling into individual calendars.
Time tracking is built directly into the platform, meaning billing data is always in sync with the schedule.
Customization options are limited and hard to work around, especially for organizations with non-standard workflows that do not fit Forecast's opinionated structure.
The interface becomes restrictive when multiple users need to work simultaneously, with limited real-time collaboration features noted by larger teams.
No free tier or publicly available pricing forces a sales conversation before teams can evaluate fit, which slows down procurement for smaller organizations.
Scalability is a concern for larger organizations; the tool works well for small and mid-sized teams but begins to strain as project count and user count grow.
Reasons to switch
Why people leave Forecast
The recurring reasons buyers give for replacing Forecast. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Forecast 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
Forecast pricing overview
Forecast uses a single, all-inclusive pricing tier with no public per-seat rate. Pricing is negotiated based on user count and contract duration, and there is no free tier or self-serve trial — every evaluation requires engaging the sales team directly.
Single Plan
Tier 1 of 1
Custom (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 Forecast's schedule — see our quote-based pricing →
What gets migrated
Forecast object support
Object-by-object support for Forecast migrations. Per-pair details surface during scoping.
Projects
Fully supportedProjects are the top-level container in Forecast, holding Phases, Tasks, and Milestones. We export the full project record including status, dates, and custom properties and land it as a top-level project or workspace in the destination. Nesting is preserved via the parent_id linkage at migration time.
Phases
Fully supportedPhases are mid-level groupings within a Project, used to chunk large work streams. We map Phases to the equivalent grouping construct in your destination (e.g., project phases, sprints, or milestones) and preserve their ordering relative to the parent Project.
Tasks
Fully supportedTasks are the leaf-level work items in Forecast, each assigned a status, assignee, due date, and optional time estimate. We map Tasks 1:1 into the destination task or issue object, preserving the status enum mapping and owner assignment.
Milestones
Fully supportedMilestones in Forecast represent key target dates tied to a Project. We export the milestone name, target date, and parent project reference, landing them as milestones or pinned deadlines in the destination system.
Custom Fields
Mapping requiredCustom Fields can be applied to Projects, Phases, Tasks, and Time Registrations. They support text, numeric, and choice types. During migration scoping we identify every non-standard field and map it to the equivalent custom property in the destination, applying the same field type and choice options.
Time Registrations
Mapping requiredTime entries in Forecast are linked to a Task (or a Project for non-task logging) and carry hours, a date, a billable flag, and optionally a rate. We map these to time entries in the destination, preserving the billable flag and associating each entry with the migrated task record.
Rate Cards
Mapping requiredRate Cards define hourly billing rates per role or person in Forecast. We export the rate card structure and rate values, then map them to the equivalent billing rate or cost table in the destination. Multi-currency rates are converted at the exchange rate active on the migration date unless a different rate is specified.
Resource Assignments
Mapping requiredForecast assigns team members to tasks with an allocated percentage or hours. We extract the assignment records and re-link them to the corresponding migrated tasks and users, flagging any orphaned assignments where the user has not been migrated.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Projects are the top-level container in Forecast, holding Phases, Tasks, and Milestones. We export the full project record including status, dates, and custom properties and land it as a top-level project or workspace in the destination. Nesting is preserved via the parent_id linkage at migration time. |
| Phases | Fully supported | Phases are mid-level groupings within a Project, used to chunk large work streams. We map Phases to the equivalent grouping construct in your destination (e.g., project phases, sprints, or milestones) and preserve their ordering relative to the parent Project. |
| Tasks | Fully supported | Tasks are the leaf-level work items in Forecast, each assigned a status, assignee, due date, and optional time estimate. We map Tasks 1:1 into the destination task or issue object, preserving the status enum mapping and owner assignment. |
| Milestones | Fully supported | Milestones in Forecast represent key target dates tied to a Project. We export the milestone name, target date, and parent project reference, landing them as milestones or pinned deadlines in the destination system. |
| Custom Fields | Mapping required | Custom Fields can be applied to Projects, Phases, Tasks, and Time Registrations. They support text, numeric, and choice types. During migration scoping we identify every non-standard field and map it to the equivalent custom property in the destination, applying the same field type and choice options. |
| Time Registrations | Mapping required | Time entries in Forecast are linked to a Task (or a Project for non-task logging) and carry hours, a date, a billable flag, and optionally a rate. We map these to time entries in the destination, preserving the billable flag and associating each entry with the migrated task record. |
| Rate Cards | Mapping required | Rate Cards define hourly billing rates per role or person in Forecast. We export the rate card structure and rate values, then map them to the equivalent billing rate or cost table in the destination. Multi-currency rates are converted at the exchange rate active on the migration date unless a different rate is specified. |
| Resource Assignments | Mapping required | Forecast assigns team members to tasks with an allocated percentage or hours. We extract the assignment records and re-link them to the corresponding migrated tasks and users, flagging any orphaned assignments where the user has not been migrated. |
Gotchas
What to watch for in Forecast migrations
Issues we've hit on past Forecast migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No public pricing or self-serve trial
CSV-only data export covers a subset of objects
No documented public API for bulk operations
Custom Fields require field-level mapping at destination
Multi-user concurrent editing is limited
| Severity | Issue |
|---|---|
| High | No public pricing or self-serve trial |
| High | CSV-only data export covers a subset of objects |
| Medium | No documented public API for bulk operations |
| Medium | Custom Fields require field-level mapping at destination |
| Low | Multi-user concurrent editing is limited |
Leaving Forecast?
Where Forecast customers move next
5 destinations Forecast can migrate to.
How a Forecast migration works
Four steps, Forecast-specific
Connect
API key (available on request or via developer account) into Forecast. Scopes limited to read-only on the data we move.
Map
We translate Forecast-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Forecast quirks before production.
Migrate
Full migration with Forecast rate-limit handling. Rollback available throughout.
FAQ
Forecast migration FAQ
Answers to the questions buyers ask most during Forecast migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Forecast 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 Forecast.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Forecast setup and destination — written quote back within a business day.