Migrate your Worksection data
Project management tool with built-in time tracking, Gantt charts, and Kanban boards. Favored by agencies and consultancies for its per-user pricing and long-tenure customer base.
In its favor
Why people choose Worksection
The signal that keeps Worksection on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Per-user pricing tiers starting at $3.75/month make Worksection cost-predictable for agencies billing clients by the hour and tracking project profitability.
The platform's time-tracking with hourly rates and built-in timer directly feeds billing reports, eliminating spreadsheet reconciliation for service businesses.
One workspace consolidates multiple client projects, their task lists, file attachments, and team communication, keeping everything from freelancers to creative deliverables in one URL.
The migration import function preserves folder structures, role permissions, and team hierarchies from other project management tools, reducing reconfiguration time.
Customizable reports allow teams to analyse project status and financial costs by time period, a capability consistently praised in long-term user reviews.
The interface is described as functional but dated — users accustomed to Asana or Monday find Worksection slower to learn and visually outdated.
The mobile app lacks offline capability, frustrating teams in field or studio environments where internet access is intermittent.
Some users report the Reports and Accounts module is underdeveloped compared to the task management core, requiring workarounds for billing export.
Limited native integrations beyond Google Drive and FTP mean teams needing deep CRM or communication tool sync often move to all-in-one platforms.
Reasons to switch
Why people leave Worksection
The recurring reasons buyers give for replacing Worksection. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Worksection 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
Worksection pricing overview
Worksection uses a per-user per-month pricing model across four tiers ranging from free to $11.25. All tiers include core project management, time tracking, and reporting features, with higher tiers adding custom fields, advanced permissions, and priority support.
Free
Tier 1 of 4
$0 per 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 Worksection's schedule — see our quote-based pricing →
What gets migrated
Worksection object support
Object-by-object support for Worksection migrations. Per-pair details surface during scoping.
Projects
Fully supportedWorksection organizes all work under Projects. We migrate Projects with their name, description, status, dates, and custom fields. Project folders and hierarchy are preserved during import.
Tasks
Fully supportedTasks are the primary work unit in Worksection. We migrate task titles, descriptions, assignees, due dates, priorities, and status. Subtasks are nested under their parent task.
Subtasks
Fully supportedSubtasks inherit parent task context and are migrated as child records. We preserve the parent-child relationship during the transfer.
Comments
Fully supportedTask-level comments and threaded discussion are migrated as part of the task record. Author attribution and timestamps are preserved.
Attachments
Fully supportedFile attachments on tasks and projects are migrated. FTP-linked and Google Drive references are resolved to physical files during import where supported.
Time Entries
Fully supportedWork logs with hours and descriptions are migrated. If rates are enabled, financial costs are calculated from hours at the configured rate during import.
Costs and Rates
Mapping requiredFinancial costs per task are imported with their descriptions. Rate-based recalculation is supported but may require confirmation of the rate value since automatic recalculation can be overridden per account settings.
Labels
Mapping requiredTask labels and stage tags are imported, but color tags and project-level color coding are dropped by Worksection's own migration logic — we flag this gap explicitly.
Users and Members
Fully supportedMember accounts including email, name, and role are migrated. If 'Invite to account' is enabled, invitations are sent; otherwise members are added to Contacts.
Teams and Departments
Mapping requiredTeam structure is preserved if 'Create teams' is enabled during import. Otherwise members land in the main team and manual regrouping is required.
Custom Fields
Mapping requiredCustom fields created per-project via Administration are supported but require field-level mapping since each project can define its own schema independently.
Gantt Dependencies
Mapping requiredTask dependencies visualized in the Gantt chart are migrated, but the 'next stage' linking between pipeline stages does not transfer and is dropped by Worksection's import.
Project History
Not in this platformWorksection's own migration documentation explicitly states project history is not transferred. We cannot preserve audit trails, activity logs, or past-state snapshots from the source account.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Worksection organizes all work under Projects. We migrate Projects with their name, description, status, dates, and custom fields. Project folders and hierarchy are preserved during import. |
| Tasks | Fully supported | Tasks are the primary work unit in Worksection. We migrate task titles, descriptions, assignees, due dates, priorities, and status. Subtasks are nested under their parent task. |
| Subtasks | Fully supported | Subtasks inherit parent task context and are migrated as child records. We preserve the parent-child relationship during the transfer. |
| Comments | Fully supported | Task-level comments and threaded discussion are migrated as part of the task record. Author attribution and timestamps are preserved. |
| Attachments | Fully supported | File attachments on tasks and projects are migrated. FTP-linked and Google Drive references are resolved to physical files during import where supported. |
| Time Entries | Fully supported | Work logs with hours and descriptions are migrated. If rates are enabled, financial costs are calculated from hours at the configured rate during import. |
| Costs and Rates | Mapping required | Financial costs per task are imported with their descriptions. Rate-based recalculation is supported but may require confirmation of the rate value since automatic recalculation can be overridden per account settings. |
| Labels | Mapping required | Task labels and stage tags are imported, but color tags and project-level color coding are dropped by Worksection's own migration logic — we flag this gap explicitly. |
| Users and Members | Fully supported | Member accounts including email, name, and role are migrated. If 'Invite to account' is enabled, invitations are sent; otherwise members are added to Contacts. |
| Teams and Departments | Mapping required | Team structure is preserved if 'Create teams' is enabled during import. Otherwise members land in the main team and manual regrouping is required. |
| Custom Fields | Mapping required | Custom fields created per-project via Administration are supported but require field-level mapping since each project can define its own schema independently. |
| Gantt Dependencies | Mapping required | Task dependencies visualized in the Gantt chart are migrated, but the 'next stage' linking between pipeline stages does not transfer and is dropped by Worksection's import. |
| Project History | Not in this platform | Worksection's own migration documentation explicitly states project history is not transferred. We cannot preserve audit trails, activity logs, or past-state snapshots from the source account. |
Gotchas
What to watch for in Worksection migrations
Issues we've hit on past Worksection migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Project history is permanently dropped on any migration
Stage links and 'next stage' dependencies do not migrate
Color tags and pinned image states are not transferred
8kB GET request limit requires chunked API reads
| Severity | Issue |
|---|---|
| High | Project history is permanently dropped on any migration |
| Medium | Stage links and 'next stage' dependencies do not migrate |
| Low | Color tags and pinned image states are not transferred |
| Medium | 8kB GET request limit requires chunked API reads |
Leaving Worksection?
Where Worksection customers move next
5 destinations Worksection can migrate to.
How a Worksection migration works
Four steps, Worksection-specific
Connect
OAuth 2.0 with bearer token into Worksection. Scopes limited to read-only on the data we move.
Map
We translate Worksection-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Worksection quirks before production.
Migrate
Full migration with Worksection rate-limit handling. Rollback available throughout.
FAQ
Worksection migration FAQ
Answers to the questions buyers ask most during Worksection migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Worksection 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 Worksection.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Worksection setup and destination — written quote back within a business day.