Migrate from Simply CRM to HubSpot

Simply CRM contacts map directly to HubSpot contacts. The contact's primary account link resolves to HubSpot's primary company association. Emails, names, phone numbers, job titles, and addresses transfer as HubSpot properties. Owner assignment resolves by email match against HubSpot users.

Simply CRM leads have no direct HubSpot equivalent because HubSpot consolidates leads and contacts into one object. Lead records migrate as HubSpot contacts with a lifecycle_stage property value of 'lead'. Lead status (New, Assigned, Converted) is preserved as a custom property.

Simply CRM accounts map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue transfer as matching HubSpot company properties. Parent-account hierarchies in Simply CRM map to HubSpot's parent company field if configured. If a parent-account hierarchy exists, the top-level account becomes the primary HubSpot company, and child accounts are linked via the parent‑company association to preserve organizational context.

Simply CRM deals migrate to HubSpot deals with deal name, amount, close date, and stage. Stage values are mapped value-by-value to the corresponding HubSpot pipeline stage name. Probability percentages are stored as a custom field since HubSpot stage probabilities are not exposed as importable properties.

If Simply CRM uses multiple pipelines (via custom modules or separate modules), each pipeline becomes a separate HubSpot deal pipeline. HubSpot allows multiple pipelines with independent stage sets. The migration plan specifies the pipeline name and stage list before the import runs.

Simply CRM logged calls transfer as HubSpot call engagement records on the associated contact timeline. Duration, call date, direction (inbound/outbound), and disposition notes migrate as engagement metadata properties. Owner and original timestamp are preserved. Call recordings, if stored in Simply CRM, are downloaded and attached to the HubSpot call engagement as a file link, allowing users to playback directly from the contact record.

Logged emails in Simply CRM migrate as HubSpot email engagements on the contact timeline. Subject line, body content, timestamp, and associated contact links are preserved. Attachments are downloaded and re-uploaded to HubSpot file storage. Email headers, including the sender and recipient addresses, are captured in HubSpot's engagement metadata to maintain full context for future reference and reporting.

Simply CRM meetings (with subject, start/end time, location, and attendees) migrate as HubSpot meeting engagements on the contact timeline. Original meeting start/end timestamps and the meeting title are preserved. Attendee contact links are rebuilt in HubSpot. If a meeting includes external guests without a HubSpot contact record, FlitStack AI creates a placeholder contact to link the meeting, ensuring the engagement timeline remains complete.

Simply CRM notes transfer as HubSpot contact or company notes with the original body text, author (matched by email to HubSpot user), and creation timestamp. Rich-text formatting is preserved where Simply CRM stores it as HTML. If a note references other records, such as linked deals or tasks, FlitStack AI maps those associations to HubSpot's note-to-record links, maintaining relational integrity across the migrated dataset.

Open and completed tasks in Simply CRM migrate as HubSpot tasks with subject, due date, status, priority, and associated contact link. Completed tasks are marked done in HubSpot. Uncompleted tasks retain their open status. If a task's assigned user does not have a HubSpot owner record, FlitStack AI flags the task for owner mapping and allows your team to assign a fallback owner before the migration runs.

Simply CRM custom fields on contacts are read from the API and created as HubSpot contact properties before import. Property type is inferred from Simply CRM's field type (text, number, date, picklist). Pick-list custom fields use HubSpot option maps. If a picklist contains values not present in HubSpot's default set, FlitStack AI creates a custom option list and maps each legacy value to the new options, preserving the original data semantics.

Simply CRM custom fields on deals are created as HubSpot deal properties before migration. Number and currency fields transfer directly. Text fields become string properties. Date fields use HubSpot date property type. If a custom field stores a multi-select picklist, FlitStack AI creates a HubSpot checkbox or multi-checkbox property and maps each selected value, ensuring no data loss during the import.

Simply CRM document attachments associated with contacts, accounts, or deals are downloaded, then uploaded to HubSpot Files. They are linked back to the associated contact or deal record via HubSpot's file-to-record association model. File metadata such as the original upload date, file size, and author information is preserved as HubSpot file properties, enabling accurate recordkeeping and searchability within the platform.