Attio is a SaaS CRM built around flexible objects and lists, priced per seat with object and record limits per plan. Pages here cover moving to Twenty, the open-source CRM with a similar model.
Comparing Attio with Twenty, the open-source CRM with custom objects, views and workflows: how object and record limits per plan compare with Twenty's unlimited objects, email and calendar sync, APIs, and what self-hosting Twenty on PostgreSQL and Redis involves.
Moving from Attio to self-hosted Twenty: exporting each object and list view, handling enriched fields that export blank, recreating objects and relations in Twenty, importing records and rebuilding automations.
Cost of ownership by component: Attio seats and the plan upgrades that object and record limits force, against Twenty's free self-hosted core or paid cloud plans, servers, upgrades and administration.
What Attio exports, view by view as CSV or Excel, what stays behind such as enriched data, who is allowed to export, and a checklist for a complete export before leaving.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.