Hubspot v4 — Breaking Changes Checklist

7 items total3 critical~1 hour for a typical integration

Before You Upgrade

1.Read the official HubSpot API v4 release notes and migration guide thoroughly.
2.Identify all HubSpot API endpoints your integration currently uses.
3.Backup your current integration code and relevant HubSpot data.
4.Set up a staging or development environment to test the upgrade process.
5.Communicate the planned upgrade to stakeholders and affected teams.

0/2

Verify your authentication methods and token handling to ensure continued access after the upgrade.

Review and test your OAuth token refresh logic.Criticalmedium

Ensure your application correctly handles token expiration and refresh using the latest OAuth 2.0 flows.

⚠ Your application may lose access to HubSpot data if tokens are not refreshed properly.

Check the usage and validity of any private app access tokens.Mediumeasy

Private apps may have changes in their scope or token management. Ensure they are still valid and used correctly.

⚠ Private app integrations might fail due to invalid or insufficient scopes.

0/3

Identify and adapt to any changes in API endpoints, request/response formats, or deprecated functionalities.

Update any integrations using the `/properties/contacts` endpoint.Criticalmedium

The contact properties API has been updated. Existing calls might need adjustments to query or manage contact properties.

⚠ Attempts to retrieve or update contact properties may fail or return unexpected data.

Review and modify integrations that interact with the deal properties API.Highmedium

Changes in the deal properties API, including potential renames or deprecations, require careful review.

⚠ Integrations relying on specific deal property fields or endpoints might break.

Adapt to changes in how pipelines and deal stages are managed.Mediummedium

Updates to the pipeline and deal stage APIs might affect how you create, update, or retrieve pipeline information.

⚠ Your system may not be able to correctly assign deals to stages or manage pipeline configurations.

0/2

Be aware of changes in data structures, field types, or API response behaviors.

Ensure your application handles updated date-time field formats correctly.Higheasy

Date and time fields may now adhere to a stricter or different ISO 8601 format. Parsing and serialization might need adjustments.

⚠ Date/time data may be parsed incorrectly, leading to errors in reporting or data processing.

Verify that your code accounts for any changes in enum values.Mediumeasy

Enum values (e.g., for deal types, lead statuses) might have been updated, added, or deprecated.

⚠ Your application might fail when trying to use outdated or non-existent enum values.

Deprecatr AI monitors 150+ providers, maps changes to your codebase, and delivers migration checklists before your team hits a breaking change.