1. Notify Inveterate & Request Export
Contact previous vendor to inform them of your plan to migrate off their platform.
Request a full export of your membership data, including customer records, tier assignments, credits, and paid membership payment method tokens.
2. Prepare CSV Files for Rivo
Prepare your migration files so they can be imported in Rivo.
Membership enrollment CSV (for tier placement)
Include:
Membership tier name
Either customer email or customer ID
Recommended additional fields:
Enrollment start date
End date (if applicable)
Internal note / external note
Source
Scheduled cancellation date
End reason and cancellation note
Subscription contracts CSV (for paid member billing continuity)
customer email or customer ID + customer payment method token
Optional but recommended fields:
Subscription status
Next billing date
Joined date
Membership tier ID
Price
Billing interval
Currency code
3. Start the Inveterate Migration in Rivo
In Rivo, start a migration job for Inveterate and connect your Inveterate API key.
Rivo will begin importing members and credits.
4. Import Subscription Customer Payment Tokens
After members and credits are imported, upload your subscription token CSV from the CSV imports page.
This import is the checkpoint that moves the migration into contract conversion.
5. Convert Subscription Contracts
Once token import is complete, Rivo converts eligible paid members into subscription contracts.
Conversion requires valid payment method token data and matching membership tier setup.
6. Import Tier Enrollments
After subscription conversion, Rivo imports tier enrollments so member access matches their migrated plan.
7. Configure Membership Program Settings
Review and confirm tier pricing and benefits.
Confirm your cancellation policy.
Confirm default enrollment tier behavior.
Confirm your failed payment retry schedule.
8. Update Storefront and Customer Touchpoints
Replace old membership purchase links/blocks with your Rivo membership setup.
Update lifecycle messaging, reminders, and cancellation communications.
9. Understand Migration Mode During Cutover
If migration mode is enabled, automatic re-billing and related notifications are paused.
Keep migration mode on while validating imported records and contract conversion.
Disable migration mode when your team is ready for fully live billing operations.
10. Validate Data Before Going Fully Live
Confirm member counts and tier placement.
Confirm paid members have active subscription contracts where expected.
Review any failed records and re-import corrected rows if needed.
11. Complete Cutover
Confirm your first expected renewals and failed-payment handling are working in Rivo.
Confirm customer-facing messaging and support workflows are updated.
12. Sunset Inveterate
Once all data is safely migrated and billing is confirmed as fully managed by Rivo:
Rivo will notify you once it’s safe to sunset Inveterate
Follow Inveterate’s offboarding instructions to deactivate your program and stop their billing.