Migrate from Simplicity Enterprise CRM to HubSpot

Simplicity lifecycle and segmentation data requires transformation before it maps to HubSpot lifecycle_stage and lists

Simplicity Enterprise CRM tracks contact qualification through behavioral segmentation lists and profile property logic rather than a single lifecycle_stage property. HubSpot's lifecycle_stage is a discrete pick-list field on the Contact record. When migrating from Simplicity, FlitStack must evaluate each contact's segment membership and profile properties to determine the appropriate HubSpot lifecycle_stage value. Contacts that were in multiple Simplicity segments may need a priority rule applied — the highest-urgency segment (e.g., 'qualified opportunity') wins over lower-priority segments (e.g., 'newsletter subscriber'). Simplicity behavioral data that cannot resolve to a single lifecycle_stage value is preserved as custom properties on the HubSpot contact record so your team can use HubSpot Smart Lists to apply lifecycle_stage manually after migration based on the preserved segment data.

HubSpot file import limit of 20MB per CSV may require chunked migration for large datasets

HubSpot's bulk import accepts CSV files up to 20MB per import batch. Simplicity Enterprise CRM migrations with large contact databases or extensive activity history may exceed this limit. FlitStack chunks large record sets into multiple import batches, maintaining referential integrity across batches by processing parent objects (Companies, then Contacts, then Deals) before child records. For activity history — call logs, emails, meetings, notes — FlitStack uses HubSpot's batch engagement API which has separate rate limits per engagement type. The migration plan includes a pre-migration size audit that flags which record sets require chunking, so no batch fails at import time due to HubSpot's file size constraint. If your Simplicity data export exceeds 20MB in any single object batch, FlitStack splits the import and validates that the aggregate record count matches the source after all batches complete.

HubSpot Starter and Professional tiers cannot receive custom object migrations — Enterprise tier required

Simplicity Enterprise CRM's configurable data structure often includes custom objects beyond contacts, companies, and deals — particularly for campaign tracking, loyalty data, or product configurations. HubSpot's Custom Objects feature is gated behind the Enterprise tier of Sales Hub, Service Hub, or Marketing Hub. If your destination HubSpot account is on Starter or Professional tier, any custom objects in Simplicity cannot be imported as HubSpot Custom Objects — they must be flattened into custom properties on standard HubSpot objects (Contact, Company, Deal) or stored as HubSpot company-level properties. FlitStack surfaces this constraint during the pre-migration audit and presents two options: upgrade the HubSpot account to Enterprise before migration, or flatten the Simplicity custom objects into HubSpot custom properties. Flattening trades object-level querying for property-level filtering in Smart Lists and workflows. Your team decides the approach before migration begins.

Simplicity campaign association data has no 1:1 equivalent in HubSpot — campaign context requires reconstruction

Simplicity's campaign management module tracks multi-channel campaign membership (email, social, event) with attribution data that spans contacts and companies. HubSpot's Campaigns object tracks campaign membership for email marketing specifically, but it does not natively capture cross-channel campaign attribution for contacts who interacted through multiple channels in the same campaign. When migrating Simplicity campaign data, FlitStack maps campaign membership to HubSpot Lists (one list per Simplicity campaign) and stores campaign metadata (name, channel, start/end dates) as custom properties on each list. Cross-channel attribution data from Simplicity — such as which contacts received both an email touch and a social touch within the same campaign — is preserved as a custom property (campaign_touchpoints_detail) on the contact record. Your HubSpot admin can use this data to manually segment contacts or to inform rebuild decisions for HubSpot's campaign attribution reporting.

HubSpot's duplicate detection may reject Simplicity contacts with identical email addresses

Simplicity Enterprise CRM sometimes stores duplicate contact records — either from data entry errors or because the same person appears under multiple business affiliations within the platform. HubSpot's import process detects contacts with matching email addresses and either merges them or flags them as duplicates depending on your HubSpot duplicate detection settings. FlitStack runs deduplication logic before import: when two Simplicity contact records share an email address, the record with the more recent last-modified date is preserved and the other is merged into it, with the merged record's custom property values appended rather than overwritten. If both records have the same last-modified date, FlitStack preserves the record with more filled fields. Your team receives a pre-migration deduplication report showing which Simplicity records were merged and why, so you can verify the merge logic before the full migration commits.