Migrate from Atomic CRM to HubSpot

Atomic CRM contacts map 1:1 to HubSpot contacts. The primary email address becomes HubSpot's Email property. A contact's associated company resolves via the contacts.company_id foreign key, creating an association in HubSpot. If a contact has no company link, it lands as a standalone contact record.

Atomic CRM companies map to HubSpot companies. Company domain, name, industry, and employee count translate to HubSpot's domain, name, industry, and numberofemployees properties. Parent-child company hierarchies (if implemented via Supabase self-referential foreign key) map to HubSpot's parent company association. Additional company metadata such as annual revenue, phone number, and address information transfers directly to corresponding HubSpot properties, preserving all relevant firmographic data during the migration.

Atomic CRM deals map to HubSpot deals. The deal name maps to dealname, amount maps to amount, expected_close maps to closedate, and status maps to dealstage. The dealcategory field is analyzed for unique values — each distinct value becomes a HubSpot pipeline name or a stage within the default pipeline.

Atomic CRM has no pipeline concept — dealcategory is a freeform text field. FlitStack AI extracts all unique dealcategory values, counts deal records per category, and proposes a HubSpot pipeline configuration: one pipeline per dominant category, or stages named after category values within a single pipeline. Your team approves the pipeline map before migration.

Atomic CRM taskTypes are configurable (default: Call, Email, Meeting). Each task type maps to the corresponding HubSpot engagement type. The task title becomes the engagement subject, the body or description becomes the engagement text body, and original timestamps are preserved. Untyped tasks land as generic HubSpot tasks.

Atomic CRM notes map to HubSpot engagement notes. The note body becomes the engagement text body, and the note is associated to the correct contact or company record via HubSpot's association API. Rich-text formatting is preserved where the source data contains it.

Any custom column added to contacts, companies, or deals via Supabase Studio becomes a HubSpot custom property. Field type mapping: PostgreSQL text/varchar → HubSpot string; boolean → HubSpot boolean; integer/numeric → HubSpot number; date → HubSpot date; JSON → HubSpot string (serialized). Properties are created in HubSpot before records are imported.

Atomic CRM owner records (or the assigned_user_id on each record) are resolved by email match against HubSpot user accounts. Unmatched owners are flagged as a pre-migration action item — either invite them to HubSpot or assign their records to a fallback HubSpot user. No record lands without a valid HubSpot owner.

HubSpot's built-in createdate timestamp is set at import time and cannot reflect the original Atomic CRM create date. We preserve the original timestamp as a custom property (e.g., original_createdate) on each record so reporting continuity is maintained. This preservation ensures that all historical reporting based on creation dates remains accurate in HubSpot, and your team can maintain complete audit trails without losing the original record creation context.

Similarly, HubSpot's lastmodifieddate reflects the import time. The original last-modified timestamp from Atomic CRM is stored as a custom property (e.g., original_updatedate) to support audit trails and change-history reporting after cutover. This approach maintains the integrity of your change history by preserving exactly when records were last updated in Atomic CRM, enabling accurate reporting on record modification patterns and supporting compliance requirements that depend on maintaining original modification timestamps.

If Atomic CRM implements tagging via a Supabase junction table, the tag names are extracted and mapped to a HubSpot contact property. Single-value tags become string properties; multi-value tags become HubSpot multi-checkbox properties with each unique tag as an option.

Atomic CRM's Supabase authentication settings (row-level security policies, user roles, SSO configuration) are Supabase infrastructure and have no HubSpot equivalent. These must be re-implemented as HubSpot user roles and permission sets post-migration. FlitStack exports a permission matrix for your HubSpot admin to reference.

Atomic CRM's custom React component configuration, shadcn/ui theme settings, and page-level customizations are a front-end concern with no HubSpot analogue. These do not migrate. Teams should treat the migration as a data-only transition and plan HubSpot UI customization separately. This includes designing custom HubSpot layouts, configuring theme colors and branding elements, and setting up any specialized page elements that were part of your Atomic CRM user experience.

If Atomic CRM stores file attachments in Supabase Storage, those files are downloaded and re-uploaded to HubSpot Files. Each file is attached to its originating record (contact, company, or deal) via HubSpot's file association API. File size limits follow HubSpot's 25MB per-file ceiling.