SAP S/4HANA to Salesforce Migration: ASC 606 Revenue Recognition Continuity
Migrating from SAP S/4HANA to Salesforce creates a revenue recognition cutover problem: open contracts have ASC 606 accounting treatments configured in the source system that must be replicated exactly in the target—with no gap in compliance and no revenue timing distortion.
Why revenue recognition makes ERP migrations harder
An ERP migration affects the revenue recognition module in three ways. First, contract data must be mapped: performance obligations, SSP schedules, and allocation tables configured in SAP S/4HANA must be reproduced in Salesforce with the same economic result. Second, open contracts require a cutover treatment: revenue recognised to date must be preserved and the remainder must continue to recognise correctly under the new system. Third, the disclosure data must be continuous: opening contract balances, cumulative revenue recognised, and remaining performance obligation amounts must be consistent across the reporting boundary.
The hardest part: Migrating contract data between systems that represent performance obligations differently. SAP S/4HANA and Salesforce may structure multi-element contracts using different data models—what is one performance obligation in SAP S/4HANA may need to be represented as two in Salesforce, or vice versa. This is a policy question that must be resolved before data migration begins.
Source and target: ASC 606 capability
| Attribute | SAP S/4HANA (source) | Salesforce (target) |
|---|---|---|
| ASC 606 module | Yes — Revenue Accounting and Reporting (RAR) module | No native — requires integration with financial ERP |
| Compliance modules | SOX, HIPAA, GDPR, ASC 606 | HIPAA, GDPR |
| Deployment model | Cloud (RISE), On-premise, Hybrid | Cloud (SaaS) |
Migration sequence for ASC 606 continuity
- Contract portfolio inventory. Document every contract type, performance obligation structure, and SSP methodology in SAP S/4HANA before migration begins.
- Policy alignment. Confirm that your ASC 606 accounting policies can be represented in Salesforce without requiring policy changes. Policy changes trigger disclosure requirements.
- Data mapping. Map each performance obligation type, contract attribute, and accounting treatment from SAP S/4HANA data model to Salesforce data model.
- Parallel run. Run both systems simultaneously for at least one reporting period to confirm revenue recognised is identical under both configurations.
- Cutover. Define the cutover date, transfer open contract balances (contract assets, contract liabilities, remaining performance obligations), and close the source system for new revenue transactions.
- Disclosure continuity. Ensure the period-end disclosures in the first post-cutover period correctly reflect pre-cutover contract activity. The opening balance disclosure is the most common error.
Frequently asked questions
Do we need to restate prior periods when we change ERP systems?
No—changing ERP systems is not an accounting policy change and does not trigger a restatement. However, if the migration results in different accounting treatments for open contracts (because the new system cannot represent the original policy), that may constitute a change in accounting policy that requires disclosure and potentially a cumulative adjustment.
What happens to deferred revenue (contract liabilities) during the migration?
Contract liabilities must be transferred to the target system with the same balances and the same remaining performance obligation schedules as in the source system. The cutover journal entry credits the new system with the same contract liability balance that existed in the old system at the cutover date.
Ready to map your contracts to ASC 606?
An assessment takes one hour. We review your contract portfolio, identify the hard judgement areas, and give you a prioritised remediation plan.
Book an assessment