SAP Sales Cloud → Attio

Catalog plan outline

General guidance from the Afterstack catalog for SAP Sales Cloud → Attio. Not SAP Sales Cloud or Attio vendor documentation.

Migration friendliness

SAP Sales Cloud 4/10 · Attio 7/10

Speed to live

SAP Sales Cloud 2/10 · Attio 7/10

Catalog migration difficulty

SAP Sales Cloud high · Attio not set

Data to export from SAP Sales Cloud

• pipeline and deal records
• custom objects
• sequences and cadences
• synced email and calendar links
• workflow rules
• saved reports
• campaign and automation records
• installed marketplace apps
• AI assistant configuration
• records for the catalog use cases: accounts, pipeline

How the catalogs differ

• Attio is flagged for custom objects. Collapse unused fields before loading them.
• Attio is not flagged for: campaign and automation records, installed marketplace apps.
• SAP Sales Cloud is flagged with an open API, which is the export path to test.
• Attio is flagged with an open API for the load.
• SAP Sales Cloud is cataloged as a fit for: SAP ERP campuses.
• Attio is cataloged as a fit for: Product-led and sales-led startups that treat the data model as the product.

Phases

1. Export

   Take SAP Sales Cloud as the source of truth for this pair. Export pipeline and deal records; custom objects; sequences and cadences; synced email and calendar links; workflow rules; saved reports; campaign and automation records; installed marketplace apps; AI assistant configuration; records for the catalog use cases: accounts, pipeline. Enterprise sales on SAP — accounts, quotes, and a services army.

2. Map

   Load into Attio only after the field map is written down. A CRM that treats your data model as the product. Attio is flagged for custom objects. Collapse unused fields before loading them.

3. Prove a sample

   Attio scores 7/10 on speed to live and 7/10 on migration friendliness. Run one sample load and one report the team already uses in SAP Sales Cloud before a full cutover.

4. Cut over

   SAP Sales Cloud scores 4/10 on migration friendliness and is marked high difficulty in the catalog. Keep SAP Sales Cloud readable until the team is working in Attio. SAP Sales Cloud (the CRM cloud in the SAP customer-experience set) is what you run when order-to-cash already lives in SAP. AI features have been added onto a platform whose center of gravity is ERP, not a sales OS. A plausible leave-from for global manufacturers; a poor fit as a startup CRM.

SAP Sales Cloud to Attio: what the vendor docs actually cover

Linked sentences come from vendor documentation opened for this page. Everything else is general guidance, not SAP Sales Cloud or Attio vendor documentation. This section does not move data and does not change the catalog outline above.

What to export from SAP Sales Cloud

SAP's public export for the Cloud for Customer generation of Sales Cloud is Data Workbench, in the help PDF opened 2026-10-18. From the Data Workbench work center, choose Export, then a standard business object or a custom one. Pick the object (the guide's example is Activities). Select Data if you want a subset, and add filters on fields that belong to that object. The guide's filter example is accounts whose role is prospect. Select fields next. Select All is the default. Choose Comma Separated Values (.csv) or Excel Workbook (.xlsx). The Schedule Task switch can defer the job up to 72 hours from now. Until that time the task stays idle, then becomes In Queue. Secure Data, if on, strips =, +, -, and @ from the start of cells. Export Data starts the job. Monitor shows Completed, and the file name is the download. More than 50,000 records split into multiple files, each capped at 50,000, with a Download All control. The same PDF's Data Workbench APIs are an import path (authentication, template, import) and the restriction line says those APIs do not import attachments. They are not the export procedure. A second public document, the OData services guide, says the tenant API is https://<your_tenant>/sap/c4c/odata/v1/c4codataapi and metadata is that URL plus /$metadata. Authentication options listed are Basic, OAuth 2.0, X.509, and SAML. The product page for current SAP Sales Cloud, also opened 2026-10-18, describes a move from the classic product to Version 2 and points at a transition journey. It does not paste the V2 entity matrix. A support note number for that matrix showed up in search and was not opened as a public page, so this writeup does not claim which V2 entities export. Pricing.html for Sales Cloud rendered no dollar amount. The trial page states a limited-time 30-day basic trial on a shared tenant with sample data, and says key-user rights for customization, master data, and integration are not in that trial.

• SAP Cloud for Customer Data Workbench — checked 2026-10-18
• SAP Cloud for Customer OData services — checked 2026-10-18
• SAP Sales Cloud pricing — checked 2026-10-18
• SAP Sales Cloud basic trial — checked 2026-10-18

How Attio imports

Attio's Import2 source list, checked again 2026-10-18, names MS Dynamics, Salesforce, HubSpot CRM, SugarCRM, and Zoho CRM. It does not name SAP, Sales Cloud, or Cloud for Customer. The article tells you to use CSV or the API when the source is missing. CSV import is available on all Attio plans. A header is mandatory. Ceilings are 100,000 rows, 100 columns, and 100 megabytes. That row ceiling is twice the 50,000-row slice Data Workbench writes, so a full SAP extract can arrive as several files that each fit, or as one joined file that does not. Members need read-and-write or full access on the destination object. Empty CSV cells do not overwrite. The migration article also says that if you load records by CSV you can still ask Import2 (help@import2.com, copy support@attio.com) to bring notes afterward, because the CSV door itself refuses notes. That is a services request, not a SAP connector. Attio's pricing page shows Free at $0, Plus at $44 monthly or $35 annually, Pro at $99 monthly or $79 annually, and Enterprise billed annually with no printed fee. The FAQ confirms a 14-day Pro trial and a free option for teams under 3 people. Those dollar figures match the catalog price note. SAP's catalog starting price is empty, which matches a pricing page that printed no rate. The catalog trial flag matches the 30-day basic trial. The trial's own limits matter: sample data, no master-data administration, so it is not a dress rehearsal for a tenant export.

• Attio migrate from another CRM — checked 2026-10-18
• Attio CSV import — checked 2026-10-18
• Attio pricing — checked 2026-10-18

Object and field mapping

• A Data Workbench account export is a standard business object file. Attio will not see SAP's internal UUID unless you map that column to an attribute you create.
• The prospect-role filter in the Workbench guide is a subset, not a field Attio understands. Apply it before download if you only want prospects.
• Company match on the Attio side, for any later Import2 pass, is the root domain. An SAP account name is not that key. Put a domain column in the file on purpose.
• Contacts are a different object from accounts. The Workbench procedure is one object per export. A contact file needs its own job.
• Opportunities and leads are not inside the account file. The product page describes pipeline and forecasting. It does not say they ride along in an account export.
• XLSX versus CSV is a Workbench choice. Attio's documented file door is CSV only. An .xlsx download still needs a CSV save.
• Secure Data stripping of leading =, +, -, and @ can change a cell that was a formula-looking phone or a negative number. Check those columns before mapping.
• OData collections such as the tenant c4codataapi are a read API, not a file Attio ingests. A script would still have to emit CSV or call Attio's API. This page does not invent that script.

What will not carry over

• SAP ERP and S/4HANA order, pricing, and availability views. The product page says Sales Cloud connects to them. Attio does not receive that connection.
• Guided selling steps, visit plans, and Joule. They are product behavior, not Workbench columns described in the export PDF.
• Workbench schedules. A task can wait 72 hours inside SAP. Attio has no queue for that schedule.
• Files past the 50,000-row split if you only download the first part.
• Notes, unless you use a path other than CSV. The CSV article excludes them. Import2 can be asked to load notes later, and SAP is still not a listed source.
• A public SAP seat price. pricing.html showed no figure. The empty catalog starting price was left as-is.
• Master data edited inside the 30-day basic trial. The trial page says those admin rights are not included.
• Version 2 entity coverage. It was not on a public page this review opened.

Cutover checklist

1. Confirm whether the tenant is classic Cloud for Customer or Sales Cloud Version 2. The Workbench PDF is the classic export. V2 steps were not on a page opened here.
2. Export accounts with an explicit domain column and only the fields you will map. Select All is the default and will blow the 100-column CSV cap.
3. Export contacts as a second object. Do not expect them inside the account file.
4. If the monitor splits the job, use Download All. Each part holds at most 50,000 records.
5. Turn Secure Data on only if you accept the leading-character strip, and spot-check phones and negatives afterward.
6. Save as CSV with a header. Keep each Attio upload at or under 100,000 rows, 100 columns, and 100 megabytes.
7. Map companies on the root domain. Store the SAP id in a custom attribute if finance still needs it.
8. Leave notes out of the spreadsheet. If history matters, treat it as a separate request, not as a completed import.
9. Do not rehearse the export inside the basic trial. That tenant is sample data without master-data administration.
10. Keep the SAP tenant as the system of record until a counted sample of accounts and contacts exists in Attio.
11. Quote SAP as no public seat price, with a 30-day basic trial. Quote Attio from its own pricing page. Leave both catalog records unchanged.

Common pitfalls

• Calling Import2's MS Dynamics entry a SAP connector. The list uses those names separately, and SAP is missing.
• Uploading the .xlsx Workbench file. Attio's file article says CSV only.
• Joining three 50,000-row slices into one sheet and then hitting Attio's row cap.
• Using the basic trial as proof you can export a production tenant.
• Assuming Version 2 uses the same Workbench clicks. The product page sends that move to a transition guide this review did not treat as the export procedure.
• Reading a missing price on pricing.html as a free SAP Sales Cloud. The page was a narrative, not a zero-dollar card. The catalog null was not edited.

Related catalog pages

• What should replace SAP Sales Cloud? — Switch narrative
• Attio product page — A CRM that treats your data model as the product.
• CRM & sales category — Catalog hub for this category