Phase 0

Decide & Plan

Lock scope, success criteria, and the cutover window before any export starts.

Document the full list of Pipedrive item types in scope. Pipedrive supports eight importable item types: People, Organizations, Leads, Deals, Projects, Activities, Notes, and Products. Confirm which are in scope and which are deliberately out of scope.
Risk if skipped: Discovering at cutover that Projects or Products were assumed but never planned forces re-scoping mid-migration.
Define historical-data scope by item type. Decide how many years of closed deals, completed activities, and archived notes you will move. Decide whether email threads and call logs are in scope.
Risk if skipped: Pulling all history by default can multiply the dataset 5–10x and blow through the cutover window.
Confirm the target Pipedrive plan and its custom-field ceilings. Lite, Growth, Premium, and Ultimate cap custom fields per item type at different levels (roughly 30 on Lite through 300 on Ultimate). Required fields are Professional/Premium+ only.
Risk if skipped: Buying Lite then discovering you need 80 custom fields per object blocks the migration until billing is escalated.
Decide whether Smart Docs, Lead Scoring, and Campaigns are in scope. Smart Docs and Lead Scoring are tier-gated. Confirm whether they need to be configured during this migration or deferred.
Identify GDPR data-residency and retention requirements. Pipedrive hosts in AWS data centers in Europe and the US. Confirm which region your tenant uses and that it satisfies any contractual residency commitments.
Risk if skipped: Discovering after cutover that your tenant is in the wrong region forces a second migration or a contractual exception.
Confirm SOC 2, ISO 27001, and EU-US Data Privacy Framework evidence needs. If your auditors require evidence packs at cutover, request the latest Pipedrive certification reports before the freeze date.
Assign a single accountable migration owner (DRI). One named person owns scope decisions, cutover go/no-go, and post-migration signoff. Document their backup.
Document explicit out-of-scope items. List the source-system features that will NOT be rebuilt in Pipedrive — chat transcripts, marketing automation flows, custom reporting macros, etc. Get sponsor sign-off in writing.
Risk if skipped: Unwritten out-of-scope items resurface as urgent during cutover and derail the schedule.
Set the target cutover date and source-system freeze window. Pick a low-activity window (often a Friday evening through Sunday). Communicate the freeze date and time to all source-system users at least two weeks in advance.
Define written success criteria for the migration. Examples: 100% of open deals migrated with correct stage; aggregate pipeline value within 0.5% of source; all owners assigned correctly; activities linked to correct deals.
Risk if skipped: Without falsifiable criteria, the migration is never formally complete and tail issues drag on for months.

Phase 1

Pre-Migration Prep

Cleanse the source, build the destination schema, and align the team.

1a. Source-system audit and cleansing

Run dedup analysis on source People using email as the primary match key. Resolve duplicate contacts at the source before export. Pipedrive's Spreadsheet Importer offers a merge option during import, but cleaner source data produces cleaner results.
Risk if skipped: Importing duplicates means rebuilding deal-to-person associations against the wrong record after dedup.
Run dedup analysis on source Organizations using domain as the match key. Normalize company-name variations (Acme Inc., Acme Incorporated, ACME) to a single canonical form.
Standardize email casing to lowercase across all People records. Mixed-case email values create silent duplicates against the lowercase keys Pipedrive uses for matching.
Normalize phone-number formats to E.164 with country code. Pipedrive stores phone as text; agree on one format (+15551234567) and apply it before export.
Identify and resolve source records missing values that will be mandatory in Pipedrive. Person name, Organization name, Lead title, Deal title, and Activity type+due date are mandatory. Records missing these will land in the skip file.
Risk if skipped: Mandatory-field misses produce a skip file at import; without a triage plan you lose visibility into what failed.
Export baseline record counts per object as of the export timestamp. Capture counts for People, Organizations, Leads, Deals, Activities, Notes, Products, and Projects. These become the reconciliation target.
Risk if skipped: Without a baseline you cannot tell at validation whether 'missing' records were never exported or lost in transit.
Snapshot source pipeline-stage definitions and current deal distribution. Document the stage name, order, and probability for every pipeline. Capture how many deals sit in each stage today.
Decide which closed-lost or archived deals are worth migrating. Closed-lost deals from beyond your retention horizon may not justify the effort to move. Document the cutoff.

1b. Destination Pipedrive setup

Provision the Pipedrive production tenant on the chosen plan. Confirm seat count, currency, fiscal year, and default timezone at company creation.
Sign up for a Pipedrive Sandbox account for dry-run testing. The Sandbox is a separate tenant for building and testing without impacting the production data set.
Risk if skipped: Skipping sandbox forces all test errors to occur in production where rollback is harder.
Create all human users in Pipedrive before any record import. Record owners on imported deals, activities, and notes match by user email. Missing users default to the import-running user, scrambling ownership.
Risk if skipped: If users do not exist before import, every record is owned by one person and you must reassign tens of thousands of records manually.
Configure global account currency and add any secondary currencies. Monetary custom fields pair with a {key}_currency field holding the ISO code (USD, EUR). Set up every currency you will load.
Risk if skipped: Loading EUR deals without the EUR currency added produces 'Please provide valid currency' skip-file errors.
Set the company timezone to match the source system's timezone. Activity due dates and deal close dates render against the company timezone; a mismatch silently shifts dates by hours.
Create every pipeline and stage that source deals will land in. Match the stage names exactly to what your transform spreadsheet will emit. Stage probability is configurable per stage.
Create all custom fields on Person, Organization, Lead, Deal, Project, and Product before any import. Pipedrive offers 16 custom field types including Text, Large text, Single option, Multiple options, Numerical, Monetary, Date, Date range, Time, Time range, User, Address, Phone, Autocomplete, Formula, and File.
Risk if skipped: Importing into a custom field that does not exist drops the data silently. There is no retry after the import completes.
Define every Single option and Multiple option custom field's full option list before import. Each Single/Multiple option field caps at 10,000 options (raised from 500 in May 2021). Options have internal IDs that the importer matches against; missing options become skip-file rows.
Risk if skipped: If an option does not exist when a row arrives carrying it, the row is rejected with an option-not-found error.
Mark Professional/Premium+ Required fields only after the migration completes. Required fields are Professional+ and they block record creation when empty. Leaving them off during import prevents legitimate historical records from being rejected.
Risk if skipped: Turning Required on before import causes thousands of rows to fail validation because legacy data never carried that value.
Disable Workflow Automation triggers that fire on record create or update. Auto-emails, deal-stage notifications, and Sales Assistant nudges fire on every imported row otherwise. Pause all automations before import.
Risk if skipped: An import of 50,000 deals can fire 50,000 stage-change emails to customers if automations are not paused.
Disconnect outbound integrations (Zapier, Make, email sync, calendar sync) during import. Reconnect after Phase 5 completes. Calendar sync is supported only for Google, Office 365, and Exchange.

1c. People and process prep

Announce the source-system freeze date to all end users. Send the announcement at least two weeks ahead with the exact freeze timestamp and the destination go-live time.
Schedule a Pipedrive basics training session for each end-user role. Cover pipeline navigation, deal creation, activity logging, and email linking. Run the session in the week before cutover, not after.
Designate first-responders for the first 48 hours after cutover. Name two admins and one Pipedrive-fluent power user who will triage user issues immediately. Publish their Slack handles or extensions.
Document the rollback decision criteria and owner. Pipedrive's Spreadsheet Importer offers a Revert action within 48 hours. Decide who can pull that trigger and under what data-loss threshold.
Risk if skipped: Without a documented rollback owner, the 48-hour Revert window expires during indecision and rollback becomes manual record-deletion.

Phase 2

Source Export

Pull complete data from the source system in formats the transform stage can consume.

Export source contacts/persons to CSV with all standard and custom fields. Include record ID, full name, email, phone, organization link, owner email, created date, and every custom field. Encode as UTF-8.
Risk if skipped: Non-UTF-8 encoding causes Pipedrive's strict parser to reject payloads with 'Invalid or malformed' errors.
Export source organizations/accounts to CSV with all fields and the parent-organization link if used. Capture the parent_org_id relationship so multi-level company hierarchies can be rebuilt.
Export source leads (top-of-funnel records) as a separate CSV. In Pipedrive, Leads live in the Lead Inbox and are distinct from Deals. Keep them separate during export so the load order can respect that.
Export source deals/opportunities to CSV with stage, value, currency, close date, owner, and linked person and organization IDs. Capture both the source record ID (for traceability) and the linked person/org source IDs so relationships can be rebuilt.
Risk if skipped: Without source IDs, you cannot reconnect deals to their people and organizations after the lookup IDs change in Pipedrive.
Export source activities (tasks, meetings, calls, emails) to CSV with type, subject, due date, due time, duration, owner, and linked deal/person/organization IDs. Pipedrive activity types include call, meeting, task, deadline, email, and lunch. Map your source types to these.
Export source notes with body, created date, author, and linked record IDs. Pipedrive notes cap at roughly 100 kB each and a deal holds up to 100 notes. Long source notes may need to be split.
Risk if skipped: Notes that exceed 100 kB are silently truncated or rejected, losing tail content that may contain important context.
Export source products/catalog items with code, name, unit price, currency, and tax. Pipedrive Products attach to Deals as line items with quantity and discount; capture the structure that powers that.
Export source projects (if in scope) with phase, owner, and linked deal. Projects are an item type in Pipedrive and follow their own template/phase structure.
Export the user list with full name, email, role, and reporting hierarchy. Used to provision Pipedrive users in Phase 1b and to map source owner_id to destination owner email.
Export source pipeline definitions: pipeline name, stages, stage order, stage probability. These power the pipeline-rebuild task in Phase 3d.
Export every source attachment along with its parent record ID and original filename. Pipedrive's per-file cap is roughly 50 MB. Files larger than 50 MB must be hosted externally and linked.
Risk if skipped: Files over 50 MB silently fail to upload; without a parallel hosting plan, content is lost.
Export source automations, sequences, and workflow definitions as documentation, not data. Workflows do not migrate as data; capture screenshots, trigger conditions, and actions for manual rebuild in Pipedrive's Workflow Automation.
Export reports and dashboards as documentation only. Pipedrive Insights reports must be rebuilt manually after cutover.
Stamp every export file with its exact UTC export timestamp. The timestamp defines the delta that the cutover final-pull (Phase 5) must capture.
Risk if skipped: Without an export timestamp you cannot tell what activity occurred between Phase 2 and cutover.

Phase 3

Transform & Map

Convert exports into Pipedrive-shaped files with explicit field, type, and relationship handling.

3a. Mapping spreadsheet

Build a master mapping spreadsheet covering every source field for every item type. Columns: source object, source field, source type, destination object, destination field, destination type, transformation rule, nullability, mandatory-at-import flag.
Risk if skipped: Without a single source-of-truth mapping document, field decisions get made twice and the second decision overwrites the first silently.
Mark the Pipedrive mandatory fields per object: Person name; Organization name; Lead title + linked person/org; Deal title + linked person/org; Activity type+due date. Confirm every source row will satisfy these. Build a pre-import validator if you have more than 10,000 rows.
Risk if skipped: Mandatory-field violations are the #1 cause of skip-file rows during Pipedrive imports.
Resolve every picklist value mismatch between source and destination. Source 'Won-Closed' must become destination 'Won'. Build the mapping table inline in the master spreadsheet so transforms reference one location.
Designate Pipedrive System ID as the only valid upsert key for updates. Pipedrive has no general 'External ID' concept. The Pipedrive System ID is assigned on first import and is the only upsert key the Spreadsheet Importer accepts for updates.
Risk if skipped: Re-running an import without the Pipedrive System ID column duplicates every record instead of updating it.
Decide handling for source fields with no Pipedrive equivalent. Options per field: drop, concatenate into Notes, or create a Pipedrive custom field. Document the choice for every orphan field.
Decide handling for source records whose owner email does not exist in Pipedrive. Either provision the missing user before import, reassign to a 'Migration' user, or drop the record. Document the rule.

3b. Data transformation

Convert all date and datetime values to ISO-8601 with explicit timezone. Format YYYY-MM-DD for Date fields and YYYY-MM-DDTHH:MM:SSZ for Date range and Time fields.
Risk if skipped: Ambiguous DD/MM vs MM/DD strings get parsed by the importer's locale and silently shift dates by months.
Populate the {key}_currency companion column for every Monetary custom field. Each Monetary field stores the numeric value in the field key and the ISO currency code (USD, EUR, GBP) in a parallel {key}_currency column. Symbols like $ or € are rejected.
Risk if skipped: Omitting the currency column produces 'Please provide valid currency' skip-file errors on every row.
Normalize numeric values: strip thousand separators, force a decimal point, cap precision at 16 decimal places. Pipedrive Numerical fields support precision up to 16; values beyond that lose precision silently.
Truncate Text custom field values to 255 characters. Pipedrive Text (varchar) fields cap at 255. Use Large text for anything longer.
Risk if skipped: Text values over 255 characters are silently truncated, losing the tail with no skip-file warning.
Re-encode every text field as UTF-8. Pipedrive's parser strictly enforces UTF-8 and rejects payloads with a 'control character error, possibly incorrectly encoded' message otherwise.
Risk if skipped: Non-UTF-8 encoding causes entire batches to fail, not single rows.
Escape commas, quotes, and newlines inside CSV cells per RFC 4180. Wrap any cell containing a comma, quote, or newline in double quotes and double-up internal quotes.
Risk if skipped: Unescaped commas split rows into wrong column counts and the Spreadsheet Importer rejects the row.
Map Single option and Multiple option values to the destination's option labels exactly. Internal option IDs differ between source and destination. The importer matches on label; case and whitespace must match the destination option exactly.
Risk if skipped: A trailing space or wrong capitalization on an option label rejects the row with an option-not-found error.
Split source records with more than 10,000 Multiple option selections into multiple records or fields. Pipedrive's per-field option ceiling is 10,000. Values beyond that cannot be added.

3c. Relationship and audit-trail decisions

Decide strategy for preserving the original record creation timestamp. Pipedrive sets add_time on import to the import moment. To preserve the source created date, store it in a custom Date field named 'Source Created Date'.
Risk if skipped: Reporting that filters on add_time will treat every migrated record as created at cutover, distorting historical trend analysis.
Decide strategy for record ownership: best-match by source owner email, or assign all to a single 'Data Migration' user. If using best-match, ensure every source owner email exists as a Pipedrive user before import (see Phase 1b).
Decide strategy for file attachments: re-upload binaries or preserve as external storage links. Re-uploading preserves in-app access. External links keep files dependent on the source storage layer but avoid re-upload time.
Pre-sort the load order: Users, Products, Organizations, People, Leads, Deals, Projects, Activities, Notes, Files. Children cannot reference parents that do not exist yet; this order respects every Pipedrive dependency.
Risk if skipped: Loading Deals before Organizations strands deals without their org link and forces a re-link pass after.

3d. Pipedrive-specific transforms

Rebuild every pipeline and stage exactly in Pipedrive before importing deals. Pipelines and stages are created in Settings > Pipelines. Stage probability (0–100) drives forecast math and must match the source intent.
Risk if skipped: Importing deals into a missing stage assigns them to the default stage and corrupts pipeline reporting.
Map every source deal-stage value to a destination stage_id. Deals reference stage_id, not stage_name. Build a name-to-ID lookup table after stages are created.
Decide deal close-date handling for won and lost deals. Pipedrive stores close_time for won/lost deals. To preserve source close dates, write close_time during import (rather than letting Pipedrive stamp the import moment).
Rebuild every Workflow Automation manually in Pipedrive after data load. Source automations do not migrate. Capture trigger, conditions, and actions during Phase 2 and rebuild in Settings > Automations. Leave them inactive until validation completes.
Risk if skipped: Activating automations before validation triggers email blasts and Sales Assistant nudges to customers on incorrect data.
Recreate Smart Docs templates with destination field merge tokens. Smart Docs is available on Premium/Ultimate and on lower tiers as a paid add-on. Merge fields use Pipedrive's variable syntax which differs from most source CRMs.
Recreate email templates referencing Pipedrive Person and Deal merge fields. Source merge-field syntax does not translate. Rebuild every template and verify rendered output on a test record.
Recreate Activity templates and saved Activity types. Custom activity types beyond the defaults must be added in Settings > Activity types before activities referencing them are imported.
Risk if skipped: Activities referencing an undefined custom type are rejected at import.
Plan the Lead Scoring rebuild if Lead Scoring is in scope. Lead Scoring is tier-gated. Source scores rarely translate one-to-one; document the new rule set and apply it after leads are loaded.
Plan calendar sync setup as a per-user post-cutover task. Pipedrive Calendar sync supports Google, Office 365, and Exchange only — not IMAP or POP. Two-factor Exchange users need an app password.
Map source contact-merge logic to Pipedrive's Spreadsheet Importer merge option. When a row matches by email, the importer can merge into the existing person or create a duplicate. Document which is correct per row class.

Phase 4

Sandbox Test Migration

Prove every transform and load path against the Pipedrive Sandbox before touching production.

Load a 1–5% representative sample of each item type into the Sandbox. Use the Spreadsheet Importer at Settings > Tools and apps > Import data for each object type.
Risk if skipped: Skipping a sample run means production becomes the first place errors surface.
Trigger every option-field value at least once in the sample. If a Multiple option field has 50 options, the sample should exercise all 50 so option-mapping errors surface here, not in production.
Verify 5–10 random Sandbox records field-by-field against the source. Walk every custom field, every option value, and every linked record. Document and triage every mismatch.
Test edge cases: 255-character text, multi-line notes, emoji, RTL languages, leading/trailing whitespace, NULL values. Each of these has historically broken at least one CRM importer; verify Pipedrive's behavior on yours.
Test Monetary field import with at least three currencies including a non-USD one. Confirms the {key}_currency column is wired correctly and that the company currency list covers your dataset.
Test parent-child relationships: organization with people, organization with parent_org_id, deal with linked person and org. Open the imported deal in the Pipedrive UI and confirm person_id and org_id are populated correctly.
Risk if skipped: Broken links are invisible from the deal list view but show as 'Person not found' in reports.
Test activity-to-deal and activity-to-person linkage on the sample. Activities without correct deal_id or person_id render orphan in the Activities calendar.
Test file attachment upload with a 1 MB, a 25 MB, and a 50 MB file. Confirms both the success path and the 50 MB ceiling behavior.
Time the sample run end-to-end and extrapolate to full volume. Use the sandbox load timing to extrapolate to your full record count.
Risk if skipped: Extrapolation from a 100-row sample without accounting for parallelism produces a cutover estimate off by 10x.
Confirm the Spreadsheet Importer Revert action works on a small Sandbox import. Verifies the 48-hour rollback path that Phase 1c relies on.
Have a sales-ops or RevOps power user spot-check 20 Sandbox records. They will catch business-logic issues (wrong stage, wrong owner, missing tag) that field-level checks miss.
Get written sandbox sign-off before proceeding to Phase 5. Sign-off names the test artifacts (record counts, sampled records, edge-case results) and is the gate to production.
Risk if skipped: Skipping sign-off lets unresolved Sandbox issues carry into production where the cost of fixing them rises.

Phase 5

Production Cutover

Execute the production load in a tight, sequenced window with idempotent operations.

Confirm the source-system freeze is in effect; verify no writes in the last hour. Audit the source change log if available, or sample 10 recent records and confirm modified_at timestamps are all before freeze.
Risk if skipped: Late writes after the freeze produce records that exist in source but not in destination, requiring a manual delta pass.
Take a final full export to capture the delta since the Phase 2 baseline. Diff the new export against the Phase 2 export and load only changed/new rows to minimize load time.
Confirm all destination automations are paused. Re-verify Phase 1b: Workflow Automation, Sales Assistant nudges, and outbound integrations (Zapier, Make) are all off.
Risk if skipped: A single live automation can send thousands of customer emails during the load.
Load Products first, capturing returned IDs into a lookup file. Deals will reference these product IDs when adding products as line items.
Load Organizations, capturing returned IDs. Build org_source_id -> org_pipedrive_id lookup file for downstream loads.
Load People with org_id populated from the lookup. Process records in parallel batches to stay within Pipedrive's per-tenant throughput budget.
Load Leads with person_id and organization_id populated. Leads land in the Lead Inbox and are distinct from Deals.
Load Deals with person_id, org_id, stage_id, value, currency, owner_id, and close_time set. Use stage_id from the pipeline rebuild lookup, not stage_name.
Risk if skipped: Loading stage_name instead of stage_id silently puts the deal in the default stage.
Load Projects (if in scope) with linked deal_id and owner_id. Projects depend on Deals and Users existing first.
Load Activities with deal_id, person_id, org_id, type, due_date, due_time, and done flag. Closed activities should carry done=1 with marked_as_done_time set to the source completion timestamp.
Load Notes with deal_id, person_id, or org_id and add_time set to the source created timestamp. Use the add_time override (where supported) so notes appear in the correct chronological position on the deal timeline.
Upload File attachments last, with the parent record ID required on each upload. Files over 50 MB must be skipped here and linked externally per the Phase 3c decision.
Capture every import job's row count, success count, error count, and error log. Build a job-status file the Phase 6 reconciliation reads from.
Risk if skipped: Without per-job error logs you cannot tell which records failed and need a re-run.
Cross-check destination counts against source counts after each item-type load completes. If the delta exceeds your tolerance (often 0.1%), stop and diagnose before loading the next type.
Risk if skipped: Pushing through with a known delta means later types reference records that should not exist.
If any load step fails partway, stop, diagnose, fix the transform, and re-run with Pipedrive System ID as the upsert key. Idempotent re-runs depend on the System ID being captured from the partial success.
Re-enable Workflow Automation and outbound integrations only after Phase 6 sign-off. Reactivation order: integrations first (so they fire on subsequent changes), then workflow automations, then Sales Assistant.

Phase 6

Validate

Prove the migration is correct before letting users into Pipedrive.

6a. Reconciliation

Compare total record count per item type: source vs Pipedrive. Use the Pipedrive list views or exports for persons, deals, organizations, activities, notes, products, projects, leads and compare to baseline.
Risk if skipped: An unexplained delta indicates either skip-file rows you missed or a parent-link failure that orphaned children.
Compare aggregate open pipeline value: source vs Pipedrive, by currency. Group deals by status=open and pipeline_id, sum value, group by currency. Investigate any delta over 0.5%.
Compare won-deal count and aggregate value for the last 12 months. Won-deal counts power most sales reporting; a delta here surfaces stage-mapping errors.
Spot-check 25–50 randomly selected deals field-by-field against source. Walk every standard field and every custom field on each sampled deal.
Spot-check 25 randomly selected people including all custom fields. Validates the People schema separately from the Deal schema.
Compare deal counts per pipeline-stage between source and Pipedrive. A stage-by-stage diff surfaces stage-mapping errors that aggregate totals hide.
Risk if skipped: Two stages that net to the same total but moved deals to the wrong bucket distort forecasts.

6b. Relationship validation

Verify a random sample of 30 person-to-organization associations match source. Confirms org_id populated correctly on People rows.
Verify a random sample of 30 deal-to-person and deal-to-organization links. Confirms person_id and org_id populated correctly on Deal rows.
Verify a random sample of 30 activity-to-deal links. Confirms deal_id populated correctly on Activity rows; orphan activities render in the calendar but not on the deal.
Confirm parent-organization (org-of-org) hierarchies rebuild correctly. Walk a known multi-level hierarchy from source and verify it in the Pipedrive org detail view.
Confirm file attachments are accessible and bound to the correct record. Open 20 random attached files from inside their parent deal/person/org to verify both linkage and binary integrity.
Risk if skipped: Files that uploaded successfully but linked to the wrong record are invisible without per-record inspection.

6c. Audit and compliance

Verify the Source Created Date custom field is populated on every migrated record. Confirms the audit-trail strategy from Phase 3c worked end-to-end.
Run a GDPR access-request rehearsal on a test contact. Confirms the new tenant's data-subject-access flow works against migrated data.
Confirm Pipedrive's region (EU or US AWS) matches the contractual residency commitment. Validates the Phase 0 residency check against the actual provisioned tenant.
Risk if skipped: Discovering a region mismatch after go-live triggers either a tenant rebuild or a customer notification.
Verify Pipedrive Security Dashboard captures login history per user. Confirms audit logging works for the new tenant from day one.

6d. User-acceptance check

Have 3–5 power users complete their daily workflow end-to-end in Pipedrive against migrated data. Examples: log in, find a deal, add a note, log a call, move stage, send email via linked inbox.
Document every issue raised in UAT with severity (blocker / important / cosmetic). Blockers must be resolved before Phase 7; cosmetic items go to the 30-day backlog.
Confirm Insights reports reflect expected totals on at least three pre-agreed reports. Open pipeline by owner, deals won this quarter, activities completed this week.

6e. Sign-off

Get written sign-off from the migration sponsor before opening Pipedrive to end users. Sign-off references the reconciliation report, UAT log, and the compliance checks above.
Risk if skipped: Opening to users before sign-off means data errors get found by sales reps mid-call, eroding trust in the new system.

Phase 7

Post-Migration Cleanup

Decommission the source, rebuild what does not migrate, and close the project.

Announce Pipedrive go-live to all end users with login URL, support contact, and the source read-only date. Include a one-pager pointing to the most common 'where did this go' translations.
Run the planned end-user training sessions by role (sales rep, sales manager, ops). Use migrated data live in the sessions so users see their own records, not toy examples.
Set the source system to read-only on the announced date. Read-only mode preserves it as a reference but prevents drift between source and Pipedrive.
Risk if skipped: Leaving the source writable creates two sources of truth and reps will use whichever is faster, scrambling the data again.
Rebuild every Insights report and dashboard in Pipedrive. Reports do not migrate. Rebuild against destination field keys and confirm totals against the Phase 6 validation report.
Reactivate Workflow Automation rules one category at a time, monitoring for unintended fires. Start with low-risk notifications. Watch Sales Assistant suggestions for a day before activating customer-facing automations.
Risk if skipped: Activating all automations at once on freshly loaded data can fire bulk customer emails referencing stale context.
Recreate every email template, Smart Docs template, and sequence template manually. Verify each renders against a live migrated record before publishing to end users.
Reconnect calendar sync per user (Google, Office 365, or Exchange). Pipedrive does not bulk-enable calendar sync; each user runs Personal preferences > Calendar sync individually.
Reconnect outbound integrations: Zapier, Make, BI tools, email-sync providers. Restore in the order they were paused; verify each integration sees migrated records correctly.
Archive Phase 2 source-system exports to long-term cold storage with documented retention. Retain for the duration of your compliance window in case forensic comparison is needed.
Schedule a 30-day post-migration retrospective. Invite the DRI, sponsors, first-responders, and 2–3 end users. Capture what worked, what hurt, and what to do differently next time.
Decide and document the source-system decommission date. Typically 90 days after cutover, after the final compliance retention window. Confirm contract terms before fully shutting it down.
Close the migration project formally. Final status report, lessons-learned doc, and project closure ticket. The migration is not done until this exists.

Watch list

Risks to track throughout

These risks live across multiple phases — keep an eye on them from kickoff through cutover.

Silent option and currency rejections

Option-field values must match destination labels exactly (case, whitespace) or rows land in the skip file. Monetary fields require ISO codes in the paired {key}_currency column, not symbols. Both failures are silent at the row level and only visible by downloading and triaging the skip file after each import.
Mandatory-field and Required-field gating

Pipedrive enforces mandatory fields at the platform level (Person name, Organization name, Deal title plus linked person/org, etc.) on every import. Plan-level Required fields (Professional and above) compound this. Keep Required fields off until after the load, and pre-validate mandatory fields on every export before transform.
Pipedrive System ID upsert discipline

Pipedrive has no general 'External ID' concept — the Pipedrive System ID assigned on first import is the only upsert key the Spreadsheet Importer recognizes. Without capturing and re-using the System ID on every re-run, partial-failure recovery duplicates records. Track System ID capture from the first sandbox load through every production re-run.
Cutover automation blast radius

Workflow Automation, Sales Assistant nudges, and outbound integrations (Zapier, Make, email and calendar sync) fire on every imported record unless explicitly paused. A 50,000-deal import can trigger 50,000 customer emails if a single automation is missed. Audit the full automation list in Phase 1b, re-verify the pause set in Phase 5, and reactivate only after Phase 6 sign-off.