Migrate your Freelo data
Lightweight Czech PM tool with a clear project-to-subtask hierarchy and a generous free tier for small teams. The Free plan's project and user caps are the most migration-relevant constraints.
In its favor
Why people choose Freelo
The signal that keeps Freelo on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
The generous free tier — 3 active projects, 3 users, 500 MB — lets teams trial Freelo without committing a budget, making it a common first PM tool for small agencies and startups.
The Gmail inbox integration turns email threads directly into assigned tasks with due dates, which teams managing client communication cite as their primary workflow win.
Time tracking and cost recalculation built into Tasks allow small teams to bill clients without a separate timesheet tool, whichFreelo markets as a core differentiator.
The four-level hierarchy (Projects → To-Do Lists → Tasks → Subtasks) gives teams more structural flexibility than flat boards, appealing to organizations used to Trello's limitations.
Teams with mixed technical ability appreciate the low learning curve — multiple Capterra reviews highlight Freelo as usable across age and skill diversity within the same company.
Freelo's notification and email cadence is described as aggressive by some users — weekly reports and reminders arrive without an easy opt-out, and early users report it felt spammy before discovering the filter settings.
The free tier limits teams to 3 active projects and 3 users, which becomes a hard ceiling quickly; teams that grow beyond this must upgrade to the Team plan at €80/month for the entire organization.
Some users find the menu structure unintuitive at first — multiple reviews mention a learning curve where key features are difficult to locate without getting used to the layout.
The Business module (billing, invoicing, advanced workflows) is only available on higher paid tiers and the trial period does not include a way to evaluate it before committing to a paid plan.
Reasons to switch
Why people leave Freelo
The recurring reasons buyers give for replacing Freelo. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Freelo 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
Freelo pricing overview
Freelo uses a per-organization flat rate on paid tiers rather than per-user pricing. The Team plan costs €80/month for the whole organization regardless of headcount, while the free plan limits to 3 projects and 3 users with 500 MB of storage. Enterprise pricing is custom and negotiated directly with Freelo.
Free
Tier 1 of 3
Free
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Freelo's schedule — see our quote-based pricing →
What gets migrated
Freelo object support
Object-by-object support for Freelo migrations. Per-pair details surface during scoping.
Projects
Fully supportedProjects are the top-level container in Freelo. We export them with all metadata (name, status, dates) and map them 1:1 to the destination's equivalent top-level container.
To-Do Lists
Fully supportedTo-Do Lists live inside Projects and group related Tasks. We export them with their project association and preserve the ordering as a custom ordering field in the destination.
Tasks
Fully supportedTasks are the core work unit. We map title, description, deadline, assignee, status, author, creation date, completion date, and comment count directly to the destination's task or ticket object.
Subtasks
Fully supportedSubtasks are a distinct nested object in Freelo under Tasks. We flatten them into the destination as children or linked items, preserving parent task linkage and status.
Users / Coworkers
Mapping requiredFreelo's user roster includes Admin, Project Manager, and standard Member roles. We map the name, email, and role for each user; role-based permissions may require manual configuration in the destination.
Time entries / Cost tracking
Mapping requiredFreelo tracks logged time and cost per task. We export the duration, cost value, and currency. Mapping to the destination's time-tracking schema depends on whether the destination has a native time-entry object.
Files / Attachments
Mapping requiredFreelo allows file uploads up to 100 MB per file. We export file metadata, captions, and UUIDs. Actual binary files are pulled via the API and re-uploaded to the destination; large files may require chunking.
Comments
Fully supportedComments are attached to Tasks and To-Do Lists. We export comment body, author, timestamp, and any embedded file references. Markdown formatting in Freelo comments is preserved as-is.
Notifications
Not in this platformNotifications are ephemeral in-app or email alerts tied to user activity and session state. They are not part of the project's persistent data and are not migrated.
Events / Activity log
Not in this platformFreelo's activity log tracks state changes over time but is not a persistent business record. We do not migrate it as it does not represent project content.
Out of Office records
Not in this platformOut-of-office settings are user-preference data tied to the Freelo account. They do not constitute project or task data and are not migrated.
Custom Fields
Mapping requiredFreelo supports custom fields on Tasks. We export the field name, type, and value for each record. Custom field type mapping (dropdown, number, date) depends on the destination's schema.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Projects are the top-level container in Freelo. We export them with all metadata (name, status, dates) and map them 1:1 to the destination's equivalent top-level container. |
| To-Do Lists | Fully supported | To-Do Lists live inside Projects and group related Tasks. We export them with their project association and preserve the ordering as a custom ordering field in the destination. |
| Tasks | Fully supported | Tasks are the core work unit. We map title, description, deadline, assignee, status, author, creation date, completion date, and comment count directly to the destination's task or ticket object. |
| Subtasks | Fully supported | Subtasks are a distinct nested object in Freelo under Tasks. We flatten them into the destination as children or linked items, preserving parent task linkage and status. |
| Users / Coworkers | Mapping required | Freelo's user roster includes Admin, Project Manager, and standard Member roles. We map the name, email, and role for each user; role-based permissions may require manual configuration in the destination. |
| Time entries / Cost tracking | Mapping required | Freelo tracks logged time and cost per task. We export the duration, cost value, and currency. Mapping to the destination's time-tracking schema depends on whether the destination has a native time-entry object. |
| Files / Attachments | Mapping required | Freelo allows file uploads up to 100 MB per file. We export file metadata, captions, and UUIDs. Actual binary files are pulled via the API and re-uploaded to the destination; large files may require chunking. |
| Comments | Fully supported | Comments are attached to Tasks and To-Do Lists. We export comment body, author, timestamp, and any embedded file references. Markdown formatting in Freelo comments is preserved as-is. |
| Notifications | Not in this platform | Notifications are ephemeral in-app or email alerts tied to user activity and session state. They are not part of the project's persistent data and are not migrated. |
| Events / Activity log | Not in this platform | Freelo's activity log tracks state changes over time but is not a persistent business record. We do not migrate it as it does not represent project content. |
| Out of Office records | Not in this platform | Out-of-office settings are user-preference data tied to the Freelo account. They do not constitute project or task data and are not migrated. |
| Custom Fields | Mapping required | Freelo supports custom fields on Tasks. We export the field name, type, and value for each record. Custom field type mapping (dropdown, number, date) depends on the destination's schema. |
Gotchas
What to watch for in Freelo migrations
Issues we've hit on past Freelo migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Free-plan export cap limits migration scope
Full data export is asynchronous with 1–2 day delay
File upload limit of 100 MB per file
No publicly documented API rate limits
Custom field type mapping may require manual review
| Severity | Issue |
|---|---|
| High | Free-plan export cap limits migration scope |
| High | Full data export is asynchronous with 1–2 day delay |
| Medium | File upload limit of 100 MB per file |
| Medium | No publicly documented API rate limits |
| Low | Custom field type mapping may require manual review |
Leaving Freelo?
Where Freelo customers move next
5 destinations Freelo can migrate to.
How a Freelo migration works
Four steps, Freelo-specific
Connect
API key (documented in Freelo API v1 via Apiary) into Freelo. Scopes limited to read-only on the data we move.
Map
We translate Freelo-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Freelo quirks before production.
Migrate
Full migration with Freelo rate-limit handling. Rollback available throughout.
FAQ
Freelo migration FAQ
Answers to the questions buyers ask most during Freelo migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Freelo 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 Freelo.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Freelo setup and destination — written quote back within a business day.