Migrate from HaystackCRM to HubSpot

HaystackCRM contact maps to HubSpot contact. All standard fields (name, email, phone, jobtitle) transfer directly. HubSpot contact properties include lifecycle_stage (which HaystackCRM has no equivalent for — defaulting to 'subscriber' unless a deal is attached). Owner resolved by email match to HubSpot user.

HaystackCRM company maps to HubSpot company. Company name, domain, industry, employee count, and annual revenue transfer as HubSpot standard properties. Multi-company contacts (HaystackCRM supports associating one contact with multiple companies) map to HubSpot's primary company plus additional company associations via the Company Associations API.

HaystackCRM opportunity maps to HubSpot deal. The deal name, amount, and close date transfer directly. The pipeline stage label from HaystackCRM maps to a HubSpot deal pipeline stage — if HaystackCRM has a single pipeline, a single HubSpot deal pipeline is created. Temperature field (Hot/Warm/Cold) migrates as a custom pick-list property (Deal_Temperature__c) since HubSpot deals have no native temperature rating.

HaystackCRM's team feature assigns records to regional or functional teams. HubSpot does not have team-based data ownership scoping — records are owned by individual users. We resolve each HaystackCRM team member by email match to a HubSpot user. Team-level visibility rules are translated to HubSpot Team Groups for organizational grouping, not data access control.

HaystackCRM tasks map to HubSpot engagements with type='task'. Task subject, due date, status, and assigned-to owner transfer directly. HubSpot engagements store the original task owner and timestamp for full audit trail. Overdue task status in HaystackCRM maps to HubSpot's task completion flag — completed tasks retain their original due date while open tasks appear in the HubSpot task queue with appropriate follow-up reminders based on the migration timestamp.

HaystackCRM events map to HubSpot engagements with type='meeting'. Event subject, start and end time, location details, and associated contact or opportunity links transfer completely. Original event creation timestamp and assigned owner are preserved on the HubSpot engagement record, maintaining the full activity history for reporting. Meeting notes or descriptions attached to the event migrate as engagement metadata.

HaystackCRM quotes linked to an opportunity transfer as HubSpot deal-line-item associations. The quote PDF itself cannot transfer (HaystackCRM stores PDFs in its own file storage) — we re-upload the PDF to HubSpot's file manager and link it to the deal record. Quote status (sent, accepted, declined) maps to a custom pick-list property on the deal.

HaystackCRM tags are flat string labels on contacts and companies. Tags transfer to HubSpot as a multi-select contact property (Contact_Tags__c) and company property (Company_Tags__c). If tags represent lead sources or segments, we document the value list for re-building as HubSpot static lists or dynamic lists with filter rules.

HaystackCRM custom fields on contacts transfer to HubSpot custom contact properties. Field type mapping is type-aware: text fields map to text, number fields map to number, date fields map to date, and pick-list fields map to HubSpot pick-lists with matching option values. Multi-select pick-lists in HaystackCRM map to HubSpot multi-checkbox properties, preserving all selected values. The custom field inventory is delivered before migration so HubSpot properties can be pre-created.

HaystackCRM custom fields on companies transfer to HubSpot custom company properties following the same type-aware mapping as contact fields. Text, number, date, and pick-list field types map directly to their HubSpot equivalents. Company-level numeric fields such as custom revenue or employee metrics map to HubSpot number properties. Multi-select pick-lists transfer as multi-checkbox properties. The field inventory is reviewed before migration to confirm all properties exist in HubSpot.

HaystackCRM custom fields on opportunities transfer to HubSpot custom deal properties. All field types are mapped type-aware: text, number, date, and pick-list fields transfer to matching HubSpot property types. Multi-select pick-lists become multi-checkbox properties. The complete field mapping plan is delivered before migration so HubSpot properties can be pre-created in the target portal — HubSpot requires all custom properties to exist before bulk import references those field names.

HaystackCRM file attachments on contacts, companies, or opportunities are downloaded and re-uploaded to HubSpot's file manager. Files are linked to the corresponding HubSpot record via the file associations API. HaystackCRM's Dropbox/iCloud/OneDrive integration attachments transfer from HaystackCRM storage only — any files stored directly in those cloud services require separate export.

HaystackCRM's automatic email ingest (Gmail/Outlook 365 integration) stores email threads as contact activity. These transfer to HubSpot as engagement records with type='email'. The original email body, timestamp, sender, and recipient are preserved. HubSpot's email tracking and logging behavior matches HaystackCRM's inbox-logging model.