NOTE: This article contains steps to take if you are already running a live site with MemberMouse and are moving your site to a new hosting provider or server. If you are migrating from a staging site to a live site, please read the article Migrating from a Staging Site.
Prior to migrating your site, you should upgrade the MemberMouse plugin on your live site to the latest version. This will ensure that there's no discrepancy between the tables when you go to migrate to your new server.
For general information about moving a site from one server to another, see this documentation provided by WordPress:
Below we'll add some specific details you'll want to keep in mind specifically related to MemberMouse.
When you're ready to go live on your new server, the following steps should be done all at once and at a time when you can take your live site offline until the migration is completed:
1. Backup your database of your live site in case you need to roll back for whatever reason.
2. EXTREMELY IMPORTANT: Put the live site into maintenance mode and delete the MemberMouse plugin. To be extra careful you should also shutdown the database on the live site. This will ensure that no database changes will happen in the process of migrating which would cause the databases to be out of sync.
3. Do a database dump from your live site and move all tables over to your new server. Generally speaking, all database tables would be copied over in a migration. For your information: All MemberMouse data is stored in tables prefixed with
mm_ . Core pages are linked to WordPress pages and WordPress content is stored in the
wp_posts table. All MemberMouse members are tied to users in the
wp_usermeta tables and some MemberMouse configuration settings are stored in the
wp_options table. All MemberMouse options are prefixed with mm- .
4. After copying all tables onto the new server, visit your new site and make sure everything works as expected.
Special Note about Existing Subscriptions
If you have existing subscriptions and you're using a card-on-file payment service such as Stripe, Braintree or Authorize.net CIM then this section applies to you. If you're using an offsite payment service such as PayPal or a non-card-on-file payment service such as Authorize.net then you can disregard this.
If you have existing subscriptions being processed by a card-on-file solution such as Stripe, Braintree or Authorize.net CIM this means that MemberMouse is handling the billing for these subscriptions. Existing subscriptions are tied to a specific MemberMouse license. When you migrate to a new site you want to continue to use the same license. If you're migrating to a different URL simply change the URL associated with your existing license instead of creating a new license.
IMPORTANT: If you have existing subscriptions for real customers make sure you understand everything clearly above prior to taking action. Failure to take the proper steps outlined above could result in your customers being unable to be billed going forward. If you have any questions please contact our support team.
You can see a list of all your licenses on your My Account page on membermouse.com.