SOAP API v41.0 Retirement — HubSpot Integration Package v3.0.1

Dear HubSpot Support Team,

I am writing regarding our HubSpot-Salesforce integration and a potential risk we have identified related to the Salesforce SOAP API version retirement announcement made in April 2026.

Our Current Setup:
• Package: HubSpot Integration v3.0.1 (installed May 8, 2023)
• SOAP data calls: 2,209 rows running on API v41.0
• Objects synced: Lead, Contact, Opportunity, Campaign, CampaignMember
• Evidence Period: June–August 2026

We have the following questions:

  1. Package Version
    Is v3.0.1 the latest version of the HubSpot-Salesforce connector package? If not, how do we upgrade safely without breaking our current sync?

  2. SOAP API Version
    Our API usage report confirms SOAP data calls are running on API v41.0. What SOAP API version does the latest HubSpot connector package use?

  3. Retirement Risk
    Salesforce has announced SOAP API versions v31.0–v40.0 will be retired by Summer 2028. Are we at risk? Will upgrading the package resolve the v41.0 issue?

  4. Upgrade Path
    What is the recommended upgrade path from v3.0.1 to the latest package version without disrupting our current data sync?

  5. Objects Synced
    Will all currently synced objects (Lead etc…) continue to sync correctly after the upgrade?

We would appreciate your earliest response as we want to plan and complete the upgrade well before the Summer 2028 deadline.

Thank you for your support.

Best regards

Hi @SumaSreejith and welcome, it’s a pleasure to have you here!

Thank you for reaching out to the HubSpot Community and for providing the package version, API usage details, and affected objects.

We’re reviewing this with the team responsible for the HubSpot-Salesforce connector to confirm the next steps.

For information, here is an article about this: HubSpot-Salesforce Connector Package v3.0.1 | Frequently Asked Questions

Thanks so much,

Bérangère

Hi @SumaSreejith, getting back to you on this!

1. Package Version: v3.0.1 may not be the latest. You can check for updates in your Salesforce org under Setup → Installed Packages, if an update is available, an “Upgrade” link will appear there.

2. SOAP API Version: I’m still checking on this

3. Retirement Risk: Salesforce has announced that SOAP API versions v31.0–v40.0 will be retired by Summer 2028. Since your usage is on v41.0, you are above the announced retirement cutoff and not immediately at risk. We recommend monitoring Salesforce’s API retirement announcements for any future expansions. If you need guidance on upgrading the API version used by the connector, please let us know.

4. Upgrade Path: Upgrading the managed package via Salesforce’s Installed Packages UI should not disrupt your existing sync configuration. We recommend reviewing the release notes for any version you upgrade to.

5. Objects Synced: All currently synced objects (Lead, Contact, Opportunity, Campaign, CampaignMember) are standard syncs supported by the integration and are expected to continue working after a package upgrade.

I hope this helps!

Have a lovely weekend!

Bérangère

This post was created with the assistance of AI tools

Hi @SumaSreejith, Happy Monday!

Getting back to you on this, regarding point number 2, the SOAP API Version, we use version 41.

I hope this helps!

Let us know if you have additional questions,

Thanks and wishing you a wonderful day!

Bérangère

Dear @Berangere ,

Thank you for your support!

I would like to check below point.

1. Package Version: v3.0.1 may not be the latest. You can check for updates in your Salesforce org under Setup → Installed Packages, if an update is available, an “Upgrade” link will appear there. —>Could you please clarify whether this link will only appear closer to or after the Summer '27 release ? Any guidance on the expected timeline would be greatly appreciated.

2. SOAP API Version: Thank you for confirming that SOAP API v41.0 is used.

Thanks in advance

Regards !

Hi @SumaSreejith and thanks for following up!

Regarding the package version, I checked internally and we are not longer requiring the package during integration install and even recommend uninstalling it for those who still have it.

This package does not take any part in the sync process anymore.

I hope this helps and let us know if you have additional questions!

Thanks and enjoy the day!

Bérangère