Migrate from Atomic CRM to Zoho CRM

Atomic CRM Contacts map to Zoho CRM Leads (for unqualified or early-stage records) or Contacts (for qualified records). Since Atomic CRM does not have a Lead object, we apply a split rule during scoping based on the customer's business definition of a qualified contact, typically using a custom field flag, a deal association, or a last-activity threshold. We create both Zoho Leads and Contacts and preserve the full Contact field set on both records for audit. Email addresses serve as the dedupe key.

Atomic CRM Companies map directly to Zoho CRM Accounts. The domain field from the Company record maps to the Account Website field. We load Accounts first in every migration so that the Account-Contact lookup relationship is satisfied at insert time. Any Companies with no associated Contacts are loaded as standalone Accounts.

Atomic CRM Deals map to Zoho CRM Deals. The deal amount, stage, close date, and owner transfer directly. We map the source deal category (stored in App.tsx props, not in the database) to Zoho Deal Stage by pre-creating matching picklist values in Zoho during the configuration phase. Deals without a linked Account are held in a staging queue until an Account is available or the customer confirms they should remain unlinked.

Atomic CRM Notes migrate to Zoho CRM Notes. The note body, author reference, and parent record linkage (Contact, Deal, or Company) transfer. Notes attached to non-existent parent records are logged in the reconciliation report for the customer to resolve before cutover.

Atomic CRM Tasks migrate to Zoho CRM Tasks with Subject, Status, Priority, Due Date, and Owner preserved. Task type classification (Call, Email, Meeting) maps from the type values defined in App.tsx props; we create matching Zoho Task Status values during configuration so that the type distinction is preserved as a custom field rather than collapsed into a single task type.

Custom fields added in Supabase Studio exist as Postgres columns on the standard tables. We discover every column by querying information_schema.columns against each table (contacts, companies, deals, notes, tasks) during scoping. Each column is type-mapped to the nearest Zoho field type: TEXT to Single Line, TEXT long to Multi Line, BOOLEAN to Checkbox, INTEGER or NUMERIC to Currency or Number, DATE to Date. We create the Zoho custom fields via the Fields API before any record migration begins.

Atomic CRM uses Supabase Auth for user identity. Owner and assignee references on Deals and Tasks reference Supabase auth UUIDs. We resolve owners by email match against the Zoho User table. Any Supabase User without a matching Zoho User is placed in a reconciliation queue for the customer to provision before migration resumes.

If the Atomic CRM instance uses Supabase Storage buckets for file attachments, those files live outside the Postgres tables. We export the bucket contents to a local file store during scoping, then upload each file to the corresponding Zoho CRM record as an Attachment via the Zoho Files API. Files are linked to the parent record (Contact, Account, Deal) using the original Supabase storage path as a reference. This step requires the customer to share Supabase Storage credentials and confirm bucket names.

Atomic CRM Deal categories are passed as props to the CRM root component in App.tsx, not stored in the database. We request the App.tsx configuration file during scoping to capture every deal stage label (e.g. Prospect, Qualification, Proposal, Negotiation, Closed Won, Closed Lost). We pre-create matching Zoho Deal Stage picklist values before migration. Any stage not represented in Zoho is added to the picklist in the configuration phase.

Task types in Atomic CRM are configurable props (e.g. Call, Email, Meeting, Follow-up) defined in App.tsx, not stored as a database field. We capture the type enumeration from App.tsx during scoping and create a Zoho custom picklist field Task_Type__c to preserve the classification. This ensures task type is searchable and filterable in Zoho reports and list views.