Xoxoday Plum communicates end-of-life timelines well in advance, ensuring administrators and IT teams can transition to newer versions with zero disruption to rewards, gifting, and incentive workflows.
How Xoxoday Plum’s version lifecycle works
Xoxoday Plum operates on a continuous delivery model, releasing regular updates that introduce new capabilities, performance improvements, and security patches. Each major version enters a defined support window the moment it is generally available, and that window is communicated clearly so organizations can plan accordingly. The lifecycle follows three broad stages: active development, maintenance support, and end-of-life. During active development, a version receives full feature updates alongside bug fixes and security releases. In the maintenance phase, the focus shifts to security patches and critical fixes, keeping the environment stable while engineering effort moves toward the next generation. End-of-life marks the point at which a version no longer receives any updates.End-of-life notice and transition planning
Xoxoday Plum notifies administrators of an approaching end-of-life date with sufficient lead time — typically months, not weeks — before support officially ends. This gives IT teams integrated with enterprise HRIS platforms like Workday, SAP SuccessFactors, or Darwinbox the runway needed to validate compatibility, update API connections, and re-test any custom workflows before migrating. For example, an organization that has built an automated milestone-rewards flow connected to Darwinbox will receive advance notice and migration guidance before their current version reaches EOL, ensuring the integration continues without gaps in reward delivery.Security and compliance continuity
Maintaining an up-to-date version of Xoxoday Plum is directly tied to its compliance posture. Xoxoday Plum holds SOC 2 Type II and ISO 27001 certifications, and continued compliance depends on running versions that receive active security patches. Once a version reaches end-of-life, it no longer qualifies for coverage under these frameworks, making timely upgrades a compliance requirement, not just a best practice. Xoxoday Plum’s security team works alongside its product team to ensure that the migration path to newer versions preserves all existing configurations, reward catalogs, user roles, and approval workflows. Administrators are not expected to rebuild from scratch when a version transitions out of support.What to expect during a version transition
When an EOL date is announced, Xoxoday Plum provides release notes, a migration checklist, and direct support channels for enterprise accounts. Teams using communication integrations such as Slack or Microsoft Teams for reward notifications will find that notification templates and bot configurations carry forward automatically in supported upgrade paths. Xoxoday Plum’s support team remains available throughout the transition window to address compatibility questions, test new configurations, and confirm that the upgraded environment meets organizational requirements before the legacy version is decommissioned. Learn more: Xoxoday Plum Help Centre — GeneralSecurity certifications and compliance standards
Learn how Xoxoday Plum maintains SOC 2 Type II and ISO 27001 compliance across its infrastructure and release cycles.
Data retention and deletion policy
Understand how Xoxoday Plum handles data storage, retention windows, and deletion requests across version upgrades.