Move your Pipedrive workspace to Lumenbase
Scan pipelines, stages, organizations, people, deals, and activities. Preview the result, then import.
- Read-only access to Pipedrive
- Preview before anything imports
- One-click rollback
See your move before you commit
Estimate your move
- Pipelines & stages
- Organizations, as companies
- People, linked to their organizations
- More data types and one-click rollback.
Comes over from Pipedrive
- Pipelines & stages
- Organizations, as companies
- People, linked to their organizations
- Deals with amount, currency, stage, owner, and status
- Activities on the timeline, including logged calls and emails
- Custom fields on organizations, people, and deals (you pick which)
- Owners mapped to your Lumenbase team members
How it works
Scan
Portage reads your old CRM and counts what is there. Nothing is written yet.
Choose
Pick what to bring over and match your old users to your new team.
Preview
Check counts, field mappings and warnings before a single record lands.
Import
The import runs in the background. Close the tab and keep working.
Review or roll back
See what came over. Not happy? Remove the imported records in one click.
Built to be safe to try
Read-only access to Pipedrive
Portage only reads from Pipedrive. Nothing in your source CRM is changed, moved, or deleted at any point in the migration.
One-click rollback
Not happy with the result? Roll the migration back in one click and every record it created is removed. Records you edited after the import, or that were merged into records you already had, are kept.
Preview before anything imports
A preview shows exact record counts, field mappings, and warnings (unmapped owners, missing links) before a single record is written.
Runs in the background, resumes if interrupted
Large workspaces move over gradually and pick up where they left off if interrupted. Your team keeps working in both tools while it runs.
Credentials stay encrypted
Your API key for Pipedrive is stored encrypted in this workspace's vault. Disconnect it anytime.
Migrate in passes without duplicates
Run Portage again whenever you like; already-imported records are detected and skipped, so re-runs never create duplicates.
Field-by-field mapping
Exactly which source field lands where. Open a record type to see it.
| Lumenbase field |  Pipeline |
|---|---|
| Name | name |
| Order | order_nr |
| Lumenbase field | Stage |
|---|---|
| Name | name |
| Order | order_nr |
| Pipeline | pipeline_id |
| Lumenbase field | Organization |
|---|---|
| Name | name |
| Address | address |
| Phone | phone |
| Website | website |
| Owner | owner_id |
| Lumenbase field | Person |
|---|---|
| First name | first_name |
| Last name | last_name |
emails[] / email | |
| Phone | phones[] / phone |
| Company | organization_id |
| Owner | owner_id |
| Lumenbase field | Deal |
|---|---|
| Title | title |
| Amount | value |
| Currency | currency |
| Status | status |
| Close date | expected_close_date |
| Owner | owner_id |
| Lumenbase field | Activity |
|---|---|
| Activity type | typeMapped to Lumenbase activity enum (call, email, meeting, task, note, …) |
| Title | subject |
| Date | due_date / due_time / add_time |
| Body | note |
| Owner | owner_id |
Rather not do it yourself?
Messy data, an unusual setup, or no time for it. We can run the migration with you, free.
Coming from somewhere else?
HubSpotPipelines · Stages · Companies · Contacts · Deals · NotesConnection: Service key or private app token, pasted in the Portage wizard