Migrate your Atomic CRM data
Open-source React/Supabase CRM toolkit for developers who need full control over data model, UI, and business logic rather than a turnkey sales tool.
In its favor
Why people choose Atomic CRM
The signal that keeps Atomic CRM on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Developers choose Atomic CRM for complete source-code ownership — the MIT license means they can modify the CRM, host it themselves, and never be locked into a vendor's pricing or roadmap.
Technical teams use it as a base to build industry-specific CRMs for real estate, B2B SaaS, or niche verticals where off-the-shelf platforms require too much workaround.
Small teams that need a lightweight CRM without per-seat SaaS fees adopt it to avoid recurring costs of HubSpot or Salesforce on a budget.
React developers adopt it for rapid prototyping because the shadcn/ui components, Refine data layer, and Supabase backend compose into a working CRM in days rather than months.
Organizations with strict data residency requirements choose it because self-hosting Atomic CRM on their own infrastructure keeps customer data entirely on-premises.
Non-technical teams hit a dead end — Atomic CRM ships without a graphical UI for custom fields, user management, or pipeline configuration, requiring developer involvement for any change.
The platform lacks out-of-the-box automation, email sequences, and reporting dashboards that sales teams expect from mainstream CRMs, causing adoption to stall after initial setup.
Scaling beyond a few hundred active records surfaces the gap between a developer template and a production-grade SaaS — no SLA, no dedicated support, no built-in caching or performance tooling.
Teams that grow beyond one or two developers find the maintenance burden high — every upgrade to React, Supabase, or shadcn/ui risks breaking customizations without a test suite to catch regressions.
When a co-founder or the single developer maintaining the instance leaves, the CRM becomes orphaned code that nobody else on the team can safely modify or extend.
Reasons to switch
Why people leave Atomic CRM
The recurring reasons buyers give for replacing Atomic CRM. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Atomic CRM 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
Atomic CRM pricing overview
Atomic CRM is MIT-licensed open source — the self-hosted Open-Source tier is free with unlimited data and storage on your own Supabase project or infrastructure. Marmelab also sells managed hosting in three tiers: Starter at €25/month for up to 1,000 contacts and 1 GB storage; Team at €50/month for up to 10,000 contacts and 10 GB storage; and Enterprise with custom pricing for unlimited contacts, dedicated infrastructure, and priority support. All managed tiers include SAML 2.0 SSO, email integration, and API access.
Open-Source (self-hosted)
Tier 1 of 4
Free (MIT license)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Atomic CRM's schedule — see our quote-based pricing →
What gets migrated
Atomic CRM object support
Object-by-object support for Atomic CRM migrations. Per-pair details surface during scoping.
Contacts
Fully supportedCore entity storing name, email, company association, and custom fields. Standard Supabase-backed table with predictable UUID primary keys. We migrate Contacts with their full field set and preserve the company relationship.
Companies
Fully supportedCompany/Account records that Contacts link to. Exposed as a Supabase table with a one-to-many relationship to Contacts. We migrate Companies first to maintain referential integrity during import.
Deals
Fully supportedDeal records with configurable categories (e.g. eCommerce, SaaS, Consulting) set as props on the CRM component. Stored in Supabase with optional custom fields. We map pipeline stage and deal value directly to the destination equivalent.
Notes
Fully supportedFree-text notes linked to Contacts or Deals. Supabase table with a polymorphic or foreign-key relationship. We migrate notes with their parent reference preserved.
Tasks
Fully supportedTask types (Call, Email, Meeting) are configurable props passed to the CRM root component. Tasks are stored in Supabase with status and assignee fields. We preserve task type classification and owner assignment.
Custom Fields
Mapping requiredCustom fields are added directly in Supabase Studio to existing tables. There is no UI for managing custom fields in the CRM itself — this is a developer-managed schema change. We audit the Supabase schema pre-migration and replicate all custom field definitions at the destination.
Users
Mapping requiredUser management is built in with Supabase Auth. Owner/User assignment on Deals and Tasks references auth UUIDs. We map source users to destination users by email, not by UUID.
Attachments
Not in this platformAtomic CRM stores attachment metadata in Supabase but the actual file handling depends on the hosting setup (local or Supabase Storage). We do not migrate binary blob storage unless explicit file-hosting configuration is documented.
| Object | Support | Notes |
|---|---|---|
| Contacts | Fully supported | Core entity storing name, email, company association, and custom fields. Standard Supabase-backed table with predictable UUID primary keys. We migrate Contacts with their full field set and preserve the company relationship. |
| Companies | Fully supported | Company/Account records that Contacts link to. Exposed as a Supabase table with a one-to-many relationship to Contacts. We migrate Companies first to maintain referential integrity during import. |
| Deals | Fully supported | Deal records with configurable categories (e.g. eCommerce, SaaS, Consulting) set as props on the CRM component. Stored in Supabase with optional custom fields. We map pipeline stage and deal value directly to the destination equivalent. |
| Notes | Fully supported | Free-text notes linked to Contacts or Deals. Supabase table with a polymorphic or foreign-key relationship. We migrate notes with their parent reference preserved. |
| Tasks | Fully supported | Task types (Call, Email, Meeting) are configurable props passed to the CRM root component. Tasks are stored in Supabase with status and assignee fields. We preserve task type classification and owner assignment. |
| Custom Fields | Mapping required | Custom fields are added directly in Supabase Studio to existing tables. There is no UI for managing custom fields in the CRM itself — this is a developer-managed schema change. We audit the Supabase schema pre-migration and replicate all custom field definitions at the destination. |
| Users | Mapping required | User management is built in with Supabase Auth. Owner/User assignment on Deals and Tasks references auth UUIDs. We map source users to destination users by email, not by UUID. |
| Attachments | Not in this platform | Atomic CRM stores attachment metadata in Supabase but the actual file handling depends on the hosting setup (local or Supabase Storage). We do not migrate binary blob storage unless explicit file-hosting configuration is documented. |
Gotchas
What to watch for in Atomic CRM migrations
Issues we've hit on past Atomic CRM migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No hosted SaaS version — migration target is a Postgres database
Custom fields are schema changes, not UI-configured properties
CRM component props define business logic that lives in code, not data
No native file attachment export — storage backend varies by deployment
| Severity | Issue |
|---|---|
| High | No hosted SaaS version — migration target is a Postgres database |
| High | Custom fields are schema changes, not UI-configured properties |
| Medium | CRM component props define business logic that lives in code, not data |
| Medium | No native file attachment export — storage backend varies by deployment |
Leaving Atomic CRM?
Where Atomic CRM customers move next
12 destinations Atomic CRM can migrate to.
How a Atomic CRM migration works
Four steps, Atomic CRM-specific
Connect
Supabase Auth (JWT-based) on the underlying Postgres; no separate Atomic CRM API surface into Atomic CRM. Scopes limited to read-only on the data we move.
Map
We translate Atomic CRM-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Atomic CRM quirks before production.
Migrate
Full migration with Atomic CRM rate-limit handling. Rollback available throughout.
FAQ
Atomic CRM migration FAQ
Answers to the questions buyers ask most during Atomic CRM migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Atomic CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Atomic CRM.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Atomic CRM setup and destination — written quote back within a business day.