Which open-source tool replaces Asana portfolios?
Teams on Asana's Advanced plan or above use portfolios, goals and resource views to track many projects from one place. OpenProject is the closer match for that job. Its portfolio and program management and team planner cover multi-project oversight, while Plane covers cross-project tracking through modules and workspace views. The gap is at the edition level: some OpenProject portfolio and resource management features sit in paid Enterprise plans, so the free Community edition may not cover the whole Asana setup. Map each portfolio view you use today against the edition that includes it before you decide.
Asana's pricing page lists unlimited portfolios, goals and resource management for seeing who is overloaded under its Advanced plan, and it adds organization-wide resource management at the Enterprise level. Those are the features to inventory first. List every portfolio, goal and resource view that leaders open each week, note who owns it, and record whether it is a status roll-up, a dependency view or a capacity view. Each type maps to a different feature in OpenProject or Plane, and the number of portfolios matters less than how many people depend on them.
Before you plan the migration, confirm three things. First, check the current feature list on the OpenProject pricing page for portfolio, resource and program management, along with SSO and LDAP synchronization, which sit in Enterprise plans. Second, check the Plane editions documentation to see which workspace views and modules your chosen self-hosted edition includes. Third, rebuild one of your portfolios in a test instance using copies of your own data. Capacity views depend on accurate effort and assignment data, so a portfolio that looks complete in Asana may show gaps once it is rebuilt.
How Asana portfolio capabilities map to open-source options
This table maps Asana's portfolios, goals, status roll-ups, resource management and org-wide resource views to OpenProject Community and Enterprise and to Plane Community and paid plans. Read each row for its coverage (covered, partial or not covered), the edition that unlocks it and the vendor page to check before you commit. The main takeaway is that portfolio and resource features sit in paid OpenProject Enterprise plans, while the facts available for Plane do not confirm direct equivalents.
| Asana capability | OpenProject (Community and Enterprise) | Plane (Community and paid plans) | Where to confirm |
|---|---|---|---|
| Portfolios | Community: not covered, with projects and Gantt charts but no portfolio layer. Enterprise: covered as portfolio and program management. | Not confirmed. Modules and workspace views are the nearest match, with no portfolio roll-up documented in the facts reviewed. | OpenProject pricing page; Plane pricing and self-hosting docs |
| Goals | Partial. Dashboards show project status, but confirm whether a goal object exists in your edition. | Partial. Cycles and modules track delivery progress; no goal entity is confirmed. | Asana pricing page for goal scope; each vendor's feature docs |
| Status roll-ups across projects | Community: partial, limited to project-level status and dashboards. Enterprise: covered in portfolios, so confirm which fields roll up. | Partial. Per-project and per-cycle progress is clear; cross-project roll-up needs confirmation. | OpenProject release notes for portfolio fields; Plane release notes |
| Resource management (who is overloaded) | Community: partial, with assignments and time tracking. Enterprise: resource management is listed as a paid feature; confirm the load view. | Not confirmed. Assignee and cycle views may show load, but check for a capacity view before relying on it. | OpenProject pricing page; Plane feature documentation |
| Org-wide resource management | Enterprise only. Confirm scope in the Corporate tier, which is quoted on request for 250 or more users. | Not confirmed for Pro or Business. Enterprise adds LDAP and API audit logs, but an org-wide resource view is not documented in the facts reviewed. | Plane pricing page; ask both vendors in writing |
| Workload and timeline views | Covered in Community through Gantt charts, agile boards and dashboards. | Partial. Work item and cycle views exist; confirm timeline and workload charts on your version. | OpenProject pricing page; Plane self-hosting overview |
| Price basis for the features above | Enterprise on-premises is per named user per month: Basic 5.95 euros, Professional 10.95 euros (25-user minimum), Premium 15.95 euros (100-user minimum). | Pro is shown at 6 to 8 US dollars and Business at 13 to 15 US dollars per user per month. Enterprise Grid is priced on request. | OpenProject and Plane pricing pages, checked on the day you request a quote |
| Access controls for portfolio data | Enterprise adds SSO (SAML, OIDC, CAS, Kerberos, Okta) and LDAP group synchronization. | SAML and OIDC are available on Pro and above. LDAP is listed as an Enterprise feature. | OpenProject and Plane pricing pages |
Which option fits which portfolio need
OpenProject Community is the free, GPL-3.0 edition. It covers the day-to-day planning that sits underneath a portfolio: work packages, Gantt charts, agile boards, time tracking and dashboards. Teams that track projects individually and need to see schedules and dependencies in one place can run it without a license fee, and it is the starting point for most teams leaving Asana projects behind.
- Work packages and Gantt charts: Project schedules, dependencies and milestones live in one tool, which covers project-level timelines.
- Dashboards: Project status views are available, but cross-portfolio roll-ups and resource overload reporting are not part of this edition.
- Support model: Community support is provided by the user community, so response times and troubleshooting depend on your own staff.
- What the team builds: Identity integration, backup routines, upgrade windows and any custom reporting across projects remain your responsibility.
Before you commit, confirm with OpenProject which dashboards and reporting features you need at the portfolio level, because those are the features the Enterprise tab covers.
OpenProject Enterprise adds the portfolio and program management and team planner features that match Asana's portfolio view more closely, together with single sign-on, LDAP group synchronization and custom branding. Enterprise on-premises is priced per named user per month, with Basic at 5.95 euros and Professional at 10.95 euros per user with a 25-user minimum, Premium at 15.95 euros with a 100-user minimum, and Corporate on request for 250 or more users. The OpenProject pricing page is the source for these figures.
- Named-user licensing: Cost scales with the number of named users, so model the seats that need portfolio access rather than the whole company.
- Support model: Enterprise plans come with vendor support, so confirm response terms in the plan you select.
- Identity features: SSO (SAML, OIDC, CAS, Kerberos, Okta) and LDAP group synchronization are included in paid plans.
- What the team builds: Portfolio structures, program hierarchies, reporting definitions and the team planner setup still need design work and staff time.
Confirm whether the portfolio and team planner features in your target plan cover the views your portfolio owners use today.
Plane is a better fit for teams whose portfolio need is mostly cross-project work item tracking. Its modules group work items across projects, and workspace views let teams see items from several projects together. It is licensed AGPL-3.0 in the Community Edition, which matches the Plane Cloud Free feature set. Plane does not present itself as a full portfolio and program management suite, so teams with formal resource planning should test it against their requirements.
- Modules and workspace views: Work items can be grouped across projects and viewed together at workspace level.
- Paid features on self-hosting: Moving to a paid plan requires the Commercial Edition with a license key, and SAML and OIDC are on Pro and above. LDAP support is listed as an Enterprise feature.
- Support model: Community Edition support is community-based. Commercial support terms come with the paid plans, so confirm them directly with Plane.
- What the team builds: Resource overload views, reporting beyond the built-in views, and the operational setup for PostgreSQL, Redis or Valkey, RabbitMQ and S3-compatible storage remain your work.
Confirm with Plane which portfolio-level views your owners need before you choose the Community Edition over a paid edition.
Which portfolio features need an Enterprise edition
For OpenProject, the portfolio and resource features that Asana customers usually need sit in paid Enterprise plans, not the free Community edition. The OpenProject pricing page places portfolio and resource management alongside SSO, LDAP synchronization and SCIM provisioning in those plans. Its Enterprise list also includes SAML, OIDC, CAS, Kerberos and Okta sign-in options and LDAP group synchronization. Decide on the Enterprise plan before the pilot, not after, because a team that moves its project data first and then finds its portfolio view behind a paid plan will have to rebuild its reporting. Confirm which plan includes each feature you depend on, and whether your identity provider needs SCIM provisioning or only single sign-on. The OpenProject pricing page is the current reference for that split.
Plane's split works differently. The Community Edition, licensed under AGPL-3.0, matches the feature set of the Plane Cloud Free tier. On self-hosted installs, SAML and OIDC are available from the Pro plan upward, while LDAP support and API-enabled audit logs are listed as Enterprise features. Moving to any paid self-hosted plan means switching a Community install to the Commercial Edition and applying a license key, with seats counted by users who hold paid roles. Treat that switch as a deployment change with its own change window, because the Commercial and Community editions are distinct codebases with separate release cycles. Also check which edition your deployment method installs. Plane's Kubernetes guide installs the Commercial Edition, whose Free plan includes 12 seats without a license key, so a team may already be running the Commercial Edition without having chosen it.
Running open-source portfolios next to the rest of your suite
A portfolio tool rarely works alone. Identity, the Asana projects still in use during cutover, file storage, reporting and the audit trail all touch it, and each one needs an owner before go-live. The cards below set out what to build or confirm for each point.
Identity and directory groups
Portfolio views are only as accurate as the people and groups behind them. OpenProject lists SSO (SAML, OIDC, CAS, Kerberos, Okta) and LDAP group synchronization under its Enterprise features, so single sign-on and group mapping sit on the license line. Your identity team should map existing directory groups to OpenProject roles and confirm which of these features your chosen edition includes before the pilot. Plane lists SAML and OIDC on Pro and above, with LDAP as an Enterprise feature. Confirm both against the current pricing pages.
Asana projects during cutover
Most portfolios cannot move in one step, so some Asana projects will stay live while others migrate. Decide which team owns each project during the overlap, freeze edits on migrated projects, and set a date for the last Asana update. Portfolio totals will be wrong if status is maintained in two places. The migration team owns the cutover calendar, and the portfolio owner signs off on which projects count in the consolidated view.
File storage through Nextcloud
Project attachments and deliverables often live in Asana comments or in a shared drive. OpenProject has a documented Nextcloud integration, so teams that already run Nextcloud can link files to work packages without copying them into the project tool. Your infrastructure team should confirm the Nextcloud version and the permission model, and decide whether files stay in one storage or move. Test that a user who cannot see a file in Nextcloud cannot reach it through OpenProject.
Reporting outside Asana dashboards
Asana dashboards and portfolio reports will not transfer as objects. Export the fields your leadership reports need, including dates, owners, status and tags, from the Asana CSV export, then rebuild the views in OpenProject or in a BI tool your organization already runs. Agree the report definitions with the executives who read them before cutover, so the new reports replace the old ones rather than running beside them.
Audit trail and retention
Asana's audit and export capabilities depend on plan and role, so confirm what your current contract gives you before you leave. In the self-hosted tool, the audit trail is your responsibility. Confirm which events each edition logs, where the logs are written, how long they are kept and whether they reach your central log platform. Security should test that a removed user's past changes stay attributed to them, and the compliance lead should record how the evidence is retained.
How to move portfolio structure out of Asana
This sequence rebuilds Asana's portfolio, goal and workload views on OpenProject or Plane, so that project data moves with its structure and users can work in the new tool without losing track of what sits under each portfolio.
Inventory portfolios, goals and their projects
Before exporting anything, list every portfolio in the Asana organization, the goals attached to each one, and the projects inside each portfolio, along with the owner of each item. Record which portfolios are actively used for reporting and which are historical. Ask the Asana admin to confirm the list, since portfolio membership is not visible from a single project export. The step is done when every portfolio has a written list of member projects and a named owner.
Export project data as CSV from Asana
Export each project in scope to CSV from its project actions menu. The CSV includes task ID, dates, name, assignee, due date, tags, notes and parent task, which covers the work itself. Do not plan on the organization export for this step, because Asana only offers it to service accounts of an Enterprise+ organization. Portfolios, goals and resource settings are not part of these files, so keep the inventory from the previous step alongside them. The step is done when every project in the inventory has a CSV file stored in a controlled location.
Map portfolios to OpenProject or Plane structures
Decide how each Asana portfolio will be represented in the target tool. In OpenProject, a portfolio is usually a program or a parent project that groups child projects, and portfolio and program management sits in Enterprise plans, so confirm the edition before you design the hierarchy. In Plane, use modules or cycles to group work items that belong to one initiative, and document which Asana goals become Plane items or pages. Write the mapping as a table with columns for Asana object, target object and owner. The step is done when the table has been reviewed by the people who report on portfolios.
Import projects and validate the results
Import the projects into the target tool. Plane offers an Asana importer on Plane Cloud and on the self-hosted Commercial Edition, which is the more direct route for Asana data. In OpenProject, the import starts from the CSV files and is typically done by the implementation team with a mapping sheet. Check a sample of tasks in each project against the source for names, assignees, dates, tags and parent-child relationships. Log any rows that did not import. The step is done when the sample check passes and every exception has an owner and a decision.
Rebuild goal and resource views by hand
Recreate the goal tracking and workload views that Asana provided through portfolios, goals and resource management. Expect to rebuild these manually. A simple project import does not carry over portfolio or goal objects, so each goal needs a target object, a status and a link to its work. For workload views, confirm whether the target edition provides resource or capacity management, since OpenProject lists portfolio and resource management among its paid Enterprise features. The step is done when each goal from the inventory has a matching view or report, and the reporting owners have reviewed it.
Cut over users and retire the Asana views
Set a cut-over date after validation, communicate it to portfolio owners and project members, and provision their accounts in the new tool. If the target edition needs single sign-on or directory synchronization, confirm that these are in place before users log in, because those features sit in paid tiers on both OpenProject and Plane. Ask portfolio owners to use the new views for their next status report. Keep the Asana CSV exports and the mapping table as an archive. The step is done when the portfolio owners have run one reporting cycle in the new tool and the Asana portfolio views are no longer used for decisions.
What do buyers ask before moving Asana portfolios?
Do I need an Enterprise edition to get portfolio views in OpenProject?
Portfolio and program management and resource management sit in OpenProject's paid Enterprise plans, not in the free Community edition. The Community edition covers work packages, Gantt charts, agile boards, time tracking and dashboards, so teams that only need project-level views can start there. Before you commit, confirm with OpenProject which portfolio features each on-premises tier includes, because the Enterprise feature list determines whether the portfolio views you use in Asana are covered. Plane's portfolio-style views should be checked against its current plan documentation in the same way.
How much does it cost to replace Asana portfolios?
Cost has four parts: software licensing, hosting, administration time and migration effort. The OpenProject Community edition is free to license, while Enterprise on-premises plans are priced per named user per month, with Basic at 5.95 euros, Professional at 10.95 euros with a 25-user minimum, Premium at 15.95 euros with a 100-user minimum, and Corporate on request for 250 or more users, as listed on OpenProject's pricing page. Hosting, backups, upgrades and staff time recur every year, while setup and data migration are usually one-time. Ask any vendor or implementation partner for a quote that separates these lines, and compare it with your current Asana portfolio tier.
How long does a portfolio migration from Asana take?
The duration depends on how many projects, portfolios and goals you move, how much of their history you keep, and how much rebuilding the target tool needs. Portfolios and goals rarely map one to one, so they usually take the most design time. Asana's per-project CSV export carries task fields such as dates, assignees, tags and parent tasks, but it does not rebuild portfolio roll-ups, so those must be recreated. No duration figure is supplied for this work, so ask your implementation partner for a timeline tied to a written scope, and ask the vendor for its own onboarding guidance.
Can our own team move Asana portfolios without outside help?
A small team with one or two portfolios and clear project owners can often do the work in-house, provided it has someone who can install and maintain the platform. The harder parts are rebuilding portfolio roll-ups, mapping custom fields and recreating permissions and reporting, which need a person who understands both the old and new tools. Packaged OpenProject installs support Ubuntu 22.04, Debian 12, CentOS or RHEL 9.x and SUSE Linux Enterprise Server 15, and Plane offers Docker Compose and Kubernetes methods. If you need an outside partner for setup, hardening or a fixed-scope migration, DeployOpen plans, implements and documents self-hosted platforms inside your own infrastructure.
What does the work require from IT and project owners?
IT provides the hosting environment, identity integration, backups, network rules and the database and object storage services. OpenProject requires PostgreSQL 16 or later and the pg_trgm, btree_gist and unaccent extensions, and its sizing guide suggests 4 cores and 4 GB RAM for up to 200 users. Plane uses PostgreSQL, Redis or Valkey, RabbitMQ and S3-compatible storage such as MinIO. Project owners must confirm which projects, portfolios and fields they still need, approve the mapping of statuses and owners, and sign off on the test migration before cutover.
What should I ask for in a fixed-scope quote?
Ask for a written scope listing which portfolios, projects and goals move, which data types come across, and which reports must be rebuilt. The quote should name deliverables, a timeline, acceptance criteria, the hosting environment, backup and upgrade responsibilities, and any ongoing support as a separate retainer. Ask whether test migrations are included and how many rounds of mapping review are covered. DeployOpen works from a written scope and does not publish a price list, so a quote follows from that document.
Which Asana data is lost when I export from Asana?
Per-project CSV exports carry task fields such as task ID, dates, name, assignee, due date, tags, notes and parent task, but they do not carry portfolio roll-ups, goals or resource views. Asana's organization export returns complete data as gzipped JSON, but only service accounts of an Enterprise+ organization can run it. Confirm with Asana which of your portfolio, goal and automation data each export includes before you plan the migration, and capture screenshots or definitions of any portfolio views you need to rebuild.
How DeployOpen scopes and delivers portfolio replacement
Every engagement starts with a written scope, deliverables and timeline agreed before any work begins. For a portfolio replacement, that scope should name the target platform, either OpenProject or Plane, the edition you need, and the specific portfolio features you must keep. Those features may sit in paid tiers. OpenProject places portfolio and resource management, SSO, LDAP synchronization and SCIM provisioning in its Enterprise plans, so the scope needs to state which of those you require. DeployOpen does not publish a price list, so the quote follows from that written scope. Ask for it to list each component separately: planning, installation, integration with your identity provider, data migration, testing, documentation and any retainer.
The delivery work covers the self-hosted deployment inside your own cloud account, data center or air-gapped network, plus the controls around it. For OpenProject, that means choosing between Docker, packaged installs or Kubernetes with Helm, and confirming the PostgreSQL version and extensions against the system requirements before anything is built. For Plane, it means deciding between Docker Compose and Kubernetes, and whether PostgreSQL, Redis or Valkey, RabbitMQ and object storage run in-house or as external managed services. Hardening, backup and restore tests, and access controls are scoped alongside the install, so the portfolio data and its permissions are protected from the first day in production.
The final deliverable is documentation your team can run without us. It should record the architecture, configuration, backup and upgrade procedures, and the portfolio structure you rebuilt, such as programs, goals and resource views. Ongoing support, upgrades and continuous testing are available as a retainer once the fixed-scope project closes. Before you sign, confirm with DeployOpen which edition each feature requires, who signs off on the written scope and how acceptance is measured. Those are the points where portfolio replacements most often drift.
