Migrate your TeamGantt data
Gantt-first project planning tool with drag-and-drop scheduling and a generous free tier. Teams who need visual timelines and simple task dependencies love it; teams needing robust resource management or multi-project portfolios hit walls quickly.
In its favor
Why people choose TeamGantt
The signal that keeps TeamGantt on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Teams choose TeamGantt because the drag-and-drop Gantt chart interface requires almost no training to get productive, especially for visual planners who think in timelines.
The free tier offers unlimited tasks and projects with no time limit, letting small teams validate the tool before committing to a paid plan.
Resource allocation and timeline visibility are straightforward—one review highlights how TeamGantt makes assigning people to tasks 'straightforward' and keeps everyone aligned.
Small agencies and construction firms cite the simple pricing per-project model as a reason to switch, especially compared to per-seat pricing in enterprise tools.
The template library and pre-built project structures reduce setup time for recurring project types like marketing campaigns or construction schedules.
Teams report that resource management is limited—workload views are paywalled behind Pro and the capacity planning features are basic compared to dedicated resource management tools.
The lack of a native macOS desktop app frustrates users who want a full-screen experience; the iPad/iPhone app is described as small and insufficient for complex project management.
Integration ecosystem is narrow—Zapier is the primary no-code integration path, and teams needing native bi-directional sync with tools like Salesforce or QuickBooks find themselves building custom API workarounds.
Some teams find collaboration features lacking—particularly threaded discussions, @mentions, and shared document editing that modern PM tools bundle in.
As teams scale beyond 5–10 concurrent projects, the per-project pricing model becomes expensive and teams report looking for unlimited-project plans or portfolio-level views that TeamGantt Basic and Standard do not offer.
Reasons to switch
Why people leave TeamGantt
The recurring reasons buyers give for replacing TeamGantt. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where TeamGantt 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
TeamGantt pricing overview
TeamGantt uses a per-project model on Basic and Standard tiers, switching to per-manager pricing on Pro. Business and Construction plans offer unlimited users and projects at negotiated rates. The free tier is feature-rich but caps at 1 user and provides no API access, making paid-plan access critical for programmatic migration.
Free
Tier 1 of 5
Free
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on TeamGantt's schedule — see our quote-based pricing →
What gets migrated
TeamGantt object support
Object-by-object support for TeamGantt migrations. Per-pair details surface during scoping.
Projects
Fully supportedProjects are the top-level container. A project's start date is inferred from its first task; its end date from the last task. We preserve all project-level settings, custom fields, and the project timeline during migration.
Tasks
Fully supportedTasks are the primary scheduling unit. We map all task fields: name, start/end dates, duration, percent complete, notes, assignees, and custom fields. Subtasks are nested via groups.
Dependencies
Fully supportedTask dependencies define predecessor/successor relationships and drive automatic rescheduling. We preserve all Finish-to-Start, Start-to-Start, and lag-time relationships as the API exposes them.
Milestones
Fully supportedMilestones are zero-duration markers. We preserve their names, dates, and associations to the parent project and task groups.
Baselines
Fully supportedBaselines capture a snapshot of the original planned schedule. We export all saved baselines so the destination can reflect what was originally planned vs. actual progress.
Time Entries
Mapping requiredTracked time is accessible via API and CSV export but requires mapping to the destination's time-entry schema. Hourly estimation preferences affect how dates are set on new tasks and must be reviewed during scoping.
Workloads
Mapping requiredWorkloads report is only available on Pro and Unlimited plans. We can export user/task assignments and hours as a CSV, then map them to the destination's resource-management structure.
Checklists
Fully supportedChecklist items on tasks are accessible via the API. We preserve the checklist structure and completion status alongside each parent task.
Users
Mapping requiredUsers and labels are tracked as task resources. We map each user record including name, email, and assignment history. Guest vs. full-user roles affect what data they can access.
Labels
Fully supportedLabels are a resource type used for grouping or categorizing tasks. We preserve label names and their assignments across all tasks.
Discussions
Fully supportedDiscussion threads attached to tasks are accessible via the API. We carry the full comment history, timestamps, and author attribution.
Custom Fields
Mapping requiredCustom fields exist at the project level and task level. We discover their field types and values via API and map them to equivalent custom fields in the destination, handling type mismatches (text, number, date, choice) explicitly.
Private Tasks
Mapping requiredTasks in projects a user is not invited to appear as 'Private' to that user. We flag which tasks may be inaccessible under the current authentication and advise on inviting the migration account to all relevant projects before export.
Groups (Subtasks)
Fully supportedGroups of tasks represent the subtask hierarchy. We preserve the group structure, names, and nesting depth, ensuring parent-child date relationships are maintained.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Projects are the top-level container. A project's start date is inferred from its first task; its end date from the last task. We preserve all project-level settings, custom fields, and the project timeline during migration. |
| Tasks | Fully supported | Tasks are the primary scheduling unit. We map all task fields: name, start/end dates, duration, percent complete, notes, assignees, and custom fields. Subtasks are nested via groups. |
| Dependencies | Fully supported | Task dependencies define predecessor/successor relationships and drive automatic rescheduling. We preserve all Finish-to-Start, Start-to-Start, and lag-time relationships as the API exposes them. |
| Milestones | Fully supported | Milestones are zero-duration markers. We preserve their names, dates, and associations to the parent project and task groups. |
| Baselines | Fully supported | Baselines capture a snapshot of the original planned schedule. We export all saved baselines so the destination can reflect what was originally planned vs. actual progress. |
| Time Entries | Mapping required | Tracked time is accessible via API and CSV export but requires mapping to the destination's time-entry schema. Hourly estimation preferences affect how dates are set on new tasks and must be reviewed during scoping. |
| Workloads | Mapping required | Workloads report is only available on Pro and Unlimited plans. We can export user/task assignments and hours as a CSV, then map them to the destination's resource-management structure. |
| Checklists | Fully supported | Checklist items on tasks are accessible via the API. We preserve the checklist structure and completion status alongside each parent task. |
| Users | Mapping required | Users and labels are tracked as task resources. We map each user record including name, email, and assignment history. Guest vs. full-user roles affect what data they can access. |
| Labels | Fully supported | Labels are a resource type used for grouping or categorizing tasks. We preserve label names and their assignments across all tasks. |
| Discussions | Fully supported | Discussion threads attached to tasks are accessible via the API. We carry the full comment history, timestamps, and author attribution. |
| Custom Fields | Mapping required | Custom fields exist at the project level and task level. We discover their field types and values via API and map them to equivalent custom fields in the destination, handling type mismatches (text, number, date, choice) explicitly. |
| Private Tasks | Mapping required | Tasks in projects a user is not invited to appear as 'Private' to that user. We flag which tasks may be inaccessible under the current authentication and advise on inviting the migration account to all relevant projects before export. |
| Groups (Subtasks) | Fully supported | Groups of tasks represent the subtask hierarchy. We preserve the group structure, names, and nesting depth, ensuring parent-child date relationships are maintained. |
Gotchas
What to watch for in TeamGantt migrations
Issues we've hit on past TeamGantt migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Project billing model charges per project on Basic tier
Workloads report requires Pro or Unlimited plan
Free plan exports are limited to CSV with no API access
Project start date is inferred, not set explicitly
Time zone and language handling for non-Latin characters
| Severity | Issue |
|---|---|
| High | Project billing model charges per project on Basic tier |
| Medium | Workloads report requires Pro or Unlimited plan |
| Medium | Free plan exports are limited to CSV with no API access |
| Low | Project start date is inferred, not set explicitly |
| Low | Time zone and language handling for non-Latin characters |
Leaving TeamGantt?
Where TeamGantt customers move next
5 destinations TeamGantt can migrate to.
How a TeamGantt migration works
Four steps, TeamGantt-specific
Connect
OAuth 2.0 into TeamGantt. Scopes limited to read-only on the data we move.
Map
We translate TeamGantt-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate TeamGantt quirks before production.
Migrate
Full migration with TeamGantt rate-limit handling. Rollback available throughout.
FAQ
TeamGantt migration FAQ
Answers to the questions buyers ask most during TeamGantt migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your TeamGantt 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 TeamGantt.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your TeamGantt setup and destination — written quote back within a business day.