Migrate from SprintHub to Pipedrive

SprintHub Lead records map to Pipedrive Lead. We extract standard Lead fields including name, contact info, status, and owner assignment. SprintHub's Lead API uses GraphQL-style query parameters; we resolve hubspot_owner_id references against Pipedrive User records by email match. Any Lead without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import begins.

SprintHub Contact records map to Pipedrive Person. Contact details, custom properties, and company associations transfer directly. If the source Contact has a linked SprintHub Company, we resolve that to the corresponding Pipedrive Organization before inserting the Person record so that the org_id lookup is satisfied at import time. Tags attached to the Contact are preserved as pipedrive_user_field_id entries on the Person record.

SprintHub Company records map to Pipedrive Organization. Company names, industry, size, and custom fields migrate without transformation. The company domain becomes the Organization's website field and is used as the deduplication key during import. Organization is inserted before Person records so that Person-Organization lookups resolve at migration time rather than requiring a second-pass update.

SprintHub Deals map to Pipedrive Deals. The dealstage property maps to a Pipedrive Stage that we pre-create to match the source pipeline structure. Pipeline assignment maps to a Pipedrive Pipeline that we configure before migration. Closed-Lost and Closed-Won reasons from SprintHub custom properties become Pipedrive Lost_reason custom fields. Deal owner resolves by email match against Pipedrive User records.

SprintHub Pipeline definitions, including stage names and ordering, are extracted as explicit key-value pairs per pipeline rather than assumed from standard names. Each SprintHub pipeline becomes a Pipedrive Pipeline. Stage probability percentages from SprintHub transfer to Pipedrive stage probability values, rounded to the nearest Pipedrive-allowed integer. Pipedrive allows multiple pipelines per account, matching SprintHub's multi-pipeline capability.

Stage names, order, and win/loss probability vary per SprintHub pipeline and are preserved explicitly in the migration mapping workbook. We configure each Pipedrive Stage to match the source stage name, position, and probability so that the sales team sees the same deal progression. Stages are created in the correct order before Deals are imported so that Pipedrive's stage_id foreign key is satisfied at insert time.

SprintHub tags are global across the instance and can be attached to Leads, Contacts, Companies, and Deals. We retrieve the full tag list including color metadata and preserve tag associations on each record during migration. Tags are mapped to Pipedrive custom user fields (type: varchar) on the respective object. The customer chooses during scoping whether tags become multi-select user fields or stored as comma-separated text for simplicity.

SprintHub custom field names, types, and picklist options vary per instance. We extract the full custom field schema alongside record values. Each custom field is pre-created in Pipedrive with the appropriate type conversion: text fields to varchar, numbers to numeric, dates to date, picklists to enum. Custom field definitions are validated during the discovery phase by inspecting the SprintHub API response schema. Picklist options migrate as Pipedrive enum options with the same label and value.

SprintHub's support for multiple WhatsApp accounts per instance is a key feature for Brazilian teams. Pipedrive does not have native multi-account WhatsApp routing. We export the account-to-conversation mappings and routing rules as a structured JSON document for the customer to reconfigure in a third-party WhatsApp integration (e.g., Twilio, W活, or a Brazilian-focused WhatsApp Business API provider) post-migration. This is not a data migration; it is a configuration rebuild that requires the customer's admin to set up the new channel connection in Pipedrive.

SprintHub automation rules including trigger conditions, filter logic, and multi-step action sequences are stored in a proprietary format. We export the rule definitions as structured JSON including trigger type, conditions, actions, and delays. Pipedrive's Automation feature covers deal-triggered and activity-triggered automations but does not replicate SprintHub's marketing automation model (email drip sequences, lead scoring, behavioral triggers). We deliver a written automation inventory with Pipedrive Automation equivalents recommended for each rule. The customer's admin rebuilds automations post-migration.

SprintHub social media campaign data including post histories, metrics, and attribution settings are stored in SprintHub's social module. We export available campaign records and performance data (impressions, clicks, engagement) as a structured CSV for the customer's records. Attribution settings and UTM mapping require manual reconfiguration in the destination social or marketing analytics tool. Pipedrive has no native social media management; the customer assigns these campaigns to their chosen social analytics platform post-migration.