Trello vs Nextcloud Deck: when each fits and what the decision turns on
Trello fits a team that wants a hosted board with little administration and does not need its boards to sit inside the same self-hosted platform as its files and chat. Nextcloud Deck fits an organization that already runs, or plans to run, Nextcloud for documents and messaging and wants kanban boards next to those files under its own administration. The decision turns on one question: must boards, attachments, comments and user identity live inside a single self-hosted platform that your team operates? If the answer is yes, Deck is the natural candidate to test. If boards are a small, separate concern that a hosted tool already handles well, the switch may add work without adding control.
Renewal dates, pricing changes, data residency rules and lock-in are the usual triggers, and each one points to a different test. For residency, confirm where Trello stores board data and attachments for your plan and region, and compare that with a Nextcloud instance in a data center you choose. For lock-in, check what you can export: Trello's per-board JSON export is capped at 1,000 actions, so the export you choose determines how much history survives. For identity, confirm whether your directory already feeds Nextcloud, since Nextcloud's LDAP app lets directory users sign in with their existing credentials, and whether Trello's single sign-on is tied to an Atlassian plan you would otherwise need to keep.
Before committing, run a short pilot. Pick one active board, import a copy, and check that cards, attachments and comments arrive as you expect, then confirm that the people who need access can reach it through your existing login. Nextcloud's own upgrade rules also belong in the plan: major versions cannot be skipped, so your team must schedule one major upgrade at a time with a backup before each. Teams that cannot staff that cadence should price a support arrangement, or choose a standalone board tool, before the migration starts.
Which option fits which organization
This table maps common Trello scenarios to the better fit between Nextcloud Deck and other options, with the condition that drives each choice. Read it by finding the situation closest to yours, then checking the reason column against where your files, administrators and integrations already sit.
| Scenario | Better fit | Reason |
|---|---|---|
| Nextcloud already holds files and chat | Nextcloud Deck | Boards sit beside the documents and conversations they relate to, so one login, one permission model and one backup routine cover both. |
| No Nextcloud today, need a Trello-style board only | Consider WeKan or a standalone board | Deck adds a full Nextcloud platform to run. If boards are the only need, a lighter single-purpose tool may carry less administration. |
| Heavy reliance on Trello Power-Ups | Trello or a tool with matching integrations | Deck has no Power-Up marketplace equivalent. Confirm each integration your team uses before choosing Deck. |
| Strict data residency requirement | Deck or WeKan on infrastructure you choose | Both can run in a region or data center you select, so boards, comments and attachments stay under your control. Confirm where backups are kept too. |
| Small team wanting minimal administration | Trello, or a hosted option | Self-hosting adds patching, backups and upgrades. A small team without an administrator may prefer a managed service or a partner-run deployment. |
| Existing Nextcloud admins with upgrade discipline | Nextcloud Deck | Nextcloud requires one major version at a time and backups before each upgrade. Teams already following that routine absorb Deck with little extra work. |
| Teams needing Atlassian Guard or Jira links | Trello, or confirm alternatives first | Deck does not replace Atlassian administration or Jira linking. Map those dependencies before any migration plan. |
| Need for SSO with an existing directory | Deck on Nextcloud with LDAP or SAML | Nextcloud documents LDAP, OpenID Connect and SAML backends, so directory users can sign in. Confirm the exact setup with your identity team. |
What changes for board users, Nextcloud admins and the security team
People who move cards every day will notice the change first. Deck uses the same basic model Trello users know: boards hold stacks, stacks hold cards, and cards carry due dates, labels, assignees, comments and attachments. The layout differs, though, and some Trello habits, such as heavy use of Power-Ups or board-wide automation, may not carry over in the same form. Users sign in through the organization's Nextcloud account rather than a Trello login, and boards appear next to the files and chat they already use.
- Familiar core: Stacks, cards, labels, due dates and assignees cover the everyday board work most teams do in Trello.
- Sign-in change: Users log in to Nextcloud, so boards follow the same account, password policy and session rules as files.
- Attachments in one place: Files linked to a card can sit in the same Nextcloud storage as the rest of the team's documents.
- Feature gaps: Confirm which Power-Ups, automations and integrations your team relies on, because Deck does not reproduce all of them.
- Version check: Deck feature coverage changes between releases, so test the exact functions your team uses against the Nextcloud version you run.
Before cutover, run a pilot board with real card volume and ask a few users to perform their routine tasks in it.
Administrators gain a board tool without adding a separate service, but they also take on Deck as one more app inside the Nextcloud instance. Deck is upgraded and backed up with the rest of Nextcloud, so its maintenance follows the platform's release cycle. Nextcloud publishes a new major version every four months and supports each one for a year, and major upgrades must be done one version at a time. Third-party apps must be confirmed compatible before an upgrade.
- Shared upgrade path: Deck changes with each Nextcloud major release, so plan upgrades around the supported version window.
- Sequential majors: Nextcloud does not allow skipping major releases, so each upgrade step needs its own test window.
- Backups: Board data lives in the Nextcloud database and storage, so backup scope must include both.
- Database and PHP support: Confirm the database and PHP versions your release requires before you schedule upgrades.
- Installation method: Nextcloud All-in-One can simplify deployment, but confirm which components your environment needs.
Ask your DeployOpen or internal platform team to document the upgrade runbook for Deck, including rollback steps and the owner for each app update.
Security and compliance leads review three things: who can sign in, what gets logged, and where the data sits. Moving boards into Nextcloud places them under the organization's own identity provider and storage, which can simplify the review. Nextcloud documents LDAP and Active Directory login, along with OpenID Connect and SAML backends, so the sign-in model can match existing controls. Whether those options fit your requirements depends on your identity setup and the Nextcloud edition you run.
- Identity: Confirm how Deck users are provisioned, deprovisioned and assigned to groups, and whether LDAP, OpenID Connect or SAML covers your requirements.
- Logging: Confirm which access and change events are logged, where they are stored, and how long they are kept for review.
- Data location: Boards, comments and attachments stay on infrastructure the organization controls, so document the hosting region and storage location.
- Licensing and support: Nextcloud Enterprise adds maintenance terms and support levels, so check which edition your controls depend on.
- Evidence: Ask your auditor which Deck and Nextcloud configurations they will sample, and prepare that evidence before assessment.
DeployOpen prepares controls and evidence for compliance assessments, but independent auditors decide whether the controls meet your framework.
How Trello and Deck compare on capability, licensing and hosting
This table compares Trello with Nextcloud Deck across board structure, collaboration features, import and export, authentication, licensing and hosting. Where a capability is not confirmed by a supplied source, the cell tells you what to check on your own instance. Read it as a checklist: the main takeaway is that Deck's value depends as much on your Nextcloud operations as on the board itself.
| Capability | Trello | Nextcloud Deck |
|---|---|---|
| Board and card structure | Boards, lists and cards with labels, assignees and due dates in the Trello web and mobile apps | Boards, stacks, cards, labels, assignees and due dates. Confirm stack and card limits on your Nextcloud version |
| Comments and attachments | Comments and attachments on cards. Full comment history depends on your Trello plan and export method | Comments and file attachments on cards, stored in Nextcloud. Confirm attachment sizes and quotas with your administrator |
| Sharing and access | Board membership and workspace-level visibility managed in Trello | Boards shared with users and groups through Nextcloud sharing. Test guest and external access on your own instance |
| Activity history | Board activity feed visible to members, with action history subject to Trello's export limits | Activity depends on the Deck app version. Verify what history is retained before relying on it for audits |
| Import and export | JSON export per board, CSV export on Premium, and a Premium Workspace export. Each has documented limits on this site | Import from Trello JSON with occ deck:import. Confirm which Trello data types the import carries in your version |
| Authentication options | Atlassian accounts, with single sign-on through Atlassian Guard on eligible plans | LDAP and Active Directory login, plus OpenID Connect and SAML user authentication backends documented by Nextcloud |
| Licensing | Proprietary SaaS subscription billed per user on Trello's plans | Nextcloud Server is AGPL-3.0. Deck is delivered as a Nextcloud app. Confirm the Deck app license in its repository |
| Hosting model | Atlassian-hosted cloud only | Self-hosted on your own servers or cloud accounts. Nextcloud All-in-One is the official installation method |
| Upgrade and support cycle | Managed by Atlassian with no action from you | Nextcloud releases a major version every four months, each supported for one year. Plan one major upgrade at a time with backups |
Where boards, comments and attachments live under each option
Trello keeps boards, comments and attachments in Atlassian's cloud, while Deck stores its cards in the Nextcloud instance your team runs. The cards below cover where each piece of data sits, who controls access and logs, and what a self-hosted setup asks of your own staff and auditors.
Trello data in Atlassian's cloud
Trello boards, card comments and attachments are stored in Atlassian's hosted service, so the storage location, backup schedule and infrastructure changes are set by the vendor. Your team controls board membership and workspace settings but not the underlying systems. Before renewal, ask Atlassian in writing where your workspace data is stored, how attachments are retained after deletion and what export options exist if you leave.
Deck data in your Nextcloud storage
Deck cards, comments and attachments are written to the Nextcloud data directory and metadata tables in the database you configure, typically MariaDB or PostgreSQL. Your team decides the disk, the database host and the backup target, so file recovery and deletion follow your own procedures. Confirm where the data directory sits, which database engine you run and whether attachments are encrypted at rest on that storage.
Directory and single sign-on options
Nextcloud can authenticate users against LDAP or Active Directory, and it also documents OpenID Connect and SAML backends, so Deck access can follow the identity provider you already use. Trello's single sign-on is handled through Atlassian Guard, which is a separate administration product. Map your joiner and leaver process to the directory group that grants Deck access, and test that removing a user from the directory also removes board access.
Audit logs and monitoring ownership
On a self-hosted Nextcloud instance, your team is responsible for collecting, retaining and reviewing server logs, admin actions and access records. Nothing is logged for you by a vendor unless you add that capability. Decide who reviews these logs, where they are shipped, how long they are kept and how you would reconstruct who moved or deleted a card. Ask Atlassian what audit history Trello exposes to your administrators so you can compare the two.
Upgrade and patch accountability
Nextcloud releases a new major version every four months and each one is supported for a year, so your team must plan upgrades one major version at a time and take a backup before each one. Third-party apps must be checked for compatibility first. Under Trello, Atlassian applies platform updates for you. Assign a named owner for patching the server, the database and PHP, and schedule the upgrade window.
Compliance evidence and paid support
Self-hosting moves control evidence, such as access reviews, backup restores and change records, into your organization's hands. DeployOpen can prepare those controls and evidence for an assessment, but independent auditors issue any report or attestation. Nextcloud Enterprise is a paid option with maintenance and support tiers that differ in lifecycle length and response times, so confirm the tier, support hours and contract terms in writing as a procurement question before you rely on them.
What a Trello subscription costs compared with running Deck
Trello's cost is a recurring subscription that scales with seats, so the total depends on how many people hold a board membership and which plan they sit on. Per-user plans and Atlassian Guard for single sign-on and administration are billed continuously, and the bill rises with each hire or contractor added to a workspace. Ask Atlassian for the current per-user price for each plan you would need, the number of paid seats your workspace would be billed for, and whether Guard is included or sold as an add-on. Nextcloud Deck has no license fee of its own, because Deck ships inside Nextcloud Server under AGPL-3.0, so its costs are the infrastructure and people behind it.
On the Deck side, the cost components are the servers or virtual machines, a supported database such as PostgreSQL, object or block storage for files and attachments, a backup target, and staff time for patching, upgrades and monitoring. Most of these are recurring. The one-time items are the initial deployment, LDAP or SSO configuration, and the migration of boards. Nextcloud publishes a new major version every four months and supports each for one year, and administrators cannot skip major releases, so each cycle adds upgrade and testing work that recurs for as long as you run the platform. Nextcloud Enterprise is optional. Its list prices, as shown on the Nextcloud pricing page, start at 71.29 euros per user per year for Standard, 104.99 euros for Premium and 204.75 euros for Ultimate, with a 100-user minimum. Those figures are list prices from that page and may have changed, so confirm them before budgeting.
When you request a written quote for a self-hosted option, ask for each line separately: infrastructure sizing and monthly hosting, backup retention and storage, the upgrade calendar and who performs each upgrade, administration hours per month, and the scope and response times of any support plan. Ask whether an implementation or migration fee is fixed or time-based. Compare the Trello renewal over the same period, including seat growth, against these lines, and note which costs fall to your own staff. The fixed-scope quote from an implementation partner should state its assumptions, such as user count and integrations, so the comparison stays honest.
How a move from Trello to Deck is planned and run
The sequence turns an informal set of Trello boards into Deck boards that match what the organization needs to keep, with each step closing on a written check before the next one starts.
Inventory boards, members and access
The project owner lists every Trello board, its owner, its active members, its Power-Ups and whether it holds archived cards that someone still uses. Team leads confirm which boards are live, which are reference only and which can be closed. The output is a signed-off register that maps each board to a Deck owner and a set of Nextcloud users or groups. The step is done when every board has one named owner and every member can be matched to a Nextcloud account, either directly or through the directory your organization already uses.
Decide what history must survive
Compliance, legal and operations leads decide which card comments, activity history, attachments and archived cards must be kept after cutover. Trello's JSON export per board includes only the 1,000 most recent actions, so anything older needs a decision now, along with a plan for keeping the original export outside Deck. Ask the vendor or your own records team to confirm which retention rules apply. The output is a short retention note per board that the migration team can test against.
Run a pilot board
Choose one active board with a small membership and a mix of card types, labels, due dates, checklists and attachments. The migration team imports a copy into a test Nextcloud instance and compares card counts, labels, assignees and attachments against Trello. Users who work on the board review the result and log every gap. The step closes when the pilot board is accepted in writing and the gaps are either fixed or accepted as known differences.
Plan the Nextcloud upgrade path and backups
The platform team confirms the current Nextcloud major version and the supported database, PHP and web server versions in the target environment, then plans any upgrades. Nextcloud does not allow skipping major releases, so each upgrade moves one major version at a time, with a backup taken beforehand and third-party apps disabled until confirmed compatible. Deck should be checked against the target release during the pilot. The output is a dated upgrade plan with a tested restore procedure. Confirm the current supported releases on Nextcloud's release schedule before you commit.
Import boards with the supported method
The migration team runs the Trello import into Deck using the occ deck:import command on the approved export files. For busier boards, the team decides between the JSON export and the Trello API route, since the JSON export is capped at the most recent 1,000 actions per board. The detailed command steps, file handling and attachment behavior are covered in the dedicated migration guide. The output is an import log for each board, kept with the retention note from earlier.
Validate cards, comments and attachments
Board owners compare each imported board with its Trello original using a shared checklist: card count, list order, labels, due dates, assignees, checklist items, comments and a sample of attachments. Any mismatch is logged with a card reference and resolved by re-import or manual correction. The check is complete when each owner signs off the board and the import log shows no unresolved errors. Keep the Trello originals available until this sign-off is recorded.
Cut over users and retire Trello access
The organization announces the cutover date, moves users to Deck boards and points them to a short guide on where their work now lives. Trello boards are set to read-only or closed according to the register, and member access is removed from accounts that no longer need it. The service owner confirms that the Trello export archive is stored under the retention rules. The output is a closed Trello estate, a documented access list and a record of the final export, ready for the post-cutover review.
Questions buyers ask before choosing Deck over Trello
Can a Nextcloud team run Deck without outside help?
Yes, a team with someone who already administers Nextcloud can usually run Deck in-house, because Deck is an app inside the same server that handles files and chat. The work that remains is routine: applying the monthly maintenance releases, keeping the server and database supported, and checking that Deck stays compatible after each upgrade. The deciding factors are whether that person has time for patching and backups, and whether the organization needs someone on call. Confirm the team's skills with Nextcloud's system requirements and decide early who owns each recurring task.
How long does a Trello to Deck migration take?
The duration depends on the number of boards, how many cards carry attachments and comments, and how much cleanup the boards need before import. Export size matters more than board count, because a few busy boards with long histories take longer to review than many small ones. Teams that rely on Trello's JSON export should also plan for its limit of 1,000 actions per board, which affects how much history arrives. No duration is stated here, so ask any provider for a written timeline based on an inventory of your boards and their attachments.
What does the internal team need to provide during a migration?
The internal team needs to name a business owner for each board, decide which archived or stale boards are kept, and confirm who approves the final cutover. Someone with Nextcloud administrator access must also provide a test instance, a database backup and the import environment. Expect reviews of board structure, labels, members and due dates, because those fields need owner sign-off before the boards are declared correct. Write these responsibilities into the scope so that no step depends on an assumption.
How do Nextcloud upgrades affect Deck?
Nextcloud releases a new major version every four months and supports each for one year, so Deck must follow the server's upgrade path. Nextcloud does not allow skipping major releases, so the server must move one major version at a time. Administrators should back up before every upgrade and disable third-party apps until they are confirmed compatible with the new release. Review the upgrade manual and the release schedule before planning any upgrade window.
Do attachments and comments survive the move from Trello?
Attachments and comments depend on the export route chosen, and the answer is not the same for every board. Trello's standard JSON export is capped at the 1,000 most recent actions per board, so older comment history may not arrive. Raw attachments are only available through the Premium Workspace export, so confirm your Trello plan before you plan the import. Ask for a sample migration of one representative board and check that comments, attachment files and card links appear as expected in Deck.
Is Nextcloud Enterprise required to run Deck?
No, Deck is part of the open-source Nextcloud Server, which is licensed under AGPL-3.0, so no license fee is required to run it. Nextcloud GmbH sells Nextcloud Enterprise separately, with paid maintenance and support tiers aimed at enterprise, public sector and education users. Support contracts are optional, but they change who answers when something breaks. Decide whether your organization needs guaranteed response times, longer maintenance lifecycles or cluster support before you select a tier.
What does a fixed-scope DeployOpen engagement include?
A fixed-scope engagement covers the agreed deliverables, which can include planning the Nextcloud and Deck deployment in your own infrastructure, importing selected boards, customizing and hardening the instance, documenting it and setting up backups. Scope, deliverables and timelines are agreed in writing before work starts, and any ongoing support, upgrades or testing can be added as a retainer. DeployOpen does not publish a price list, so a quote follows from the written scope. Ask for a written list of what is in and out of scope before you sign.
How DeployOpen helps evaluate, implement and migrate Deck
DeployOpen is a Chainscore Labs company that plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own infrastructure. For Trello vs Nextcloud Deck, we start with a written scope that fits how your organization already runs Nextcloud for files and chat, then build and document the boards, users and migration path that follow from it.
How we scope
- Review which Trello boards, members and attachments are in use before any data moves
- Confirm whether Nextcloud is already running, its version and its user directory
- Agree deliverables, timelines and responsibilities in writing before work starts
- Engagements are fixed-scope, with ongoing support available as a retainer
How we build
- Install Nextcloud and Deck in your cloud account, data center or air-gapped network
- Connect directory login through LDAP, OpenID Connect or SAML, as your environment allows
- Configure database, caching, backup and antivirus settings to match your policies
- Test board sharing, permissions and attachment handling against a representative sample
How we hand over
- Document the Deck setup, configuration keys, user roles and backup procedures
- Run the Trello import in a staging instance and record which items did not carry over
- Train board owners on creating boards, cards, labels and sharing inside Nextcloud
- Deliver the upgrade runbook covering one-major-version-at-a-time upgrades and pre-upgrade backups
How we support
- Plan Nextcloud upgrades against the maintenance schedule for the version you run
- Review third-party app compatibility before each upgrade, keeping apps disabled until confirmed
- Offer security testing of the Nextcloud deployment as a fixed-scope engagement
- Provide ongoing support, upgrades and continuous testing through a retainer
