Migrate from noCRM.io to HubSpot

noCRM Lead splits into two HubSpot objects: the embedded contact data (name, email, phone, title) maps directly to HubSpot Contact. Original noCRM Lead ID is stored on the HubSpot Contact as an internal reference property for traceability. This mapping also preserves the original noCRM step value in a custom property, allowing reporting on lead status after migration.

noCRM stores company as a free-text or custom field inside the Lead record. FlitStack creates a corresponding HubSpot Company record for each unique company value found, then links the Contact to it via HubSpot's Associations API. Circular references and duplicate company names are flagged before insertion.

When noCRM step equals Won, FlitStack creates a HubSpot Deal record linked to the migrated Contact and Company. The deal amount and close date are sourced from noCRM Dream-tier custom fields or the lead's last-modified date as a proxy. This gives the sales team a pipeline view in HubSpot that mirrors noCRM's winning-step perspective.

noCRM's step field (To-Do, Standby, Won, Lost, Cancelled) maps to HubSpot Deal stage values. Each noCRM step requires a value-by-value mapping to the corresponding HubSpot pipeline stage name. Lost and Cancelled steps map to HubSpot Closed Lost; Won maps to Closed Won.

noCRM tags are flat string labels on a lead. FlitStack maps tags to HubSpot contact properties — a dedicated multi-picklist property (e.g., nocrm_tags) captures all original tags so teams can filter HubSpot contacts by noCRM origin without losing segmentation context.

noCRM comment threads map to HubSpot's engagement timeline as note-type activities with the original author and timestamp preserved. Each comment appears as a separate timeline entry on the Contact record so the conversation history is searchable in HubSpot. Attachments linked to a comment are likewise imported as file associations, keeping the full context of each interaction.

File attachments on noCRM leads are downloaded from the noCRM storage URL, re-uploaded to HubSpot's File Manager, and associated with the Contact record. Original filenames and file-type metadata are preserved. Files larger than 25 MB are split or flagged for manual handoff.

HubSpot's native Createdate and LastModified are set at migration time. The original noCRM create date and last-modified date are stored as custom datetime properties (Original_Create_Date__c, Original_Last_Modified__c) on the Contact so historical reporting continuity is maintained. These custom date fields are also used in HubSpot's date-based filters and workflows to trigger follow-ups based on the original noCRM activity timeline.

noCRM Dream-tier custom fields (dates, numbers, pick-lists, checkboxes) are translated into typed HubSpot custom properties under the appropriate object. Field type is inferred from noCRM's field definition; pick-list values are mapped value-by-value. Fields without an obvious HubSpot counterpart are stored as text properties and flagged for admin review.

noCRM user assignments are resolved by email match against HubSpot Users. Unmatched owners are flagged in the migration report; the admin either creates the HubSpot user first or assigns records to a fallback owner. Owner history from noCRM is preserved as a custom audit property.

noCRM's next-action date is a core UX element — reps see their next task directly on the lead card. HubSpot has no native equivalent. FlitStack stores this as a custom datetime property (Next_Action_Date__c) on the Deal so the date remains visible in the HubSpot timeline view.

Beyond Won deals, noCRM leads in any step (To-Do, Standby, Cancelled) can optionally create HubSpot Deals so the full pipeline stage distribution is visible in HubSpot reporting. Teams choosing not to create Deals for early-stage leads have those noCRM leads migrate as Contacts only — flagged with a pipeline stage property for future deal creation.