> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clix.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Migration Overview

> Compare migration destinations and choose the right messaging platform for your team.

<Warning>
  **Clix will shut down on November 30, 2026.**

  Complete your migration before this date to continue sending notifications.
  Preserve your campaign settings and reports before the service shuts down.

  If you would like to migrate to **Notifly**, email
  [support@clix.so](mailto:support@clix.so) for migration assistance.
</Warning>

Choose a destination based on the campaigns you run today, your budget, and how much messaging infrastructure your team wants to maintain.

## Compare Your Options

The fit suggestions below are starting points for your evaluation. Each solution name links to its Clix migration guide.

| Solution | A good fit when... | Cost and effort to consider |
| - | - | - |
| **[Notifly](/migrations/notifly)** | Your team wants to manage targeted push campaigns and expand into in-app messaging or email. | Monthly plans include free push sends. Check the tier for API-triggered sends and frequency caps. [Pricing](https://notifly.tech/en/pricing). |
| [Braze](/migrations/braze) | You need complex cross-channel journeys and enterprise governance. | Request a quote based on active users, channels, and required features; plan for Canvas and data integration setup. [Pricing](https://www.braze.com/pricing). |
| [Customer.io](/migrations/customer-io) | Your lifecycle messaging revolves around identified users, events, and custom workflows. | Budget for profile volume and channel usage; plan your identity mapping and workflow rebuild. [Pricing](https://customer.io/pricing). |
| [OneSignal](/migrations/onesignal) | You want a push-focused starting point with a dashboard and room to add other channels. | Compare free-plan limits with paid-plan active-user and channel charges; confirm journey and event features. [Pricing](https://onesignal.com/pricing). |
| [Firebase Cloud Messaging](/migrations/firebase-cloud-messaging) | Your engineering team wants direct control of delivery and can own campaign logic. | FCM is no-cost, but you must budget for your backend, scheduling, audiences, suppression, and reporting. [Pricing](https://firebase.google.com/pricing). |

## A Practical Starting Point

<Tip>
  If you want to keep campaign operations accessible while watching costs,
  consider **Notifly** first. Its [campaign and journey
  tools](https://notifly.tech/en) handle targeting, automation, and reporting,
  while its published monthly plans include free push sends. Together with the
  Clix migration assistance above, this makes it a practical option to evaluate
  for your existing workflows.
</Tip>

Compare the total cost for your expected audience and channels, including the plan tier and engineering time. Confirm current pricing and feature availability with the provider before choosing.

## Plan Your Move

1. List your essential campaigns, channels, consent rules, and reporting needs.
2. Rebuild one representative campaign and test an upgraded app installation with your shortlisted provider.
3. Follow the linked migration guide, preserve Clix reports, and complete your rollout before **November 30, 2026**.