CRM workspace migration wizard

    Migration Guide

    Use the Data Hub migration wizard, two-phase import for large orgs, and background batch jobs to move pipelines, contacts, deals, and activities from your previous CRM.

    By Sebastian StreiffertPublished Jan 10, 2026Updated May 29, 20267 min read

    Start Pipedrive migration

    What Portage does for Pipedrive

    Lumenbase Portage copies your connected Pipedrive organization into Lumenbase: pipelines and stages, companies, people, deals, and activities. It is a guided flow in Data Hub (not a simple CSV upload) so field relationships and dependencies stay consistent.

    Use this when you are moving your workspace from Pipedrive rather than maintaining a permanent two-way sync. See System Operations → Data Hub → Lumenbase Portage to start or resume a session, or read the Lumenbase Portage hub for all supported origins.

    Before you start

    1. In the Portage wizard, click "Connect with Pipedrive" to authorize read-only access, or paste an API token instead. No separate Integrations step needed.
    2. Make sure you are a workspace owner or admin. Only they can run a migration.
    3. Plan a quiet window for very large orgs: imports can run in the background, but the first phase still needs your attention to confirm preview counts.
    If you only need a flat spreadsheet of contacts, use Import from CSV instead of the full migration wizard.

    Wizard steps

    1

    Scan

    Lumenbase reads your source organization and counts how many records exist per entity type (pipelines, stages, companies, contacts, deals, activities). This is read-only on the source side.
    2

    Configure

    Choose which entity types to import. The wizard respects dependency order (for example, companies before contacts).
    3

    Preview

    You see record counts and, when applicable, a breakdown of how the import will be paced (see below).
    4

    Import

    A batch job runs server-side. You can keep working: use Continue in backgroundand watch progress from the floating batch job indicator in the app.
    5

    Summary

    When the job finishes, you get a summary of what was imported. If something failed, you can review options including rollback when offered.

    Two-phase import (priority sprint + slow drip)

    Large workspaces are split so critical structure lands first. Entity types with fewer records import in a sprint phase first. Any entity type whose scan count is above a high threshold (currently 10,000 records per type) is scheduled for a second slow drip phase after the sprint completes.

    In the preview you will see which types are sprint vs slow drip when both apply. On the import screen, sprint rows finish before slow-drip rows begin.

    Sprint phase

    Priority import for entities under the per-type threshold, so you get faster feedback and usable pipelines and deals sooner.

    Slow drip

    Heavy entity types import after the sprint so the system can pace work and stay within safe limits.

    Extremely large total volumes may show warnings in the UI. If you are near platform caps, coordinate with your admin before running a full migration.

    After migration

    Background jobs

    The import runs as a batch job. You do not need to keep the migration dialog open. If you close it, open Data Hub again to see status or use the global batch job entry points.

    Rollback

    If the import fails or you need to undo, the summary step explains when rollback is available. Use it to avoid a partially applied state you cannot reconcile manually.

    Ongoing source connection

    If you keep the source CRM integration connected for other purposes, that is separate from the one-time migration job. Treat migration as the initial bulk move; day-to-day sync rules depend on your integration settings.

    Quick Reference

    Start here: Data Hub → Lumenbase Portage → Pipedrive
    Requires: Source CRM integration connected
    Phases: Sprint first, then slow drip for very large entity types
    Background: Continue in background; watch batch job progress
    Related: CSV import (Data Hub) for smaller or custom files

    Was this article helpful?