Salesforce · CRM · Transactional
Migrate opportunities into Salesforce, covering the opportunity record, sales stage and close date, line items and price books, ownership, forecasting impact and historical pipeline scope.
Opportunities are where a CRM migration becomes visible to the business on day one. Stage and close date drive forecasting, so a mapping error does not produce a data problem — it produces a wrong forecast in front of sales leadership.
The object also depends on almost everything else: the account, the owner, the price book and the products. It loads late, and it is where earlier shortcuts in account and product migration surface.
Scope is agreed in discovery; this is the shape of the object.
| Data area | Typical information |
|---|---|
| Opportunity | Name, account, amount, close date, stage, type, lead source, probability |
| Line items | Products, quantities, prices, referencing a price book entry |
| Ownership | Owner user, which drives visibility and forecast attribution |
| RecordType | Which sales process and stage picklist applies |
| Stage history | Where historical stage movement is in scope |
| Related records | Contact roles, activities, quotes where in scope |
Dependency drives load sequence: a child cannot exist before its parent.
Confirm each of these before the first migration cycle.
Production-proven means we have delivered this object from that source. Supported and custom-mapping describe capability, not delivery history.
Object-level equivalence. Field-level mapping is produced per engagement.
| Source system | Source entity | Target object |
|---|---|---|
| Oracle Fusion CX | Opportunity + revenue lines | Salesforce Opportunity + line items |
| Dynamics 365 | Opportunity + opportunity products | Salesforce Opportunity + line items |
| SAP CRM | Opportunity transaction | Salesforce Opportunity |
Bulk API 2.0 with upsert against an External Id
Line items loaded after opportunities and after price book entries exist
Closed opportunities loaded with their final stage rather than replayed through stages
Every opportunity resolves to a loaded account.
Stage picklists differ by sales process.
Required, and its plausibility checked for open opportunities.
For every line item, in the opportunity's price book.
Inactive users cannot own records.
Where amount is derived from line items rather than entered.
What has to exist before this object can load.
What actually fails on this object, and why.
Counts alone rarely prove this object migrated correctly.
Open opportunity count and total pipeline value: source vs loaded
Pipeline by stage compared to source — the check that proves stage mapping is right
Closed-won value by period, where historical closed business is in scope
Line item count and total against opportunity amounts
Ownership distribution, including fallback-owner count
Forecast comparison run in the target and compared to the source forecast before sign-off
Closed-lost pipeline is a common archive candidate. It carries analytical value but no operational purpose, and it can easily outnumber open pipeline several times over. Migrating open opportunities plus closed-won history, and archiving the rest, keeps the CRM focused while preserving the analysis.
Extraction, mapping, transformation, validation preparation and target load generation.
Explore DataMove →Preserves source, prepared and target states for reconciliation, lineage and audit evidence.
Explore DataVault →Migration progress, data quality, exceptions and readiness across cycles.
Explore DataLens →Source-specific guidance for moving this object.
Published case studies whose scope included opportunities.
Tell us your source application, target system, object scope, volume and migration timeline. We can discuss the recommended migration approach and relevant Syntra ETL project experience.