Skip to main content

July 2025 - Impact Guide

For Account Admins, learn more about upcoming changes to the platform

Ian Remington avatar
Written by Ian Remington
Updated yesterday

About this Guide

This guide is designed to help Crelate System Administrators understand the potential user impact of an upcoming release of Crelate. The guide provides additional insights that Crelate System Administrators should be aware of. Crelate provides this guide ahead of scheduled releases to allow Crelate System Administrators time to prepare for and take advantage of new or changing system capabilities.

About Crelate Upgrades

All upgrades to Crelate are automatic, benefit all users and typically require no user action. However, not all system upgrades are on by default. System Administrators may need to opt-in or opt-out of some new functionality. We know change can be disruptive and we work hard to ensure System Administrators have the flexibility to control when new features are available to their teams.


AI Company Auto-Complete – New

Impact

When creating a Company, Crelate's AI will provide auto-complete suggestions. Selecting an option will create the company using the name and will also populate the domain field.

Severity

Medium

Applies To

All Users

Action Required

None, however Company records created prior to this change will not have the domain field populated.

SKU

All

Company records now include a dedicated domain field to improve data integrity and reduce duplicates. This field must be unique across your dataset and is used to link each company to enriched data within the platform.


Chrome Extension Update – Improved

Impact

We’re rolling out a new version of the Crelate Chrome Extension that brings improved performance and enhanced stability.

Severity

Low

Applies To

All users using the Crelate Chrome Extension

Action Required

Ensure you are on the most up to date version of the Chrome Extension

SKU

All

Most browsers update extensions automatically, but if not, please check and manually update to the latest version to take advantage of the improvements.


Outlook Add-In – Update to Supported Office Versions – Changed

Impact

Support for Office 2016 and Office 2019 will end on October 14, 2025 and there will be no extension and no extended security updates.

Severity

Medium

Applies To

Organizations still using Office 2016 or Office 2019.

Action Required

To keep using the Outlook Add-In, make sure you upgrade to the most recent version of Office 365 before October 14, 2025.

SKU

All

We are in the process of re-certifying our Outlook Add-on and adding support for new Microsoft APIs. During this effort we are dropping support the sunsetting versions of Outlook.


Job Portal v1 Deprecation – Changed

Impact

We’re officially retiring Job Portal v1 on January 1, 2026. After this date, it will no longer be supported.

Severity

High

Applies To

Organizations using Job Portal v1

Action Required

Ensure you're upgraded to the new Job Portal and see here for instructions if this is necessary for you.

SKU

All

To ensure the best experience, we’re consolidating support and development around Job Portal v2, which includes all the same functionality as v1—plus ongoing enhancements.


Public API Performance Protection Throttling – ACTION REQUIRED

Impact

Developers make high-volume calls to the Crelate API, or make many calls using inefficient queries, may experience throttling.

Severity

Medium

Applies To

All Public API users

Action Required

  • Update your code to be efficient. Do not repeatedly download the entire dataset when deltas are more efficient.

  • Select only the columns you need when retrieving data.

  • Handling throttling error codes and have your code “back off” its requests.

  • Make smart use of caching. Example tags, country codes, picklist values do not change frequently.

SKU

All

To protect all users from bad actors and performance issues, we will be implementing throttling of the Public API. Most users should be unaffected, however if your code is inefficient and negatively impacts the performance of others you may see throttling errors returned. Developers should handle throttle errors and update their code to slow the pace of requests or to be more efficient.


What's Next?

Looking for more on our release? Check out a sneak peek of what's to come!

Did this answer your question?