Migrating from Rise
If you are moving from Rise to Rivo, there are two practical paths:
Keep existing Rise balances visible while new loyalty activity starts in Rivo
Fully move to Rivo for store credit and loyalty balances
This guide helps you choose the right path and run your cutover with less customer confusion.
Choose your migration path
Path 1: Hybrid handoff (recommended for lower-risk cutovers)
Use this path if you want to keep the customer experience stable while you transition.
In your account widget settings, you can set Gift Card / Store Credit Provider to Rise so customers can still see their Rise balance during the transition period.
At the same time, new loyalty activity can run in Rivo.
Best for:
Stores that want to avoid a hard switchover
Teams that want to phase migration by campaign or customer segment
Merchants with meaningful remaining Rise balance liability
Path 2: Full cutover to Rivo credits and store credit
Use this path when you are ready to replace Rise completely.
With this setup, Rivo handles your loyalty balances and store credit experience in one place. This gives you full control over future earning, redemption, and customer messaging inside your Rivo program.
Best for:
Stores ready for a complete platform change
Teams that want a single loyalty and credit experience in one system
Merchants optimizing for long-term operational simplicity
What is and is not automated
Rivo currently has in-app automated migration flows for some platforms, but Rise migrations are generally handled through a hybrid setup and/or CSV workflow.
For Rise specifically:
There is no one-click Rise import flow in the migration wizard
You should plan migration operations around manual cutover steps and CSV imports when needed
CSV options for historical data
Use CSV imports when you need to move historical balances or transaction history.
If you need to import customer balances and profile loyalty fields in bulk, use:
Using CSV files to manage Loyalty data in bulkIf you need full historical points or credits activity, use:
Import Historical Points or Credits Transactions
Tip: define your CSV scope before importing (balances only vs full history) so reporting and customer timelines stay consistent with your migration goal.
Recommended cutover checklist
Confirm whether you are doing a hybrid handoff or full cutover.
Audit outstanding Rise balance liability before launch.
Prepare and validate any CSV files for balances or historical activity.
Configure your account widget and loyalty experience in Rivo.
Announce the transition timing internally (support, lifecycle marketing, and ops).
Run launch-day validation on a small customer sample before full rollout.
Segment and communication strategy
During migration, many teams maintain a dedicated “migrated from Rise” audience so support and lifecycle campaigns can be targeted precisely.
If you use Klaviyo, create a segment for your migration cohort and apply a clear customer tag for that group in your flow setup:
Klaviyo integration
Common questions
Do we have to migrate all Rise balances on day one?
No. Many stores begin with a hybrid handoff and migrate in phases.
Can we use CSV if we only want to move balances first, then history later?
Yes. You can split your migration into stages and import data in a controlled sequence.
Which path is better for customer experience?
A hybrid handoff is usually smoother for customers when you want to avoid abrupt changes during transition.
Need a hand with your move from Rise?
Contact our team to get help planning your migration path.