Native Salesforce Sync - SOAP API migration to REST API | Community
Skip to main content
P
PavelIv1
Level 2
July 9, 2026
Solved

Native Salesforce Sync - SOAP API migration to REST API

  • July 9, 2026
  • 3 replies
  • 63 views

Hi everyone,

I'm a bit confused about the retirement of the SOAP API and the required migration to the REST API.

Does this change apply to Marketo's native Salesforce Sync as well?

My confusion comes from the fact that the Salesforce sync is typically configured once and then runs continuously. A migration from one API to another sounds like it might require changes to the sync configuration, but I haven't found any documentation that clarifies whether that's actually the case.

I've searched the community using several different terms but couldn't find any discussions about this. Given the impact of the SOAP API retirement, I expected there to be more conversation around it, so I thought I'd ask here.

Can anyone clarify whether any action is required for customers using the native Salesforce Sync?

Thank you!

Best answer by BlaneMcMichen-1

No action is required for the native Salesforce Sync itself just because of the Marketo SOAP API retirement.

That retirement is aimed at customer-built or third-party integrations that call Marketo's SOAP API. The native Salesforce Sync is a separate managed CRM sync capability in Marketo Engage, and Adobe continues to support it. In fact, Adobe's Salesforce sync documentation shows the native sync using its own supported authentication flow, including OAuth 2.0 for Salesforce sync operations. For newer subscribers, OAuth support for Salesforce CRM syncing has been available by default, and existing subscribers can enable it as needed. 2021 Log in Using OAuth 2.0

So, if a customer is only using the native Marketo ↔ Salesforce sync, they do not need to "migrate the sync from SOAP to REST" themselves.

The only time customer action is needed is if they also have:

  • custom integrations using the Marketo SOAP API, or
  • an older Salesforce sync authentication setup that needs to be updated to OAuth 2.0 based on Salesforce/Marketo authentication requirements.
  • review any custom LaunchPoint or external integrations separately from the native CRM sync, because those are the items most likely to be impacted

3 replies

BlaneMcMichen-1
Adobe Employee
BlaneMcMichen-1Adobe EmployeeAccepted solution
Adobe Employee
July 9, 2026

No action is required for the native Salesforce Sync itself just because of the Marketo SOAP API retirement.

That retirement is aimed at customer-built or third-party integrations that call Marketo's SOAP API. The native Salesforce Sync is a separate managed CRM sync capability in Marketo Engage, and Adobe continues to support it. In fact, Adobe's Salesforce sync documentation shows the native sync using its own supported authentication flow, including OAuth 2.0 for Salesforce sync operations. For newer subscribers, OAuth support for Salesforce CRM syncing has been available by default, and existing subscribers can enable it as needed. 2021 Log in Using OAuth 2.0

So, if a customer is only using the native Marketo ↔ Salesforce sync, they do not need to "migrate the sync from SOAP to REST" themselves.

The only time customer action is needed is if they also have:

  • custom integrations using the Marketo SOAP API, or
  • an older Salesforce sync authentication setup that needs to be updated to OAuth 2.0 based on Salesforce/Marketo authentication requirements.
  • review any custom LaunchPoint or external integrations separately from the native CRM sync, because those are the items most likely to be impacted
SanfordWhiteman
SanfordWhiteman
Level 10
July 9, 2026

Are you talking about the SFDC SOAP API or the Marketo SOAP API?

 

The SFDC SOAP API is not being retired. (I’ve seen this FUD going around a bit lately.) Only the specific login() SFDC SOAP API method is being retired because of the possibility of session hijacking. The SFDC SOAP API as a whole is not going away.

 

The Marketo SOAP API is retired but is not used by the Marketo-SFDC Sync.

P
PavelIv1Author
Level 2
July 10, 2026

Thank you ​@SanfordWhiteman.

We got the email from Salesforce about the login() SFDC SOAP API with our Marketo ID and this opened up the conversation about the whole SFDC/Marketo integration, which in turn got me confused and I decided to ask here to understand better. Which I do now, thanks to you and ​@BlaneMcMichen-1.

    BlaneMcMichen-1
    Adobe Employee
    BlaneMcMichen-1Adobe Employee
    Adobe Employee
    July 9, 2026

    I am talking about the Marketo SOAP API being retired and that the native integration to Salesforce is being managed by Adobe, so that is out of scope for the concerns ​@PavelIv1 has raised.

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    July 10, 2026

    Right, I was asking ​@PavelIv1.

      Terms & ConditionsAccessibility statement

      Loading footer...