Migrate from Spark CRM to Pipedrive

Spark People migrate directly to Pipedrive Persons. The primary Organization link in Spark maps to Pipedrive's organization_id field on Person. Multiple organization associations in Spark collapse to the primary link with secondary organizations surfaced as relationship entries. If a Spark Person has no company association, the resulting Pipedrive Person record has no organization_id and can be linked manually or through a follow-up data-quality pass.

Spark Companies map to Pipedrive Organizations. Parent-child company hierarchies in Spark use Pipedrive's parent Organization ID field to preserve structure. Multi-person associations collapse to the primary contact in Pipedrive's Person-Organization relationship model. Company address components (street, city, state, postal code, country) map to Pipedrive's structured address fields for geocoding support if enabled in your account.

Spark Deals migrate to Pipedrive Deals 1:1. The Spark pipeline maps to a Pipedrive pipeline with stages mapped value-by-value. Each deal retains its linked Person (primary contact) and Organization (company) via Pipedrive's deal_person_id and deal_organization_id fields. Deal currency and expected close date transfer as-is, with stage probabilities re-applied from Pipedrive's stage configuration.

Each Spark pipeline becomes a Pipedrive pipeline. Stage names map value-by-value to Pipedrive stage names. Stage order and probability percentages are preserved as Pipedrive stage configuration. If Spark has one pipeline, it maps to one Pipedrive pipeline; multiple Spark pipelines create multiple Pipedrive pipelines. Stage probability percentages are configurable post-migration if your deal-closing assumptions differ from historical data.

Spark email history migrates as Pipedrive Email Message records linked to the Person. Subject, body, direction (sent/received), and timestamp are preserved. Pipedrive's email sync must be configured separately if you want future emails to sync automatically. Attachments within emails re-upload as Pipedrive Files subject to the 25MB per-file limit.

Spark call logs migrate as Pipedrive Activities with type='Call'. Duration, outcome, and linked Person are preserved. Notes attached to calls map to Pipedrive Activity notes. Call recordings do not transfer — Pipedrive stores recordings separately via its own call tracking integration. If Spark recordings are accessible via URL, they can be re-hosted and linked manually post-migration.

Spark meetings migrate as Pipedrive Events with original start/end times, location, and linked Person preserved. Attendees from Spark map to Pipedrive's activity participants if your Pipedrive plan supports it. Calendar sync configuration is a separate post-migration setup step. Recurring meeting series split into individual Event records with the recurrence pattern documented in the activity notes.

Spark notes migrate as Pipedrive Notes linked to the parent Person, Organization, or Deal. Rich-text formatting is preserved where the target field supports it. Notes without a parent link attach to the associated Person by default. If no Person association exists, the Note attaches to the related Organization or Deal as applicable.

Spark custom fields map to Pipedrive custom fields. Custom fields must be pre-created in Pipedrive with matching types (text, number, date, drop-down, etc.) before migration runs. We deliver a custom field specification sheet during planning so your Pipedrive admin can create these before the data load. Drop-down custom fields require value lists to match exactly or the import will skip mismatched selections.

Spark owners resolve to Pipedrive users by email match. If a Spark owner has no corresponding Pipedrive user, their records assign to the migration initiating user by default. Your team should create Pipedrive users for all active Spark owners before migration begins. Inactive Spark owners are flagged for review but do not block migration — their records can be reassigned post-migration.

If Spark uses a lead concept separate from Person, those records migrate to Pipedrive Leads. Pipedrive Leads share custom fields with Deals in some plans — we map lead-specific fields to the Lead object and deal fields to the Deal object without conflict. Lead status values map to Pipedrive's lead lifecycle stages (New, Contacted, Qualified, Unqualified) where applicable.

Spark file attachments on People, Companies, and Deals re-upload to Pipedrive Files and link to the parent record. Pipedrive has a 25MB per-file limit. Files stored in Spark's cloud attach via URL where accessible; we re-upload as new Pipedrive Files. Files exceeding 25MB are flagged in the migration report with guidance to host externally and link manually.