Operations

Database search & replace without the risk.

Domain migrations, URL updates, protocol changes — all require database-wide search and replace. But WordPress stores serialized data, and a naive find-replace breaks serialization, corrupting options, widgets, and plugin settings. BlockForge handles serialized data correctly, creates an automatic backup before every operation, and lets you preview changes before committing.

The Challenge

One wrong replacement can break an entire site.

Serialized Data

WordPress stores arrays and objects as serialized strings in the database. These strings include character counts — change the string length without updating the count and the data becomes unreadable. Widgets disappear, plugin settings reset, theme customizations vanish. A standard SQL REPLACE breaks every serialized value it touches.

No Undo Button

A bad search-and-replace on production without a backup is catastrophic. There is no "undo" for a database UPDATE that affected 50,000 rows. If you replaced the wrong string or forgot about edge cases, the only recovery path is restoring from backup — assuming you have one that is recent enough.

Migration Complexity

HTTP to HTTPS, domain changes, staging to production, subdirectory to root — each migration scenario requires careful, comprehensive replacement. Miss one table and you have mixed content warnings. Replace in the wrong order and URLs break. The complexity multiplies when multiple replacement patterns are needed.

How It Works

Safe replacements with preview and automatic backup

BlockForge provides a search-and-replace interface that handles WordPress serialized data correctly. Enter your search and replace terms, select which database tables to include, and run a dry-run preview first. The preview shows exactly how many rows will be affected in each table — before anything changes. When you are ready, BlockForge creates an automatic backup, performs the replacement with full serialization support, and logs the operation for your records.

  • Serialized data support — correctly updates character counts in serialized strings
  • Automatic pre-operation backup for safe rollback if needed
  • Dry-run preview showing affected rows per table before committing
  • Table selection — choose exactly which tables to include in the operation
  • Regex support for advanced pattern matching and replacements
  • Case-sensitive option for precise control over matching behavior
Search & Replace DRY RUN
http://acme-corp.com
https://acme-corp.com
Dry Run Results
wp_posts 247 rows
wp_postmeta 89 rows
wp_options 34 rows
Total affected 370 rows
acme-corp.com · 12 tables selected Backup before replace
Operation History

http:// → https://

2026-03-09 10:15 UTC · John · 370 rows

COMPLETED

staging.acme.com → acme-corp.com

2026-03-07 16:42 UTC · Sarah · 1,204 rows

COMPLETED

/blog/ → /news/

2026-03-05 09:30 UTC · John · 58 rows

COMPLETED

Full history of every operation

Every search-and-replace operation is permanently logged with the search term, replace term, affected tables, row counts, and the user who performed it. Review past operations to verify that migrations were applied correctly. Use the history to audit changes during compliance reviews or to understand the sequence of modifications made during a complex migration project.

Key Capabilities

Everything you need for safe database replacements

Serialized Data Support

WordPress stores complex data structures as serialized PHP strings with embedded character counts. BlockForge correctly unserializes data, performs the replacement, and re-serializes with updated counts. Widgets, theme mods, plugin options, and custom data all survive the replacement intact.

Auto-Backup

Every search-and-replace operation automatically creates a database backup before execution. If the replacement produces unexpected results, restore the backup with one click. No manual pre-backup steps, no remembering to create a snapshot — BlockForge handles it automatically.

Dry-Run Preview

Before committing any changes, run a dry-run that scans every selected table and reports exactly how many rows would be affected. Review the numbers, verify the scope is correct, and only proceed when you are confident. The dry-run touches nothing — it is a read-only operation.

Table Selection

Choose exactly which database tables to include in the search-and-replace operation. Skip tables that should not be modified, target only content tables for URL changes, or include all tables for a complete domain migration. Full control over scope reduces risk.

Regex Support

For advanced replacement scenarios, use regular expressions to match complex patterns. Replace URL schemes regardless of domain, normalize formatting inconsistencies, or handle pattern-based migrations that simple string replacement cannot address. Full PCRE regex syntax supported.

Operation History

Every search-and-replace operation is logged with the search term, replace term, tables affected, row counts, timestamp, and the user who performed it. Review past operations, audit changes for compliance, and track which migrations have already been applied.

Related Features

Safe search & replace. Every time.

Handle domain migrations, URL updates, and content changes without risking your production data.