Oracle Sales → Attio

Catalog plan outline

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

Migration friendliness

Oracle Sales 4/10 · Attio 7/10

Speed to live

Oracle Sales 2/10 · Attio 7/10

Catalog migration difficulty

Oracle Sales high · Attio not set

Data to export from Oracle Sales

• pipeline and deal records
• custom objects
• sequences and cadences
• call and voice logs
• 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: call and voice logs, campaign and automation records, installed marketplace apps.
• Oracle Sales is flagged with an open API, which is the export path to test.
• Attio is flagged with an open API for the load.
• Oracle Sales is cataloged as a fit for: Oracle 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 Oracle Sales as the source of truth for this pair. Export pipeline and deal records; custom objects; sequences and cadences; call and voice logs; 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 CX sales cloud — accounts, quotes, and Oracle gravity.

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 Oracle Sales before a full cutover.

4. Cut over

   Oracle Sales scores 4/10 on migration friendliness and is marked high difficulty in the catalog. Keep Oracle Sales readable until the team is working in Attio. Oracle Sales (CX Sales) is the incumbent when the rest of the stack is already Fusion or E-Business. AI has been added onto a CRM whose center of gravity is ERP, not a sales OS. A leave-from for global account teams; a poor first CRM.

Oracle Sales to Attio: what the vendor docs actually cover

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

What to export from Oracle Sales

Oracle Fusion Cloud Sales does not hand Attio a ready spreadsheet. The public export path opened on 2026-10-18 is the CX Sales REST bulk-export activity at /crmRestApi/resources/11.13.18.05/bulkExportActivities. You first GET importExportObjectMetadata, ordered by DisplayName, and read ExportSupport. The Account example returns PuidAttribute PartyNumber, KeyAttributes PartyId, and a RequiredFields list that includes OwnerPartyNumber, PartyNumberKey, ConflictId, AddressNumber, Country, OrganizationProfileId, OrganizationName, and SalesProfileNumber. Activity uses ActivityNumber. Address uses AddressNumber. A single-object POST needs Name, ExportObject, ExportColumnNames, ExportFilterCriteria, ExportFileName, and Activate. The Account sample sets Activate to YES, names the file test_Acc.zip, and filters OrganizationName. The response Status starts at QUEUED and returns a BulkExportJobId. A later GET on that id reports COMPLETE, ERROR, or COMPLETE_WITH_ERRORS, plus RecordsExported and an ExportFileURL. Hierarchy exports nest childBulkExportActivity: the guide's example pulls Address (City, Country, State, Status) and Classification (PartyType, ClassCategory, ClassCode) under Account, with ExportParentObject set to Account. You can leave Activate at NO and PATCH it to YES later, or pass an ExportMapping number instead of columns. PrivateMaps set to Y keeps a map private. EnableSplit YES with SplitSize 100000 produces several zip attachments such as Account_Split_1.zip, downloaded from the child Attachments link. The sample payload's Delimiter is COMMA_DELIMITER and FileCharset is ORA_ZCA_UTF8_ENCODING. That zip is Oracle's file, not an Attio import. Quote-to-cash objects (CPQ, orders, subscriptions, incentive compensation) are separate Fusion services. They are not columns in the Account example.

• Oracle CX Sales export data using REST — checked 2026-10-18
• Oracle Fusion Cloud Service global price list (8 October 2026) — checked 2026-10-18

How Attio imports

Attio's migration article, reopened 2026-10-18, lists Import2 sources by name. Oracle, Fusion Sales, and CX Sales are absent. MS Dynamics, Salesforce, and HubSpot CRM are present, which is why this pair cannot borrow their button. The article's fallback for an unlisted source is a CSV file or the API. The CSV article says the file door is on every plan. Admins may import. Members may import only with read-and-write or full access on the object or list. The file must be CSV, must have a header, and is capped at 100,000 rows, 100 columns, and 100 megabytes. Empty cells are skipped and do not wipe a value already stored. New attributes can be created while mapping. Notes are not accepted through that CSV door. Objects such as companies and people map to Attio objects, not to lists, when you use Import2; the CSV door is what you use if a Fusion extract should land on a list. Attio's pricing page the same day shows Free at $0, Plus at $44 per user per month or $35 if billed annually, and Pro at $99 or $79 on the annual cycle. Enterprise is billed annually and prints no seat fee. The FAQ says the free option is for teams with fewer than 3 people, Plus goes up to 10 seats, and there is a 14-day Pro trial. One compare row calls Pro seats unlimited and another row on the same page says up to 12. The catalog stores the $0 start, the free-plan flag, the trial flag, and the $35 / $44 and $79 / $99 figures. It does not store a Pro seat cap, so that internal clash was not edited into the catalog. The October 8, 2026 Fusion price list, opened the same day as this review, prices Oracle Fusion Sales Enterprise Cloud Service at 150.00 per hosted named user per month, minimum 10, part B95942, and Oracle Fusion Sales and Service Limited Cloud Service at 25.00 per hosted named user per month, minimum 10, part B89673. Rechecked 2026-10-19, the catalog starting price for Oracle Sales is $25, the Limited hosted-named-user price, and the note also stores Enterprise at $150. Those list figures were not written into it. The current oracle.com/cx/sales page prints no dollar and no trial length. A Release 13.1 trial document describes a 30-day trial for an older Oracle Sales Cloud Service name. That document is not the October 2026 Fusion price list, so the catalog trial flag on Oracle Sales is false. The current product page and the October 8, 2026 list do not state a trial.

• 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

• Oracle Account.OrganizationName is a display string. Attio's company identity on the migration article is the root domain, not a legal name and not a full URL.
• PartyNumber and PartyId have no Attio attribute until you create one during the CSV map. They are Oracle's public unique id and internal key, not an email.
• EmailAddress on the Account export sample can be an account-level address. Attio people match on a person email. Do not pour an account mailbox into the person email column without a contact row.
• The Address child job (City, Country, State, Status) is a second payload under ExportParentObject Account. Attio does not inherit that parent link from the zip.
• Classification columns such as ClassCategory and ClassCode are Fusion party classes. They are not Attio company categories unless you map them on purpose.
• A filter on LastUpdateDate, written as an attribute code inside ExportFilterCriteria, is how you cut a delta. Attio's CSV import has no equivalent incremental cursor.
• EnableSplit and SplitSize 100000 mean several zip parts. Attio's 100,000-row CSV ceiling is a different limit on a different file type. Unzip, then recount rows before upload.
• Quotes, subscriptions, and compensation participants are separate price-list SKUs (Incentive Compensation is 75.00 per compensated participant, minimum 500, part B96471). They are not Account columns.

What will not carry over

• Fusion role security, approval matrices, and Redwood page layouts.
• The UCM FileUrl signatures on the attachment payload. Those links expire and are not records.
• Incentive plans, order management, and subscription billing. They live on other Fusion services.
• Notes, if the only door you use is Attio CSV. The CSV article does not take them.
• An Import2 button for Oracle. The supported-CRM list does not name it.
• A confirmed current Fusion Sales trial. The product page and the October 8, 2026 price list do not state one.
• The catalog's empty Oracle starting price. The price list does publish 150.00 and 25.00. The catalog was left unchanged.
• Agentic sales assistants on the Fusion marketing page. Attio does not ingest those agents.

Cutover checklist

1. GET importExportObjectMetadata and keep only objects whose ExportSupport is Y.
2. Export Account with PartyNumber, OrganizationName, and a real domain column if one exists in your metadata. The sample columns do not include a website.
3. Run Address and Classification as child activities, not as extra headers glued onto the Account file.
4. Poll BulkExportJobId until Status is COMPLETE. COMPLETE_WITH_ERRORS needs the error report before anyone treats the zip as complete.
5. If EnableSplit is YES, download every Account_Split zip from Attachments. A single ExportFileURL is the unsplit case.
6. Convert the delimited extract to CSV with a header. Stay inside 100,000 rows, 100 columns, and 100 megabytes per Attio file.
7. Map the company on a root domain. Leave PartyNumber in a custom attribute if you still need to trace the Fusion party.
8. Put people in a separate file keyed by a person email. Do not reuse the account EmailAddress as that key.
9. Leave notes out of the CSV. Plan a different path if activity history matters.
10. Keep Fusion writable until a sample of accounts and people has been checked in Attio. The REST job does not switch Fusion to read-only.
11. Quote Oracle from the October 8, 2026 list (150.00 Enterprise, minimum 10, or 25.00 Limited, minimum 10) and Attio from the pricing page ($0, $35/$44, $79/$99). The catalog now stores Limited at $25 as the starting price and Enterprise at $150 in the note.
12. Ignore the Release 13.1 30-day trial page when you brief a current Fusion tenant. It names an older service.

Common pitfalls

• Uploading the zip to Attio. The CSV article accepts a .csv file, not a zip of split extracts.
• Treating PartyNumber as Attio's company key. The migration article's company key is the domain.
• Assuming Import2's Salesforce object list (Contacts, Accounts, Leads, Opportunities) applies to Fusion. Oracle is not in the source list.
• Scheduling cutover on a QUEUED job. Status has to reach COMPLETE.
• Quoting a Fusion trial. The current product page and the October 8, 2026 list do not state one, and the catalog trial flag is false.
• Collapsing Incentive Compensation or CPQ into the Account export because the marketing site describes one quote-to-cash flow.

Related catalog pages

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