Migrate from Attio

    Move your Attio workspace to Lumenbase

    Portage imports companies, people, deals, and notes with the same guided wizard used for every Portage origin.

    Connection: API token (pasted in the Portage wizard)

    One-click rollback is built in.

    • Read-only access to Attio
    • Preview before anything imports
    • Runs in the background, resumes if interrupted
    Start trial and migrateAttio setup guide

    See your move before you commit

    Estimate the time and check what comes over. The source stays read-only, and you can roll back the import.

    Estimate your move

    Enter rough record counts. Times are estimates.

    ≈ 25 minfor 6,300 records
    • Companies & people (people linked to their company)
    • Deals with amount, currency, owner, and status
    • A default pipeline & stage so deals keep their structure
    • More data types and one-click rollback.
    Migrate from Attio

    Comes over from Attio

    • Companies & people (people linked to their company)
    • Deals with amount, currency, owner, and status
    • A default pipeline & stage so deals keep their structure
    • Notes on the record timeline
    • Owners mapped to your Lumenbase team members

    Other supported origins

    Portage uses one wizard in Data Hub for every CRM. Pick another origin or continue with your selection above.

    Pipedrive

    Connect with Pipedrive or paste an API token in Portage

    Entity types

    Pipelines · Stages · Organizations · Persons · Deals · Activities

    Migrate from PipedrivePipedrive migration guide

    HubSpot

    Private app service key (pasted in the Portage wizard)

    Entity types

    Pipelines · Stages · Companies · Contacts · Deals · Notes

    Migrate from HubSpotHubSpot migration guide

    Salesforce

    Connected App client credentials (pasted in the Portage wizard)

    Entity types

    Stages · Accounts · Contacts · Opportunities · Tasks

    Synthetic default pipeline; stages come from your Opportunity stage picklist.

    Migrate from SalesforceSalesforce migration guide

    Five-step Portage process

    Identical wizard flow for every origin: scan, configure, preview, import, summary.

    1. 1

      Scan

      Read-only inventory of your source CRM. Counts per entity type, sample records, and connection validation before anything is written.

    2. 2

      Configure

      Choose entity types to import and map source users to Lumenbase workspace members. Dependency order is enforced automatically.

    3. 3

      Preview

      Review record counts, sprint vs slow-drip pacing for large orgs, field mappings, and warnings (unmapped owners, empty types, missing relationships).

    4. 4

      Import

      Server-side batch job with checkpointed progress. Continue in the background; track status from Data Hub or Import History.

    5. 5

      Summary & rollback

      Per-entity import results, immutable entity origins, and session rollback that removes imported records using provenance rows.

    Guided process

    One five-step wizard for every supported CRM in Data Hub.

    • Unified Portage wizard

      Open Lumenbase Portage in Data Hub, then connect your source CRM.

    • Dependency-ordered import

      Imports pipelines, stages, companies, contacts, deals, then activities so links resolve in one pass.

    • User owner mapping

      Map source CRM users to Lumenbase members; unmapped owners surface as preview warnings.

    • Entity type selection

      Import only what you need; skipped types never touch the target workspace.

    • Background batch jobs

      Track live progress by the summary bar and view the full log in Import History.

    • Sprint + slow drip

      Entity types over 10,000 records import in a paced second phase to protect API budgets and server limits.

    • Pause & cancel

      Pause an in-flight import or cancel a scan; sessions resume from saved checkpoints.

    Checks & validations

    Checks run before, during, and after each import.

    • Connection validation

      Each origin validates credentials before scan (OAuth token, Attio API token, HubSpot service key).

    • Workspace membership

      Only members of the workspace can start or continue a migration session.

    • Active session guard

      One active Portage session per workspace per origin; prevents overlapping imports for the same CRM.

    • Preview warnings

      Unmapped users, zero-count entity types, and deals-without-companies relationship gaps.

    • Scan schema version

      Full pagination counts with no estimates from partial pages.

    • Duplicate-safe resume

      import_record_changes keyed by session + source_system + source_id skips already-imported rows on continuation.

    • Provenance-or-rollback

      If provenance write fails after insert, the entity row is deleted so resume never creates silent duplicates.

    • Immutable entity origins

      Each imported record gets a migration origin tag (provider, session, external source id) for audit and lineage.

    Process robustness

    Built for large workspaces, API limits, and server timeouts.

    • Chunked self-reinvoke

      Scan and import edge functions checkpoint progress and re-invoke on wall-clock or early_drop shutdowns.

    • Adaptive chunk sizing

      Import batches shrink after a timeout and grow after successful runs.

    • Rate-limit awareness

      Pipedrive: token budget headers and automatic pause metadata. All origins: stale-detector respects pause flags.

    • Stalled job recovery

      Cron + UI resume restart failed batch jobs when the session is still scanning or importing with a saved checkpoint.

    • Session rollback

      Chunked rollback via execute-import-rollback removes provenance-tracked entities and clears the session.

    • Import invocation limits

      Migration edge functions cap self-reinvoke depth to prevent runaway loops.

    • Cancel propagation

      Cancelled sessions abort continuations and mark linked batch jobs cancelled.

    Audit & lineage

    Know what was imported, from where, and undo it if needed.

    • import_record_changes

      Every imported row logged with migration_session_id, source_system, source_id, and target record_id for rollback.

    • entity_origins

      First-origin certificate: origin_kind=migration, origin_system=provider, origin_run_id=session, external_source_id=source key.

    • Batch job operational log

      Scan and import milestones appended to batch_jobs metadata for support and recovery.

    • Per-provider batch job types

      Distinct job types (e.g. attio_migration_import) for monitoring and stale-detector rules.

    Entity catalog & field mapping

    Import order is fixed across all origins: Pipelines → Stages → Companies → Contacts → Deals → Activities. Below: Lumenbase entity, origin object labels, API references, provenance keys, and field mappings.

    1. Pipelines

    pipelines

    Deal pipeline definitions and ordering.

    OriginObject labelAPI / sourceProvenance keyField mapping
    AttioDefault pipeline (synthetic)Portage default. Attio deals use status instead of Pipedrive-style pipelinesSingle default pipeline created so Attio deals can attach to a stage.pipelines
    • Name default → name → "Deals"

    2. Pipeline stages

    pipeline_stages

    Stages within each pipeline; linked to parent pipeline.

    OriginObject labelAPI / sourceProvenance keyField mapping
    AttioDefault stage (synthetic)Portage default. Maps the Attio deal status ID when presentLinks: pipeline_source_id: defaultDeal stage links use Attio status id when available on the deal record.stages
    • Name default-open → name → "Open"

    3. Companies

    companies

    Organizations / accounts.

    OriginObject labelAPI / sourceProvenance keyField mapping
    AttioCompanyPOST /v2/objects/companies/records/querycompanies
    • Name values.name → name
    • Domain / website values.domains → website
    • Owner values.created_by → created_by

    4. Contacts

    contacts

    People; optionally linked to a company.

    OriginObject labelAPI / sourceProvenance keyField mapping
    AttioPersonPOST /v2/objects/people/records/queryLinks: values.company | primary_company → companypeople
    • First name values.first_name | name → first_name
    • Last name values.last_name | name → last_name
    • Email values.email_addresses → email
    • Phone values.phone_numbers → phone
    • Company link values.company → company_id
    • Owner values.created_by → created_by

    5. Deals

    deals

    Opportunities linked to company, contact, pipeline, and stage when available.

    OriginObject labelAPI / sourceProvenance keyField mapping
    AttioDealPOST /v2/objects/deals/records/queryLinks: company, person, stage (status id)deals
    • Title values.name → title
    • Amount values.value → amount
    • Currency values.value.currency_code → currency
    • Stage link values.stage.status.id → stage_id
    • Owner values.created_by → created_by

    6. Activities

    activities

    Timeline activities (notes and typed activities) linked to company, contact, or deal.

    OriginObject labelAPI / sourceProvenance keyField mapping
    AttioNoteGET /v2/notesLinks: parent_object + parent_record_idnotes
    • Title title → title
    • Body content_plaintext → description
    • When created_at → occurred_at
    • Type (fixed) → type → note

    Sign up, connect your CRM in Integrations, then run Lumenbase Portage from Data Hub, one wizard for every origin.

    Try the full workspace free for 14 days. No credit card required.