---
title: "Salesforce to Attio migration | Rig"
description: "Move customer records, relationships and sales history from Salesforce to Attio. Rig maps the fields, tests sample records and reconciles the move with your sales and operations owners."
canonical: "https://rig.so/migrate/salesforce-to-attio"
format: markdown
---

Migration

# Salesforce to Attio migration

Move customer records, relationships and sales history from Salesforce to Attio. Rig maps the fields, tests sample records and reconciles the move with your sales and operations owners.

By [Rig](https://rig.so/about) · Last updated 11 November 2026

[Get a migration plan](https://rig.so/book-demo)

[Download the migration checklist](https://rig.so/downloads/migration-checklist.csv)

## At a glance

- Rig scopes the data, logic and integrations before agreeing a fixed delivery price.
- Move in checked waves, with a parallel run where possible.
- Keep history and test permissions as part of acceptance.
- Your system owners approve the mappings and cutover.

01**Inventory**

Records, logic and owners

02**Map and rebuild**

Source to target definitions

03**Run in parallel**

Counts, totals and access

04**Accept and switch**

Sign-off and rollback plan

Each wave ends with an acceptance check. This diagram shows the delivery process.

## Map the data and the logic it carries

This is a starting inventory. The target edition, customisations and API access determine the final mapping. An object with the same name can still behave differently.

| Source | Target or retained output | Checks and known traps |
| --- | --- | --- |
| Account | Company | Preserve company IDs, domains and parent relationships. |
| Contact and Lead | Person | Merge duplicates deliberately; preserve consent and source IDs. |
| Opportunity | Deal or custom object | Map currencies, stages, owners and line items separately. |
| Task and Event | Notes and tasks | Confirm API coverage for attachments, timestamps and associations. |
| Custom objects and record types | Lists and custom attributes | Check target licence limits; rebuild automation and reports separately. |
| Owners, teams and access | Target users, teams and roles | Map inactive owners and service users; test record visibility before release. |
| Campaign membership and attribution | Target properties, associations or history archive | Preserve the source attribution separately when the target cannot reproduce it. |
| Picklists and sales stages | Target enumerations and pipelines | Keep original values, then approve a translation for closed and active stages. |
| Products and opportunity line items | Target products, deal lines or custom records | Check SKU relationships, quantities, discounts and currency precision. |

## Preserve the sales process as well as the records

Map owners, teams, pipeline stages and picklist values explicitly. Salesforce leads do not have a direct equivalent in every target. Activities, campaign attribution and custom objects need a sample import before the full migration. Rebuild workflows against the target permissions and test them with the people who use them.

## Connect, scope and run the migration in Rig

Rig natively maps systems and data across the IT estate, connects source and target systems and supports schema-to-schema mapping with record previews. Scope the objects and history, prepare the destination, then rehearse the load and reconcile the results. Track sign-off, cutover and follow-up tasks in the same migration workspace.

## Agree a timeline against the actual scope

These are planning allowances for individual phases, not a promise for the whole project. Large estates need repeated waves, and application configuration can add time.

| Phase | Initial planning allowance | Exit check |
| --- | --- | --- |
| Assessment | 3 to 5 working days | Owners, access and inventory agreed |
| Sample and mapping | 5 to 10 working days | Sample records and exceptions reviewed |
| Build and parallel validation | 2 to 6 weeks per wave | Counts, totals and permissions accepted |
| Final sync and cutover | 1 to 3 working days per wave | Business owner signs off; rollback remains available |

## Keep the evidence for each migration wave

You receive the source-to-target mappings, a reconciliation report, an exception log and a cutover checklist. Test duplicates, missing relationships, deleted records, time zones and permissions as well as headline totals. Keep the old system available until the agreed retention and rollback checks pass.

## Where Rig may fall short

Rig is a data infrastructure and implementation partner. A migration that only needs a supported CSV import may be simpler to do yourself. Sub-minute operational replication, a full ERP implementation and specialist application redesign need a separate scope or another provider. Confirm connector coverage before committing to Ingest.

## Check the import method before the full move

Attio CSV imports create and update records, while notes and tasks need separate handling through its API. When the source contains attachments, private activities or custom relationships that the target cannot reproduce, agree an archive and give users a tested way to find that history after cutover.

Inside Rig Migrate

## Run the migration in Rig, from the systems map to cutover

Rig natively maps systems and data across your IT estate, connects source and target systems, scopes the move and maps one schema to another. The same migration workspace tracks destination preparation, rehearsals, reconciliation, sign-off and the work after cutover, so your team can review the decisions and progress in one place.

1. ### Map the IT estate
   
   Map systems, data and integration flows across the IT estate. See which reports, processes and teams depend on the systems you plan to change.
2. ### Set up the migration
   
   Create the migration in Rig and record the source, destination and work to deliver. Keep the migration tasks and progress together.
3. ### Connect and discover
   
   Connect the source and target systems, then inspect their schemas and available data. Confirm access before deciding how each object will move.
4. ### Scope the work
   
   Choose the objects, fields and history to migrate. Record what stays, what changes and the dependencies the migration needs to preserve.
5. ### Map schema to schema
   
   Map source objects and fields to the target schema. Preview records and review rules to copy, translate, calculate, link, look up and match owners.
6. ### Prepare the destination
   
   Track the target preparation needed before loading data, including its configuration and the relationships your mapped records will use.
7. ### Rehearse the load
   
   Dry run the whole load and rehearse it in the destination environment. Review the results and resolve issues before the production cutover.
8. ### Reconcile and sign off
   
   Compare source and target records, relationships and business totals. Review exceptions with the system owners and record acceptance before proceeding.
9. ### Cut over
   
   Work through the agreed cutover tasks in Rig. Coordinate the final load and user switch with the people who own the systems.
10. ### Check after cutover
    
    Track the checks after the switch, confirm that reporting and processes work, and resolve outstanding issues before retiring the old setup.

[![Rig migration task list showing the systems map, setup, connection, scope, design, destination preparation, rehearsal, reconciliation, cutover and after-cutover stages](https://rig.so/migration-stages.png)](https://rig.so/migration-stages.png)

Migration stages and task progress in Rig. [View the full-size screenshot](https://rig.so/migration-stages.png).

### Inspect source values and target previews

The migration workbench shows source fields, target previews and the rule for each mapping. Your team can review translated values, linked records and calculated fields before signing off the mapping and rehearsing the load.

[![Rig Migrate workbench mapping a Dynamics 365 CE quote to Salesforce CPQ, with source values, target previews and translation, link and calculation rules](https://rig.so/migration-workbench.png)](https://rig.so/migration-workbench.png)

A D365 CE to Salesforce CPQ example. The workbench shows mapping decisions and migration tasks; this is not a completed cutover. [View the full-size screenshot](https://rig.so/migration-workbench.png).

### Reporting migration at Birdie

Birdie reports rebuilding sales and marketing reporting in less than a day. Its team kept Snowflake and the existing Fivetran pipelines; retirement of the Looker licence is not confirmed.

[Read the migration case study](https://rig.so/case-studies/birdie)

![Salesforce permission set object settings used when reviewing migration access](https://rig.so/salesforce-permission-set-object-settings.png)

Review source permissions before extracting CRM data.

## Common questions

What moves in this migration?

Move customer records, relationships and sales history from Salesforce to Attio. Rig maps the fields, tests sample records and reconciles the move with your sales and operations owners.

How much does a migration cost?

Rig maps the work and agrees a fixed delivery price before the migration starts. Source access, custom logic, history and the number of integrations affect the scope. Platform and third-party licence costs are agreed separately.

Can we keep reporting history?

Yes, where the source permits extraction. Agree which history belongs in the target system and which stays in a governed archive. Reconcile both against the original records.

How do you check that the data matches?

Compare record counts, identifiers, relationships and business totals for each wave. Record exceptions and require the business owner to accept the results before cutover.

Will both systems run during the move?

Plan a parallel run where the systems and licences allow it. Agree the source of truth, final changes, rollback conditions and the point at which users switch.

Who does the implementation?

Rig engineers work with your system owners. Your team approves mappings, permissions and acceptance checks. Application configuration and specialist ERP or CPQ work must be included in scope or assigned to your application partner.

Is there a guaranteed completion date?

The assessment produces a dated plan. The planning ranges on this page are estimates, subject to access, data quality, target readiness and user acceptance.

## Related guides and services

[Data migration services for systems, warehouses and reporting](https://rig.so/services/data-migration)[migrate](https://rig.so/products/migrate)[CRM data migration services with checked records and history](https://rig.so/services/crm-data-migration)[salesforce](https://rig.so/integrations/salesforce)[attio](https://rig.so/integrations/attio)[connect salesforce migration](https://rig.so/guides/connect-salesforce-migration)

## Sources and product details

Vendor information checked on 11 November 2026. Confirm current editions, licence terms and prices with the vendor before buying.

- [Salesforce Data Loader guide](https://developer.salesforce.com/docs/platform/data-loader-impl/guide/data-loader-using.html)
- [Attio imports and exports](https://attio.com/help/reference/imports-exports)

Talk to Rig

## Plan the move around the work you need to keep

Tell us where your team spends time, loses money or needs better information.
In a 30-minute call, we’ll discuss the data and systems work that could help.

[Get a migration plan](https://rig.so/book-demo)Use the platform with your team, or add our engineers.

---

- [This page as HTML](https://rig.so/migrate/salesforce-to-attio)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)