Migrate your AceProject data
Legacy web-based project management tool with built-in time tracking, expense management, and collaborative document handling. Suited for small to mid-sized teams who need an all-in-one PM suite without modern integrations.
In its favor
Why people choose AceProject
The signal that keeps AceProject on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Free tier with 3 users, 3 projects, and 1 GB storage lets teams validate fit before committing to a paid plan.
Built-in time tracking and expense reporting without requiring separate integrations or add-on purchases.
Gantt chart view, file commenting, and built-in chat consolidate communication into a single tool.
User-friendly dashboard with drag-and-drop task organization and real-time project status visibility.
One of the oldest web-based PM tools, giving it an established track record and stable, predictable feature set.
Slow load times and infrequent feature updates leave teams wanting a more responsive, actively developed platform.
No self-hosted or on-premises option forces reliance on the vendor's cloud, which limits control for regulated industries.
Lack of open source status means teams cannot self-modify or audit the codebase, unlike competitors such as OpenProject.
Limited third-party integrations require additional tooling to connect with modern CRM, ERP, or DevOps workflows.
Reasons to switch
Why people leave AceProject
The recurring reasons buyers give for replacing AceProject. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where AceProject 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
AceProject pricing overview
AceProject uses a per-seat, per-month subscription model with five tiers ranging from a free Basic plan for 3 users up to Enterprise for large deployments. Paid tiers increase user counts, storage, and project limits. Custom pricing is available for higher-volume customers.
Basic
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 AceProject's schedule — see our quote-based pricing →
What gets migrated
AceProject object support
Object-by-object support for AceProject migrations. Per-pair details surface during scoping.
Projects
Fully supportedProjects are the top-level container. We export all project metadata, statuses, and custom fields via the admin Export Data tool. Standard CSV output is straightforward with no schema quirks.
Tasks
Fully supportedTasks are the core work unit, supporting Assignees, Dependencies, Estimates, and Custom Fields. We preserve task hierarchy as exported. The CSV import requires DOS CRLF line endings — we convert source files accordingly before ingestion into a destination system.
Subtasks
Fully supportedSubtasks are nested under Tasks in the hierarchy. We flatten the tree structure into parent-child pairs during export and reconstruct the relationship in the destination platform.
Users
Fully supportedUsers are defined at the account level and assigned to Projects. We export all User records including custom User fields. Post-migration, manual project assignment is required since AceProject does not auto-assign imported users to their associated Projects.
Documents
Mapping requiredDocuments are associated with Projects. We export document metadata and attach file references, but file content transfer depends on whether the destination platform supports document hosting or requires a separate file migration.
Expenses
Mapping requiredExpense records are tied to Projects and optionally to Tasks. Normal users may have restricted visibility — we verify the exporting user's rights. Value mappings may be needed for currency fields across regional pricing tiers.
Time Entries
Fully supportedTime entries are recorded against Tasks and include hours, dates, and billing rates. We preserve the hours and date values. Rate fields map directly unless the destination uses a different currency denomination.
Custom Fields (Tasks)
Mapping requiredCustom Fields for Tasks support Boolean, Date, List, Numeric, Text, and User types. They only render in the new AceProject interface — we detect the interface version before mapping to avoid silent field loss on the classic side.
Custom Fields (Users)
Mapping requiredUser-level custom fields are supported. We export them as key-value pairs and map to equivalent custom properties in the destination platform where supported.
Dependencies
Fully supportedTask dependencies are defined within the Task object. We export the dependency type and linked Task ID and reconstruct the dependency graph in the destination system.
Comments
Mapping requiredDocument and task commenting is available. We export comment text and author. Comment threading structure is simplified during migration — flat comments migrate cleanly, nested threads are flattened.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Projects are the top-level container. We export all project metadata, statuses, and custom fields via the admin Export Data tool. Standard CSV output is straightforward with no schema quirks. |
| Tasks | Fully supported | Tasks are the core work unit, supporting Assignees, Dependencies, Estimates, and Custom Fields. We preserve task hierarchy as exported. The CSV import requires DOS CRLF line endings — we convert source files accordingly before ingestion into a destination system. |
| Subtasks | Fully supported | Subtasks are nested under Tasks in the hierarchy. We flatten the tree structure into parent-child pairs during export and reconstruct the relationship in the destination platform. |
| Users | Fully supported | Users are defined at the account level and assigned to Projects. We export all User records including custom User fields. Post-migration, manual project assignment is required since AceProject does not auto-assign imported users to their associated Projects. |
| Documents | Mapping required | Documents are associated with Projects. We export document metadata and attach file references, but file content transfer depends on whether the destination platform supports document hosting or requires a separate file migration. |
| Expenses | Mapping required | Expense records are tied to Projects and optionally to Tasks. Normal users may have restricted visibility — we verify the exporting user's rights. Value mappings may be needed for currency fields across regional pricing tiers. |
| Time Entries | Fully supported | Time entries are recorded against Tasks and include hours, dates, and billing rates. We preserve the hours and date values. Rate fields map directly unless the destination uses a different currency denomination. |
| Custom Fields (Tasks) | Mapping required | Custom Fields for Tasks support Boolean, Date, List, Numeric, Text, and User types. They only render in the new AceProject interface — we detect the interface version before mapping to avoid silent field loss on the classic side. |
| Custom Fields (Users) | Mapping required | User-level custom fields are supported. We export them as key-value pairs and map to equivalent custom properties in the destination platform where supported. |
| Dependencies | Fully supported | Task dependencies are defined within the Task object. We export the dependency type and linked Task ID and reconstruct the dependency graph in the destination system. |
| Comments | Mapping required | Document and task commenting is available. We export comment text and author. Comment threading structure is simplified during migration — flat comments migrate cleanly, nested threads are flattened. |
Gotchas
What to watch for in AceProject migrations
Issues we've hit on past AceProject migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Task import does not auto-assign users to Projects
Custom fields only visible in the new interface
CSV import requires DOS-style CRLF line endings
Expense field visibility gated by user role
| Severity | Issue |
|---|---|
| High | Task import does not auto-assign users to Projects |
| Medium | Custom fields only visible in the new interface |
| Medium | CSV import requires DOS-style CRLF line endings |
| Low | Expense field visibility gated by user role |
Leaving AceProject?
Where AceProject customers move next
5 destinations AceProject can migrate to.
How a AceProject migration works
Four steps, AceProject-specific
Connect
Username + password Login call returns a GUID token used in subsequent requests; auto-expires after 8 hours of inactivity. into AceProject. Scopes limited to read-only on the data we move.
Map
We translate AceProject-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate AceProject quirks before production.
Migrate
Full migration with AceProject rate-limit handling. Rollback available throughout.
FAQ
AceProject migration FAQ
Answers to the questions buyers ask most during AceProject migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your AceProject 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 AceProject.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your AceProject setup and destination — written quote back within a business day.