Migrate from Atomic CRM to HighLevel

Atomic CRM Contacts map directly to GoHighLevel Contacts. Each record carries UUID primary key, name fields, email, phone, company association (via foreign key to the companies table), and any custom columns discovered in the Postgres schema. We resolve the company reference by looking up the source company UUID against the Companies migration map to populate the GoHighLevel Contact's company or agency association. UUIDs do not carry forward — each GoHighLevel Contact receives a new system-generated ID.

Atomic CRM Company records map to GoHighLevel Contacts with the business name as the primary identifier, or to GoHighLevel Companies if the destination account uses the Companies object. We determine the preferred target object during scoping based on the customer's GoHighLevel account configuration. Website, address, and custom fields migrate to matching GoHighLevel custom fields that we create before import.

Atomic CRM Deals map to GoHighLevel Opportunities. Deal title, value, and close date transfer directly. Pipeline stage and deal category are stored as TypeScript props in App.tsx, not in the Postgres schema — we capture these enum values during scoping and pre-create the GoHighLevel pipeline with matching stage names before migration begins. Any custom columns on the deals table become GoHighLevel Opportunity custom fields.

Atomic CRM does not store pipeline stage definitions in the database — stages are passed as CRM component props in App.tsx. We request the App.tsx configuration file during discovery to extract the stage names, their order, and any probability or status values. We then create the corresponding GoHighLevel Pipeline and stages manually before importing any Deal records. The customer replicates the stage configuration in their GoHighLevel account before we begin the Opportunity import phase.

Task types (Call, Email, Meeting, and any custom types) in Atomic CRM are defined as a TypeScript enum passed to the CRM component — not stored in the database. We extract the enum values from the shared App.tsx configuration file and create a corresponding dropdown custom field in GoHighLevel Tasks before migration. We then set the task_type__c field on each migrated Task record to the matching source value. Without App.tsx, the task type is unknown and all imported tasks receive a default classification.

Atomic CRM Notes linked to Contacts or Deals migrate to GoHighLevel Notes attached to the corresponding Contact or Opportunity. Note body and timestamp transfer directly. We preserve the parent reference by resolving the source record UUID to the newly created GoHighLevel ID using the UUID-to-ID map built during the Contact and Deal import phases.

Atomic CRM owner references use Supabase Auth UUIDs. We extract every distinct UUID appearing on Contacts, Companies, Deals, and Tasks, then request a list of active GoHighLevel Users matched by email address. We build a UUID-to-User-ID lookup table before importing any records. Any owner without a matching GoHighLevel User is flagged in a reconciliation report and held from import until the customer provisions the missing User account.

Custom fields in Atomic CRM are Postgres columns added through Supabase Studio — not managed in any application UI. We run a pre-migration schema diff against a reference export to enumerate every column on every table. Each column maps to a GoHighLevel Custom Field created on the corresponding object before data import. Column type mapping from Postgres data types (varchar, integer, boolean, timestamp, jsonb) to GoHighLevel field types is handled in this configuration phase. Schema discovery must be complete before any record import begins.