Black Nerd Problems · Media & Publishing
Migrating 9,000+ posts without losing a decade of editorial history
- Build
- Connect
The situation
Black Nerd Problems is built on a decade of archived editorial content: articles, podcast episodes with embedded audio and video, and media features spread across a wide category taxonomy. The brief was a full platform rebuild on WordPress, standing up a membership and monetization layer, ticketed events, and a hardened hosting foundation, while migrating an archive of over 9,000 posts onto the new architecture without breaking the editorial history that gives the publication its identity. At that volume, a content migration is not a plugin-run-once job. It is an exercise in preserving block-level structure across thousands of individually authored posts, each carrying its own mix of embeds, images, and formatting quirks accumulated across years of different editors and different eras of WordPress itself.
What we found
Once the archive moved, the failure modes were exactly the kind that do not announce themselves during development. They surface post by post, on close inspection. Heading structure collapsed and paragraphs merged where the import process did not preserve block-level formatting exactly. In-content images went missing on affected posts. Video and social embeds broke on podcast and media posts, because embeds depend on the exact shortcode or block markup surviving the move unchanged, and at this volume some inevitably did not. Spot-checking a sample of the archive would have missed most of this. The only way to find failures that are invisible until you open the individual post is to open every post.
What we did
Rebuilt the platform on WordPress with MemberPress Pro and Stripe as the monetization core: gated content, subscriber tiers, and subscription billing, wired and tested before any content migration began. Added Ticket Tailor for ticketed event sales, Fluent Forms Pro and Mailchimp for lead capture and audience email, and a WP Engine, WP Rocket, and Yoast foundation built specifically to protect page speed and search equity through the move. Migrated the full archive, over 9,000 posts across a wide category taxonomy including podcast and media posts carrying embedded audio, video, and social content, onto the new architecture. Then ran a full QA pass organized by content category rather than by post, so progress and completion could be tracked systematically instead of relying on a general sense that the migration went fine.
Result
A production platform running membership, payments, and ticketed events as first-class systems, not bolted on after launch. A 9,000+ post archive migrated and QA-verified category by category, with structural and embed failures found and fixed rather than assumed away. The categories worked through the QA pass came back clean; what remains is finishing the rest of the archive with the same process.
Stack
WordPressMemberPress ProStripeTicket TailorFluent Forms ProMailchimpWP Engine
Have something like this?
A description of the problem is more useful than a list of requirements.