by jrtwebsolutions 0 (0 reviews)

JRT Database and File Migrator

Name: JRT Database and File Migrator
Author: jrtwebsolutions

Move WordPress databases and files between environments with safe find & replace, exports, imports, and site-to-site transfers.

JRT Database and File Migrator ranks #67,200 among WordPress.org plugins with 0+ active installations, is #4,276 of 4,943 in the Utilities & Tools category, and was last updated Aug 5, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7.0.4 (Current: 7.1)

v1.0.0 Current Version v1.0.0

Updated 1 month ago Last Update on 05 Aug, 2026

Refreshed 10 hours ago Last Refreshed on

#4,276 of 4,943 in Utilities & Tools

View on WordPress.org

Rank

#67,200

— No change

Active Installs

-100%

KW Avg Position

N/A

— No change

Downloads

138

+3 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 0%

0+ 10+

51,212

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 10 more installs to reach 10+

Rank Changes

Current #67,200

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.0.0
Last Updated: Aug 05, 2026
Requires WP: 6.2+
Tested Up To: 7.0.4
PHP Version: 7.4 or higher
Author: jrtwebsolutions

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

database export find & replace import migration

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,756

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,007

Elementor Website Builder - more than just a page builder

10M+ installs

Contact Form 7

10M+ installs

All-in-One WP Migration and Backup

5M+ installs

#10

UpdraftPlus: WP Backup & Migration Plugin

3M+ installs

#15

WPCode - Insert Headers and Footers + Custom Code Snippets - WordPress Code Manager

View all Utilities-and-tools plugins

Frequently Asked Questions

Common questions about JRT Database and File Migrator

No data leaves your site unless you opt in to Freemius usage tracking or activate a Pro licence.

Two strategies, chosen per value. Where the payload can be parsed, it is unserialized with object instantiation disabled, walked recursively, and re-serialized with corrected byte lengths. Where it cannot — for example when it contains objects of classes this site does not have — a token rewriter edits the s:N:"..." segments in place without ever instantiating anything, so PHP object injection is not possible either way. If a payload cannot be handled safely by either strategy it is left untouched. The plugin will not corrupt data to force a replacement.

Media uploads, themes and plugins, each selectable independently. Files are compared by size and modification time, so re-running a transfer only sends what actually changed. Anything else under wp-content/ — including mu-plugins/, caches, and files at the site root such as .htaccess — is not transferred. Move those yourself if your site depends on them.

Yes, and this is the direction to use. A pull is driven entirely by the site you are sitting at: it makes outbound requests to the live server, which never needs to reach back. That means your local machine does not have to be publicly reachable, and it does not need HTTPS of its own. Pushing to a local machine from a live server is not possible without a tunnel, because the live server would have to open a connection to your desktop.

The destination reports the directory it could not write to. Give the web server write access to that directory and run the transfer again. Transferred files are given the same permissions WordPress itself uses for new files (FS_CHMOD_FILE / FS_CHMOD_DIR), so a restrictive umask on the receiving server cannot leave you with files the web server is unable to read back. My local install cannot verify the live site's certificate. Turn off "Verify TLS certificates" in Settings. This is separate from the plain-HTTP option, so switching it off does not otherwise weaken how sites connect. Leave it on in production. Transfers time out against a slow server. Raise "Remote request timeout" in Settings. A request that times out part way through cannot be retried safely, because it may already have been applied on the other side, so it ends the transfer rather than risking duplicate work.

Each site has a random 64-character connection key. Every request between sites is signed with HMAC-SHA256, has a 5-minute validity window, and replay protection. HTTPS is required by default.

Not yet. Multisite support is planned.