1. Notify Inveterate & Request Export
Contact previous vendor to inform them of your plan to migrate off their platform.
Request a full CSV export of all membership data, including the paymentMethodId or subscription contract (required to continue billing paid members without interruption).
2. Prepare CSV Files for Rivo
Provide Rivo with a separate CSV file per membership tier, aligned with the Rivo import template.
Paid Tiers – Required Columns
customerId
firstName
lastName
creditBalance
tierId
tierName
status
nextBillingDate
paymentMethodId (mandatory for continued billing)
joinedAt
Free Tiers – Required Columns
customerId
firstName
lastName
creditBalance
tierId
tierName
status
joinedAt
Also include your target Rivo launch date.
3. Complete the Tier Mapping File
Fill out the mapping sheet that indicates:
Inveterate Tier ID → Rivo Tier Name
This ensures every member is correctly placed into the intended tier during migration.
4. Provide Inveterate API Key to Rivo
Share your Inveterate API key with Rivo so we can pull ongoing updates (membership status changes, credit adjustments, cancellations, etc.) after the initial import.
This prevents the need for a second “delta migration.”
Rivo will notify you once members are migrated
5. Configure Membership Plans in Rivo
Confirm pricing, billing frequency, benefits, and perks for each tier.
Validate that all tiers reflect your intended membership structure.
6. Update Theme Touchpoints
Review your storefront and update all locations where memberships are purchased or referenced.
Replace legacy Inveterate:
Variant IDs
Selling Plan IDs
with the new Rivo membership product + selling plan, which you can find on the memberships dashboard
7. Configure Integrations
Ensure any connected platforms are correctly wired to Rivo:
Email (Klaviyo, Attentive, etc.)
SMS
Reviews
Subscriptions (Loop, Recharge, Ordergroove)
Any other loyalty/CRM tooling
8. Update All Membership Flows
Duplicate and update workflows in your marketing tools to use Rivo’s event triggers and variables:
Welcome flows
Renewal reminders
Expiration warnings
Failed renewal journeys
Perks/benefits unlock sequences
9. Set Failed Payment Retry Rules
Configure your failed payment retry logic inside Rivo.
Match your current retry strategy or optimize your rules as part of the migration.
10. Configure Default Tier Enrollment
If applicable:
Set your default tier for new customers or non-members entering the program.
11. Confirm Billing Cutover
Rivo will notify you once recurring billing for paid members has fully transitioned.
Verify that all expected renewals are processing correctly on Rivo.
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.
Their documentation link goes here once provided by the merchant.