Proven Platform Migration Service: Zero-Downtime RCP to MemberPress for 90,000+ Users

Platform migration is one of the most complex operations you can run on an active membership website. The risks are real: lost subscriptions, billing disruptions, and members who notice. When a client came to TechCreative needing to move from Restrict Content Pro (RCP) to MemberPress, we were not just moving data — we were keeping a live business running without pausing it for a single minute.

This case study covers the full platform migration we performed for a membership site with over 90,000 registered users, 14,000+ active Stripe subscriptions, and payment transactions processing every few minutes throughout the day.

✓ Zero subscription losses | ✓ Zero billing disruptions | ✓ Zero maintenance mode downtime

The Challenge: Migrating a Live Membership Platform Without Taking It Down

The conventional advice for a major platform migration is to put the site in maintenance mode, move everything, test it, and bring it back online. That approach works fine for low-traffic sites. It does not work when Stripe is processing renewals continuously.

Putting this site in maintenance mode — even briefly — would have meant:

Blocking new member signups during the window
Creating potential Stripe webhook failures
Risking SEO impact from extended downtime
Disrupting an audience of 90,000 members who expected everything to work

We built a plan that kept the site fully operational throughout the entire process.

Why We Built a Custom RCP to MemberPress Migration Plugin

There is no reliable off-the-shelf tool that handles a full RCP-to-MemberPress platform migration with complete transaction history, live Stripe continuity, and proper shortcode replacement. We evaluated what was available and built our own solution.

The plugin is modular by design. With modifications, the same codebase can be adapted to migrate from:

The migration target can also be adjusted. While we prefer MemberPress — and we explain why below — the plugin can be adapted to migrate to Paid Memberships Pro or another platform if the project requires it.

Our Platform Migration Service: The Complete Process

Here is the exact sequence we followed for this platform migration service engagement, step by step.

Step 1: Recreate All Subscriptions via WP-CLI

Before touching anything on the live site, we used WordPress CLI (WP-CLI) to recreate all subscription records from RCP inside MemberPress.

15,000 active subscriptions recreated
10,000 expired subscriptions imported for complete member history
Total processing time: a few minutes

WP-CLI allowed this to run as a background process with no effect on site performance. Stripe kept processing payments. Members kept accessing content. The site did not know we were doing anything. At this stage, MemberPress held all subscription data — but RCP was still controlling access.

Step 2: Import Full Transaction History into MemberPress

A migration that loses billing history is not finished. Members would log into their accounts and find an empty payment history — that is not acceptable.

In Step 2, we attached every transaction record from RCP to the corresponding MemberPress subscription. For every member, this meant:

Complete billing history visible from day one on the new platform
Accurate payment dates, amounts, and subscription cycle data
A billing page that looked exactly as it should — fully populated

Step 3: Replace RCP Shortcodes with a Single MemberPress Partial Rule

RCP protects content through shortcodes embedded inside posts and pages. MemberPress uses an access rules engine. Replacing shortcodes one-by-one across hundreds of pages would have been slow, error-prone, and a maintenance problem for years to come.

Our approach: a single MemberPress partial rule that covered every membership level in one configuration.

When the site admin adds a new membership level in the future, they do not need to update every shortcode or manage multiple MemberPress rules. One partial rule handles the entire site automatically.

After setting up the rule, we systematically replaced every RCP shortcode across the site. Content protection was now running on MemberPress.

Step 4: Switch the Login Form and My Account Page

With subscriptions, transactions, and content protection all migrated, the remaining user-facing elements needed updating:

Login form: RCP shortcode replaced with the MemberPress equivalent
My Account page: RCP account shortcode replaced with the MemberPress shortcode

Small changes — but critical. The member experience had to be seamless the moment MemberPress became the active system.

Step 5: Reconcile Stripe Data Against MemberPress Records

Before signing off, we ran a full reconciliation between Stripe and MemberPress. Every active Stripe subscription needed a matching record on the platform.

What we found: A single subscription was missing. The reason: this subscription had been created during the migration window itself — a new member signed up while the migration script had already run. It was never captured.

The fix: we manually created one subscription object and one transaction record in MemberPress. Everything else was a perfect match. The migration was complete.

Solving the PDF Protection Problem on Nginx

The client sold PDFs as part of their membership offering. Their server runs Nginx — and this created a specific complication.

MemberPress’s standard URI-based file protection rules are designed for Apache. On Nginx, those rules do not work as expected without server-level configuration changes that are not always practical.

The problem was not new to the platform migration — under RCP, the PDFs had no real protection either. A logged-in member with an active subscription could share the direct download link, and anyone could access the file without being authenticated.

We built a custom PDF proxy add-on for MemberPress that:

Intercepts all PDF download requests before they reach the file system
Checks whether the requesting user has an active MemberPress membership
Serves the file only if access is confirmed
Works on Nginx without requiring changes to server configuration

PDF protection is now enforced at the application level, tied directly to MemberPress membership status.

Why TechCreative Recommends MemberPress

We are often asked why we default to MemberPress when Paid Memberships Pro offers comparable functionality — including a free tier.

The answer is straightforward: we have run fewer problems with MemberPress.

MemberPress costs more than most alternatives. The annual license is higher, and that is a real consideration for clients on tight budgets. But for a site running 90,000 users and 14,000+ active billing subscriptions, we reach for the tool we trust most, not the cheapest option available.

PMPro is a solid platform and we do use it for specific projects. But when the stakes are high — active memberships, continuous billing, large user bases — MemberPress is our go-to.

Migration Results

Metric	Result
Active subscriptions preserved	✓ 100% — zero losses
Full transaction history migrated	✓ All records visible in MemberPress
Site downtime	✓ Zero
Maintenance mode used	✓ Never
Stripe reconciliation gap	1 subscription created mid-migration, manually resolved
PDF file protection on Nginx	✓ Custom proxy add-on deployed

Need a Platform Migration Service for Your Membership Site?

If you are running on Restrict Content Pro, S2 Members, Paid Memberships Pro, or another platform and need to migrate without losing subscriptions, billing history, or uptime — this is exactly what TechCreative does.

Our platform migration service is built around one principle: your members should never know the migration happened.