Migrate from Atomic CRM to Pipedrive

Atomic CRM Contacts map to Pipedrive Person records. We determine whether each Contact should be created as a Lead or a Person based on deal association: Contacts linked to at least one Deal in Atomic CRM become Pipedrive Persons attached to an Organization; Contacts with no deal history and no company association become Pipedrive Leads. We preserve the original email address as the primary key for deduplication.

Atomic CRM Company records map directly to Pipedrive Organization. The company sector, website, and phone fields map to Pipedrive's standard fields. Organization is created before any Person import so that the Org ID is resolved at Person insert time. Multi-address support in Pipedrive accommodates any company addresses stored in Atomic CRM custom columns.

Atomic CRM Deals map to Pipedrive Deals. The deal category (e.g. eCommerce, SaaS, Consulting) maps to a Pipedrive Pipeline that we configure before migration using the category values extracted from App.tsx. Deal value, stage, expected close date, and custom fields migrate directly. We resolve the linked Organization ID at migration time using the company name match against the destination Organizations table.

Each deal category defined in App.tsx becomes a Pipedrive Pipeline. The stage labels and probability percentages (e.g. Qualified, Proposal Sent, Won, Lost) migrate as Pipeline stages with corresponding probability values. We extract the exact enum values from App.tsx and create matching Pipedrive stages in the same order so that deal progress reporting is preserved without rework.

Atomic CRM Notes link to either a Contact or a Deal via a polymorphic or foreign-key relationship. We migrate Notes as Pipedrive Notes attached to the corresponding Person or Deal using the resolved destination record IDs. Note timestamps are preserved as the Note's pinned timestamp in Pipedrive.

Atomic CRM Tasks map to Pipedrive Activities. The task type (Call, Email, Meeting) is extracted from App.tsx as a TypeScript enum and recreated as Pipedrive Activity types from the Growth tier or as standard types on Lite. Task status (pending, completed) maps to Pipedrive done flag. Assignee is resolved by matching the Supabase Auth UUID to the Pipedrive User ID via email lookup.

Any column added to the Contacts, Companies, or Deals tables in Supabase Studio (beyond the standard schema) becomes a Pipedrive custom field. We inspect the Postgres information_schema.columns output to enumerate every column, infer the Postgres data type (varchar, integer, boolean, timestamp, etc.), and map it to the corresponding Pipedrive field type (string, int, set, date). The customer approves the field mapping before any data is written to Pipedrive.

Atomic CRM owner assignment on Deals and Tasks references Supabase Auth UUIDs. We extract all distinct owner UUIDs from the database, match them to Pipedrive Users by email address (the standard Supabase Auth identifier), and hold any unresolved owners in a reconciliation queue. The customer provisions Pipedrive User seats for any missing accounts before record import resumes.

Atomic CRM attachments stored in Supabase Storage buckets are not migratable through a native export API. If the customer provides bucket credentials and explicit write access to the destination, we export the bucket contents as binary files and attach them to the corresponding Pipedrive Deal or Person records. Files stored outside Supabase (e.g. a custom S3 configuration) require separate coordination and are outside standard scope.

If Atomic CRM stores tag data as a text array or related table in Postgres, we migrate tags as Pipedrive Labels attached to the corresponding Person, Organization, or Deal. Label creation is idempotent — duplicate label names are deduplicated on the destination before assignment.