Migrate from HaystackCRM to Pipedrive

HaystackCRM Companies map directly to Pipedrive Organizations. We export Companies first in every migration to establish the organizational backbone before any Contact or Deal import, since Pipedrive requires an Organization ID or name to satisfy the Organization-People relationship. The Company name field maps to Organization name, and any Company phone, website, or address fields map to the equivalent Organization fields. If multiple Companies share the same name, we append a numeric suffix to prevent duplicate Organizations and document the merge decisions in the scoping deliverable.

HaystackCRM Contacts map to Pipedrive People. Each Contact carries a required link to an Organization (resolved from the Company export), a name, email, phone, and address. We export Contacts second, resolve the Organization reference via the Company name match, and import People with their Organization ID populated. Any Contact without a linked Company receives the customer's default Organization or is flagged for a separate import batch. Custom tag values on Contacts migrate to Pipedrive Labels as a multi-value field.

HaystackCRM Opportunities map to Pipedrive Deals. Each Opportunity carries a dollar value, a pipeline stage, a status (open, won, lost), and a temperature priority (hot, warm, cold). We map the dollar value to Deal value and the temperature priority to a custom Deal field (hs_temperature__c) since Pipedrive Deals do not have a native temperature property. Stage names migrate as-is if they match Pipedrive's default stages, or we pre-create custom stages in Pipedrive to match the HaystackCRM stage vocabulary before import. Deal owner resolves via email match against Pipedrive Users.

HaystackCRM Tasks map to Pipedrive Activities with type=Task. Each Task carries a title, due date, status, and optional Contact or Opportunity linkage. We export Tasks with their parent linkage preserved as raw IDs from the spreadsheet, then resolve the parent reference during import by matching Contact email or Opportunity title within the same Organization. Task assignment resolves via the owner email match against Pipedrive Users. Completed status maps directly; open tasks inherit the Pipedrive default open status.

HaystackCRM Events are calendar-bound records with a start date, end date, title, and optional linked Contact. We export Events as discrete date-bound Activities in Pipedrive with type=Event. The calendar sync links that HaystackCRM maintains with device calendars cannot be reconstructed in Pipedrive and are documented as a manual rebuild item in the handoff deliverable. Attendee information from HaystackCRM Events maps to Activity participants in Pipedrive if present in the export; otherwise the Event is created as a single-participant record.

HaystackCRM Items and the product catalog map to Pipedrive Products. Each Item carries a name, SKU (if set), unit price, and description. We export the full item catalog and import into Pipedrive Products with Standard Price Book entries created during the same import batch. If the catalog includes pricing tiers or quantity-based pricing, we map those to Pipedrive PricebookEntry records with the appropriate pricing model.

HaystackCRM Tags are flat string labels assigned to Contacts, Companies, and Opportunities. They map to Pipedrive Labels, which are also flat. We export all unique tag values across object types, deduplicate, and create Pipedrive Labels during the schema setup phase. Each Contact, Organization, or Deal then receives its label assignments during import. Any tag that served a hierarchical purpose in HaystackCRM (such as category.subcategory conventions) is preserved as a single flat label and documented in the handoff deliverable for the customer to reorganize into Pipedrive Topics if desired.

HaystackCRM Users are assigned as owners of Contacts, Companies, Opportunities, and Tasks. We export the user roster and match by email address against Pipedrive Users. If a HaystackCRM user has no matching Pipedrive account, we hold their record assignments in a reconciliation queue and document the gap. The customer's admin provisions the missing Pipedrive Users before we resume the migration. Migration cannot complete with unresolved owner references because Pipedrive requires a valid User ID on all owned records.

HaystackCRM Teams allow role-based grouping and region-based contact segmentation. Pipedrive has a Teams feature (Advanced tier and above) that enables grouping users for shared pipeline visibility and territory management. We export team membership and roles from HaystackCRM, then configure Pipedrive Teams during the schema setup phase. Role granularity in HaystackCRM (if it exceeds Pipedrive's default team permissions) is documented as a configuration review item.

HaystackCRM Quotes generated from hot Opportunities are exported as PDF references and line item data. Pipedrive does not have a native quote object at the Essential or Advanced tiers; quoting is available as a Documents feature or via integrations (PandaDoc, Ironclad). We export quote line items as structured data and the PDF links as attachment references, then deliver a written inventory of each Quote with its linked Opportunity and recommended Pipedrive Documents or integration setup. The admin rebuilds the quoting workflow post-migration.

HaystackCRM Dashboard metrics are computed dynamically from live data and do not exist as persistent records. We do not migrate dashboard snapshots. The customer's admin rebuilds reports and dashboards in Pipedrive once data is loaded; we deliver a record count summary by object type to serve as the baseline for dashboard setup.