At Thrive, we’re constantly evolving — improving our platform to deliver better performance, stronger security, and richer learning experiences.
As part of this commitment, some features are periodically replaced or retired to make way for newer, more efficient functionality. Our goal is to balance innovation with stability, ensuring customers always benefit from progress without unexpected disruption.
This page explains how Thrive manages the lifecycle of features, including how and when older features are deprecated and removed from service.
Our goal is to ensure all customers have ample notice and support when transitions occur, so your teams can plan and migrate smoothly without disruption.
Our Commitment
We understand that changes to core functionality can impact your workflows, integrations, and training materials. We will ensure we consult with our account director and learning impact managers during this process to ensure the suggestions are fit for purpose.
That’s why we aim to:
Provide a minimum of 6 months’ notice before a feature is fully retired.
Where possible, we will offer 3 months of dual running where both the old and new versions are available.
Follow this with a 3-month deprecation period during which the old feature remains operational but receives no further enhancements.
In rare cases, we may need to shorten this timeline and not provide an alternative solution for a deprecated feature. If that happens, we’ll communicate transparently through the notification channels listed below.
Deprecation Stages
Stage | Timing | Description |
|---|---|---|
Stage 1 — Announcement | Day 0 (Initial Notice) | A formal announcement is made that a feature will be replaced or retired. This initial notice is critical for customer planning. |
Stage 2 — Dual Running Period | Months 0–3 | Both the existing and the replacement features are available concurrently. This allows for a controlled, self-paced migration. |
Stage 3 — Deprecation Period | Months 3–6 | The older feature remains functional but enters a maintenance-only state. No new improvements or feature enhancements are introduced. |
Stage 4 — Sunset | After 6 Months | The older feature is permanently removed from service. All infrastructure supporting it is decommissioned. |
Notification Channels
When a feature is scheduled for deprecation, we’ll make sure you’re informed through multiple channels:
Posts on Thrive Tribe (our customer community).
Direct communication from your Account Director.
Each notification will clearly outline:
The affected feature(s).
The reason for deprecation.
Key dates (dual running start, deprecation start, and sunset date).
Migration or replacement guidance.
Example Deprecation Timeline
Announcement Date | Dual Running (3 Months) | Deprecation (3 Months) | Sunset Date (Retired) |
|---|---|---|---|
1st November 2025 | Nov 2025 – Jan 2026 | Feb 2026 – Apr 2026 | 1st May 2026 |
During the dual running period, both versions are available. After this, the old version enters deprecation and is finally removed at the sunset date.
Support During Transition
Throughout the 6-month lifecycle:
We’ll proavide clear migration guides, FAQs, and examples to help you transition smoothly.
Our support team and account contacts will be available to assist with planning and implementation.
Any feedback during the dual running period helps us refine the new feature before full rollout.