Twenty CRM update: new features up to version 2.0 and skipping versions on upgrade

Using or planning Twenty CRM? We install, operate and update Twenty for you - learn more about Twenty hosting, operation & support at WZ-IT or arrange a consultation directly.

At WZ-IT, we use Twenty CRM ourselves as our central customer management system. It is lean, modern, completely open source and fits perfectly with our claim to operate data in compliance with the GDPR and without vendor lock-in.

That's why we take a close look at each release. This article started as an overview of 1.3.0 and 1.4.0 and is now updated: since then Twenty has made the jump to version 2.0 (as of June 2026: the 2.x series), and upgrading has become much simpler - jumping across versions without any intermediate step is now possible.

Table of Contents

• Twenty CRM 1.3.0 - August 9
• Twenty CRM 1.4.0 - August 21
• From 1.4.0 to version 2.0
• Jump straight to the latest version (from v1.22)
• Conclusion

Twenty CRM 1.3.0 - August 9

Merge Records - simply merge duplicates

One of our favorite features: from version 1.3.0, duplicate entries in the CRM can be easily merged. Instead of manually checking and transferring data, two data records can be merged with a click - including their links and histories. This ensures clean master data and saves an enormous amount of time.

IMAP & CalDAV

With IMAP support, mailboxes can now be connected directly to pull incoming emails into the CRM. There is also CalDAV sync so that calendars can be connected to Twenty.

Import Relations

Relationships between data records can now be set during CSV import - e.g. linking contacts to companies or assigning tasks to projects.

Any Field Filter

A new search filter allows you to search across all fields. This is useful if, for example, you know a telephone number but are not sure in which field it was entered.

Twenty CRM 1.4.0 - August 21

Field Level Permission

Rights management has become more granular: individual fields can now be made read-only or editable for certain roles. This complements the previous object authorizations and enables finer-grained security and compliance setups.

Workflow Filters

Workflows can now be extended with filter conditions. This means automations only continue to run if defined criteria are met - ideal for complex business processes.

Two-Factor Authentication

Another new feature is 2FA with apps such as Authy or 1Password. An important security measure for many environments - but less relevant in our setup, as we secure Twenty CRM behind Cloudflare Zero Trust anyway.

From 1.4.0 to version 2.0

A lot has happened since 1.4.0 (summer 2025). Across the 1.x line, practical features were added step by step, including file attachments on records, an "Updated by" field for traceability, self-hosted billing, customizable sidebars with favorites and a significantly improved AI chat.

The real milestone is Twenty 2.0, released on April 21, 2026. It turns the CRM into an extensible platform:

• App development platform: model your own data, add business logic and design layouts to build apps on top of Twenty.
• AI features: agents, chat and compatibility with the Model Context Protocol (MCP) - AI can access the CRM in a structured way.
• Git-backed workspace versioning: workspaces can be versioned via git repositories, with branching and rollback.
• Freely designed layouts: build record pages and dashboards from widgets via drag-and-drop.
• Developer workflow: scaffold directly from Claude Code, Cursor or the CLI.

Twenty has moved quickly since: as of June 2026, the 2.x series is at version 2.12 with further integrations, UI improvements and ongoing security patches. Twenty maintains the full, continuous changelog in its official releases.

Jump straight to the latest version (from v1.22)

For self-hosted instances, updating used to be tedious: you had to move from version to version and run each migration individually. That is over.

Since v1.22, Twenty supports cross-version upgrades. According to the upgrade guide: you can jump from any supported version straight to the latest release without stepping through each intermediate version - for example from v1.22 directly to 2.0.

The threshold matters: if your instance is older than v1.22, you must first upgrade incrementally through each major tagged version (v1.6 to v1.7, v1.7 to v1.8 and so on) until you reach v1.22. From there, the direct jump is possible.

In practice:

• Migrations run automatically on server startup - no manual upgrade command is needed.
• The upgrade:status diagnostic command lets you inspect the state of instance and workspace migrations, which helps when debugging or filing a support request.
• This is enabled by version-aware schema management (columns are marked with their added/removed version), so Twenty correctly reconstructs the path across multiple versions.

Despite the automation: back up before every upgrade, and test larger jumps in a staging environment first. Especially when moving from 1.x to 2.0, the architecture and some defaults change.

Our approach at WZ-IT

We run Twenty CRM in production and update it as a managed service. For a version jump, we back up the instance and database, test the upgrade in a staging environment, run the actual update with a controlled cutover and then verify with upgrade:status that all migrations completed cleanly. This keeps the CRM current without your team having to worry about migration paths.

Further guides

• Install Twenty CRM with Caddy and automatic SSL certificates - getting started with your own instance.
• Managed Open Source at WZ-IT - hosting and operation for Nextcloud, GitLab, Mattermost, Twenty and more.
• Twenty hosting, operation & support - our services around Twenty CRM.

Conclusion

With version 2.0, the lean open-source CRM has become an extensible platform - with an app framework, AI integration and git-backed versioning. At least as important for operations: cross-version upgrades from v1.22 finally make updating straightforward, because the jump to the latest version no longer has to run through every intermediate version.

If you self-host Twenty, you should bring your instance to at least v1.22 - after that, a single jump keeps you current.

Want to adopt, update or run Twenty CRM in production? We handle installation, updates and managed hosting - GDPR-compliant and without vendor lock-in. Arrange a consultation now.

Sources

• Twenty Upgrade Guide (self-hosting)
• Twenty Releases
• Twenty Releases on GitHub
• heise online: Twenty 2.0 - The open-source CRM follows up