Ready to migrate your site from Memberstack 1.0 to 2.0? This article will guide you through what's needed. If you do NOT have any paying members, please see this article instead.
To be 100% upfront, this is not a "quick" process and there is a risk of things breaking along the way. You'll want to sit down with your team and a calendar to map out your migration from start to finish.
Along those same lines, if your current site is working well and you don't need any of the functionality 2.0 provides you are welcome to stay on Memberstack 1.0 (if it ain't broke don't fix it, and all that).
We've designed this process to optimize for the following things...
- Super low impact for your members (they should never know).
- Avoid churn (due to SCA, notifications, etc.).
- A situation where someone cancels, creates an account, upgrades, etc. during a migration.
Note: All Membership IDs will be changed to Plan IDs and all third-party tools using membership ids would need to be updated to plan IDs. This includes all zaps. We also suggest disabling any triggers that fire when a subscription has been updated otherwise, your zap will fire for every imported member.
Create a new account with Memberstack 2.0. (1.0 and 2.0 accounts are 100% independent of each other.)
- Follow these instructions to manage 1.0 and 2.0 header scripts. This will let you set up 2.0 on your 1.0 site.
- Use our handy “plan import tool” to import your paid memberships from Stripe.
- Manually recreate your free memberships as free plans in 2.0.
- Once your plans are in, you’ll need to configure your redirects, gated content, and other plan settings.
- Next, you'll want to recreate your custom fields in 2.0. Custom fields have not changed. As long as your 2.0 IDs match your 1.0 IDs you won't need to update your site.
- We recommend migrating your site 1:1 and then adding additional functionality like email verification, multiple memberships, social logins (coming soon), etc. .
- Add or update the following elements. Most attributes are the same, but some have changed. You can keep your old attributes in place without conflict since 1.0 is unaware of 2.0's attributes and vice versa.
- If you want to use our pre-build modals…
- Login modal → data-ms-modal=”login”
- Signup modal → data-ms-modal=”signup”
- Forgot Password modal → data-ms-modal=”forgot-password”
- Profile modal → data-ms-modal=”profile”
- If you want to build your own UI in Webflow then.
- Confirm your custom login form is using the latest attributes.
- Confirm that your custom signup form is using the latest attributes.
- Build a custom forgot password flow.
- Update your custom profile forms.
- Paid plans → data-ms-price:update="PRICE ID"
- Free plans → data-ms-plan:add="PLAN ID"
- Attributes to show/hide content → data-ms-content="members"
- Logout links are now → data-ms-action="logout"
- Dynamically link to members-only content (new)
- Follow these steps to make site content more secure.
- If you want to use our pre-build modals…
- If you have any custom code, you’ll need to update a few things to get it working with 2.0. Convert 1.0 front-end API code to 2.0 DOM code.
- Upgrade your Memberstack account. If you already have a 1.0 plan then you can follow this guide to transfer over your subscription.
- Set up your live mode and test mode domains. Your live mode domain should be the same domain members will use after migration. Probably your 1.0 domain.
- Schedule downtime on your website & turn your password protection page into a “scheduled maintenance” page. Here's a cloneable to start from.
- (Optional) Contact Support to schedule a call with our team to help with the actual migration.
Only start this section after your site has been thoroughly tested.
- Join the call from the previous step.
- Password-protect your signup, login, and profile pages. Its important members cannot create or access their accounts during this time.
- Export members from 1.0 and Import your free and paying members into 2.0.
- Comment out the big header script from part 1, step 1 and add your new Memberstack 2.0 header script. Publish your site (with password protection still enabled).
- Test, test, and test.
- If everything works as expected → Remove password protection and proceed to the next section.
- If you need to roll back → Remove the 2.0 script and uncomment the big header script from step 1.
- If you can’t resolve the issue, remove password protection (so members can use 1.0 again) & contact Memberstack support.
- Cancel your subscription with Memberstack 1.0. You can ignore any mention of 10%.
Will the updated attributes work on my site while it is still running MS 1.0?
(Say I need to publish halfway through — will people still be able to log in/out and access their membership modals?)
One thing that seems to be missed in this checklist: You will need to update links to show/hide content on a page.
For example, `ms-hide-element` doesn't work in 2.0. It needs to be changed as per this page.
Yes and no... If there's a new attribute for 2.0 then you'll need to add the new attributes AND keep the old attribute. 1.0 will use the old and ignore the new. 2.0 will use the new and ignore the old. Does that make sense?
Alastair Budge you are correct! Thank you 🙏 I've updated the article
Please sign in to leave a comment.