Announcement Notice: Migrate Your V1 Announcements

Overview

AppNavi is transitioning away from V1 Announcements. If you currently use V1 Announcements to communicate updates, guide users, or share important information within your application, review your existing configuration and plan your migration to the supported announcement experience.

Migrating your announcements helps ensure that your in-app communications continue to reach the intended audience and behave as expected.

This guide explains when to migrate, what to review before starting, how to configure and publish replacement announcements, and how to verify the results.

Important: Check the official AppNavi deprecation timeline and migration instructions for your environment before making changes. Confirm any applicable deadlines with your AppNavi administrator or support contact.

When Should You Migrate?

Migrate your V1 Announcements if you currently use them to:

Communicate product updates, announcements, or service changes.
Notify users about new features or changes to existing functionality.
Display targeted messages to specific user groups.
Share important information directly within your application.

Review all active, scheduled and reusable announcements before migrating. This helps prevent important communications from being overlooked during the transition.

What This Means

V1 Announcements will not be displayed to end users anywhere in the application on avatar side.
Users will still see them listed in your announcements dashboard, but only with the option to delete.
Users will not be able to open or preview the content of a V1 announcement after the update.

Recommended Action Before the Release

To preserve your existing announcement content, we recommend migrating them to the new V2 Announcements format:

Open the V1 announcement you want to keep.
Copy the full content.
Create a new V2 Announcement in the portal.
Paste the copied content into the new announcement editor.
Save your V2 announcement.

This ensures your important messages remain visible and accessible to users after the release.

Troubleshooting

If an announcement does not appear or behaves differently after migration:

Confirm that the replacement has been saved and published.
Review its audience, targeting, scheduling, and visibility settings.
Verify that the announcement is being tested in the correct application context.
Check whether the expected behavior is supported by the replacement functionality.
Consult the official AppNavi migration instructions or contact AppNavi support if the issue persists.

When requesting support, provide the affected announcement, the relevant configuration, the expected behavior, and the actual result.