Migratico Lite

By superweby

10+ active installationsVersion 2.7.10

The simple and reliable WordPress migration plugin. Quickly backup, migrate, copy, move, or clone your site from one location to another.

Description

WordPress Migration & Backup Plugin

Migratico Lite provides a simple way to move WordPress sites, create reliable backups, or clone a site for development. With Migratico, you can easily migrate, transfer, or clone your WordPress site between domains or hosts with no downtime. Create full backups of your website, or package your entire site to download and install elsewhere with only a few steps.

At Migratico, reliability, security, and ease of use are our top priorities. Our intuitive migration wizard and real-time progress tracking make Migratico one of the most beginner-friendly backup and migration plugins on the market. You don’t have to hire a developer. Create a backup and migrate sites in just a few minutes.

Easy Site Migration, Backup, and Cloning

Migratico streamlines site migrations by packaging your website files and database into downloadable archives. Download and re-install your backup on any new WordPress location or server without dealing with complicated setups. The installer works on an empty server – no need to install WordPress first.

Fast WordPress Migrations

Migratico makes WordPress website migrations fast and stress-free. Quickly move to a new host, domain, or server. No downtime, no data loss, and no coding required.

Reliable WordPress Backups

Create complete backups of your WordPress site including database and files. Perfect for:
– Pre-update backups
– Development site copies
– Disaster recovery
– Moving to new hosting

WooCommerce Migration Support

Migratico offers reliable WooCommerce migration and backup. Easily migrate your entire online store including:
– Products and categories
– Orders and customers
– Payment settings
– Custom product data

Large Database Support

Migratico handles databases of any size with automatic timeout recovery:
– Chunk-based import prevents memory issues
– Automatic resume after PHP timeouts
– No file size limits
– Tested with databases over 1GB

Real-time Progress Tracking

Watch your migration in real-time with streaming progress updates:
– Live progress bar during installation
– Detailed status messages
– Automatic recovery from timeouts
– Up to 50 automatic resume attempts

Smart Migration Wizard

Migratico’s smart migration wizard makes transferring your website effortless:
– 4-step installation process
– Environment compatibility check
– Database connection testing
– Automatic URL rewriting
– wp-config.php updates

Clone WordPress Website

Migratico clones your entire WordPress website quickly and easily. Perfect for:
– Staging sites
– Development environments
– Testing updates
– Client demos

Key Features

  • Complete Site Export – Database and files in one package
  • Automatic ZIP Splitting – Large sites split into manageable archives
  • Real-time Progress – Live updates during installation
  • Auto-Resume – Continues after server timeouts
  • Smart URL Rewriting – Updates all URLs automatically
  • Database Connection Test – Verify settings before installation
  • Multi-language – Available in Czech, German, and English
  • No External Dependencies – Everything runs on your server
  • Security Focused – No data sent to external servers

Who Should Use Migratico?

Migratico is perfect for:
– Website Owners moving to new hosting
– Developers creating staging sites
– Agencies migrating client sites
– E-commerce Sites with large databases
– Anyone needing reliable WordPress backups

Usage

Creating a Migration Package

  1. Go to Migratico Lite > Create Package
  2. Enter a package name
  3. Set maximum ZIP file size (recommended: 100MB for most hostings)
  4. Optionally exclude directories (cache, logs, etc.)
  5. Click Create Package and wait for completion

Downloading the Package

  1. Go to Migratico Lite main page
  2. Click download buttons for your created package:
    • migratico.php – Installation wizard
    • database.sql.zip – Database export
    • files_001.zip, files_002.zip, etc. – Site files

Installing on New Server

  1. Upload all package files to your new server (tip: upload migratico.php first and open it once in your browser before uploading the ZIP / SQL files — see Security)
  2. Open migratico.php in your browser
  3. Follow the 4-step wizard:
    • Step 1: Environment check
    • Step 2: Database settings (with connection test)
    • Step 3: Site settings
    • Step 4: Installation with real-time progress
  4. After successful installation, delete all package files for security

Security

The wp-content/uploads/migratico/ directory is sensitive: migration packages contain the full database (including user hashes) and a copy of the site files. Migratico Lite protects this directory with deny-all .htaccess / web.config rules, a per-package migration secret that must be entered manually in the installer, and automatic package expiration after 4 hours (adjustable via the migratico_package_ttl filter).

nginx users: nginx does not process .htaccess files. Add this to your server block:

location ^~ /wp-content/uploads/migratico/ { deny all; return 403; }

The plugin detects nginx and displays a warning in the WordPress admin until this is configured.

Notes:
– Package files are downloaded only through a nonce- and capability-protected (manage_options) AJAX endpoint.
– The generated installer (migratico.php) refuses every request — page views, form submissions and AJAX endpoints — until the per-package migration secret is entered on its welcome screen. Only the SHA-256 hash of that secret is stored in the package and embedded in the installer; the raw secret is shown once in the WordPress admin when the package is created and is never written to disk, logs or URLs.
– On the target server the installer keeps the entered database and admin credentials and its log in PHP files (installer-data.php, installer-log.php) that return an empty 404 when requested directly, so they cannot be downloaded on any web server that runs the installer. “Delete Installation Files” removes them together with the installer.
– During the database import the installer unpacks the SQL dump under a random, unguessable file name (readable only by the PHP user where the host allows it) and never writes that name to a publicly readable file. The dump is deleted after the import, and “Delete Installation Files” also removes it if an import was interrupted.
– On servers that list directory contents (Apache Options Indexes, the default on many cPanel hosts), an empty web root would list the package files by name. From its first request on, the installer therefore creates a placeholder index.php (HTTP 503 “Site migration in progress”) when the web root has no index.php / index.html. The migrated site’s own index.php replaces it, and “Delete Installation Files” removes it only if it is still the installer’s placeholder. Between uploading the files and opening the installer for the first time the directory can still be listed — upload migratico.php first, open it, then upload the package files, and keep the package files in the same directory as the installer. If an installation is abandoned and the installer and package files are deleted by hand, the placeholder removes itself on the next visit.
– The installer always installs into its own directory (the target site’s web root). WordPress installations in parent folders or subfolders (for example the main site around an add-on domain folder) are never touched.
– Migration packages (completed or interrupted) are automatically deleted after their TTL via WP-Cron.

Credits

Developed by Miroslav Novotny
Website: https://migratico.com
Support: https://migratico.com/support

License

This plugin is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This plugin is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

Installation

  1. Upload the migratico folder to the /wp-content/plugins/ directory
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Navigate to “Migratico Lite” in the admin menu

FAQ

Who Should Use Migratico?

Migratico is perfect for website owners, developers, and agencies who need to:
– Migrate WordPress sites to new hosting
– Create development or staging copies
– Backup sites before updates
– Clone sites for testing
– Move WooCommerce stores

What’s required to use Migratico?

Minimum requirements:
– WordPress 5.3 or higher
– PHP 7.4 or higher
– ZipArchive PHP extension
– Sufficient disk space for backups

Most modern hosting providers meet these requirements.

Do I need coding skills to use Migratico?

No! Migratico is designed for users of all skill levels. The 4-step wizard guides you through the entire process with clear instructions and real-time progress updates.

Will Migratico slow down my website?

No. Migratico only runs when you’re creating a backup or during installation. It has no impact on your site’s front-end performance.

Can I migrate WooCommerce sites?

Yes! Migratico fully supports WooCommerce migrations including:
– Products and categories
– Orders and customers
– Payment gateway settings
– Custom product data
– Large product catalogs

How long does migration take?

Migration time depends on your site size:
– Small sites (< 100MB): 1-5 minutes
– Medium sites (100MB-1GB): 5-20 minutes
– Large sites (1GB+): 20+ minutes

Progress is shown in real-time during the process.

What if the installation gets stuck?

Migratico has automatic timeout recovery:
– PHP timeouts are handled automatically
– Progress is saved every few seconds
– Installation resumes from where it stopped
– Up to 50 automatic resume attempts

Can I migrate large databases?

Yes! Migratico supports databases of any size:
– Chunk-based import prevents memory issues
– Automatic resume after timeouts
– No file size limits
– Tested with databases over 1GB

Does it update all URLs?

Yes, comprehensive URL rewriting includes:
– WordPress core URLs (siteurl, home)
– Post content URLs
– Custom field URLs
– wp-config.php constants
– Serialized data in options and postmeta

Is it safe to use?

Yes! Security features include:
– No data sent to external servers
– Protected export files with .htaccess
– Secure installation process
– Files should be deleted after migration

What hosting providers are supported?

Migratico works on all modern hosting:
– Shared hosting (Hostinger, Bluehost, SiteGround)
– VPS and dedicated servers
– Cloud hosting (AWS, DigitalOcean)
– Local development (XAMPP, Local, MAMP)

Can I exclude files from export?

Yes, you can exclude:
– Cache directories
– Log files
– Temporary files
– Specific plugins or themes
– Upload directories

How do I restore from backup?

Restoration uses the same installer:
1. Upload migratico.php and ZIP files
2. Run the installer wizard
3. Your site is restored to backup state

Where can I get support?

Support is available at:
– Support Forum
– Documentation
– Contact Form

Is there a knowledge base?

Yes! Visit migratico.com for:
– Installation guides
– Troubleshooting tips
– Video tutorials
– Best practices

Screenshots

Changelog

2.7.10

  • FIX: The installer could stop a healthy database import with “The database import keeps failing” when the hosting server killed several import requests shortly after they started, or while the database server was still rebuilding the indexes of a large table (ALTER TABLE … ENABLE KEYS / ADD KEY). After a killed request it now saves its position after every statement, waits for a statement the database server is still executing, and raises the shortened time budget again once requests finish normally.
  • FIX: The time budget of an import request ignored the hosting time limit and was always 55 seconds, so requests could be killed on hosts with a 30-second limit.
  • FIX: TIMESTAMP values could still be shifted by the server’s time zone when the database connection dropped during the export, on sites with a database read/write split (HyperDB, LudicrousDB), or when an export started with an older version was finished after the update.
  • FIX: Stored procedures, functions and triggers in dumps from phpMyAdmin or mysqldump (DELIMITER blocks) were split into separate statements: they were not created, statements from their bodies ran against the imported data, and a SET NAMES from a procedure body could damage the character encoding of all following rows. They are now imported whole, without the DEFINER clause (it requires extra privileges on the target server).
  • FIX: A truncated database file could be reported as complete when its last, unfinished statement was larger than about 1 MB and contained “/*”.
  • FIX: A statement just below the server’s max_allowed_packet failed with “packet too large”.
  • Faster import of tables without a primary key, especially on network storage.

2.7.9

  • FIX: The installer’s database import silently damaged rows longer than 1 MB (large serialized options, page-builder data): part of the value could be dropped, or the row was cut and not imported at all. A comment line longer than 1 MB could even be executed as SQL. Long rows are now imported completely.
  • FIX: When the hosting server killed an import request (time or memory limit), the installer waited 10 minutes before it continued and then repeated the whole interrupted part, which duplicated rows in tables without a primary key. The import now saves its position every few seconds (after every row in tables without a key), continues right away, makes its requests shorter if they keep being killed, and stops with a clear message if the same statement keeps failing. A request that overlapped the end of the import no longer starts it again from the beginning.
  • FIX: TIMESTAMP values could be shifted by the server’s time zone after a migration. The database export now reads them in UTC, as the dump header declares, and the installer applies the dump’s session settings (time zone, SQL mode, character set) to every request of an import that takes several requests and after a lost database connection — before, they applied only to the first request.
  • FIX: SQL statements larger than the server’s max_allowed_packet were skipped without a trace; they are now logged in the installer log and counted as errors. The older import path now also detects a truncated database file.
  • FIX: Database dumps from other tools could lose rows or never finish: a phpMyAdmin dump with SET AUTOCOMMIT = 0 lost all rows of a table when a request ended after its INSERTs, a huge INSERT with one row per line could not be split across requests, and a dump ending with a comment (Duplicator) was reported as truncated.

2.7.8

  • CRITICAL FIX: The installer could overwrite a different, live WordPress site. When it was uploaded into an empty folder inside another WordPress installation (for example an add-on domain folder inside public_html), it installed into the parent site, replacing its files and wp-config.php; it could also pick a WordPress in a subfolder. The installer now always installs into its own directory, and it only looks for, extracts and deletes package files there (it could delete files such as a files_2024.zip backup in the parent folder).
  • SECURITY: The wp-config.php backup made during the migration (wp-config.php.backup.) could be downloaded as plain text, including the database password, and was never deleted. It is now a protected file with a random name, and “Delete Installation Files” removes it together with backups left by older installers.
  • SECURITY: On servers with directory listing enabled (Apache “Options Indexes”, the default on many cPanel hosts), opening the target site’s empty web root listed the package files — including the database archive and, during the import, the randomly named unpacked SQL dump — so anyone could download the complete database. The installer now creates a placeholder index.php from its first request on; the migrated site’s own index.php replaces it, and “Delete Installation Files” removes it if it is still there. If an unfinished installation is abandoned and the installer and package files are deleted, the placeholder removes itself on the next visit.

2.7.7

  • CRITICAL FIX: The installer’s chunked database import lost one row at every chunk boundary (roughly every 25–55 seconds of import), and a boundary inside a CREATE TABLE statement lost the whole table. Large sites migrated with older installers can be missing rows — compare row counts of important tables or re-run the migration with a new package.
  • SECURITY: While the installer imported the database, the complete unpacked SQL dump (user password hashes, e-mail addresses, site options) could be downloaded from the target site’s web root as database_temp.sql — for the whole import, and permanently if the import was interrupted. The dump is now unpacked directly under a random file name, its path is no longer stored in the publicly readable import state, and “Delete Installation Files” removes any leftover dump. A running import from an older installer is converted automatically.
  • SECURITY: The import state of an uncompressed database dump and the package hash cache (installer-hash.txt) no longer reveal the package hash.

2.7.6

  • SECURITY: The installer’s working data (database and admin passwords) could be downloaded from the target site’s web root as installer-data.json while a migration was running, or permanently if the installation files were never deleted. It is now stored in installer-data.php, which returns an empty 404 when requested over HTTP — on Apache, nginx and LiteSpeed alike, without .htaccess rules. A migration started with an older installer is converted automatically.
  • SECURITY: The installer log (now installer-log.php, protected the same way) revealed the package archive names, and with them the URL of the database dump. The database import state no longer stores passwords, and progress messages no longer contain the package hash.

2.7.5

  • Fix: “Delete Installation Files” after a completed migration no longer fails with “Invalid migration secret” when the installer’s PHP session has expired (e.g. after ~24 minutes of inactivity on shared hosting). The installer now also keeps the login in its own HttpOnly cookie, and if both are gone it asks for the migration secret again and then deletes the files.
  • The installer uses its own session cookie name, so sessions of the migrated site can no longer interfere with it. Leftover installer log and data files are removed together with the installer.

2.7.4

  • CRITICAL FIX: Database export could lose rows — when a large table was exported across several requests, DROP/CREATE TABLE was written again on every resume, so the import kept only the last part of the table. Re-export packages of large sites created with older versions.
  • Fix: File export of large sites no longer exceeds max_execution_time (the cost of compressing large files is now budgeted per file) and every export step can be safely repeated after a crash, timeout or lost connection — no duplicated or missing files.
  • New: Export watchdog — interrupted steps are restarted automatically (with backoff) while the export page is open.
  • New: Detailed export status panel (phases, current table / ZIP part, speed, time left, server heartbeat, events) and last-activity info in the package list.
  • Fix: The plugin’s own data directory (uploads/migratico, incl. older packages) is no longer included in the export.
  • Large databases are kept as an uncompressed .sql when compressing would not fit one step; the installer finds it by the package hash and deletes it after the migration.
  • New: The installer checks before the import that all package files were uploaded completely (exact sizes are embedded in the installer, the SQL dump has an end marker) and lists missing or incomplete files; a failed database check can be retried after re-uploading the file.
  • New: Package downloads support resuming (HTTP Range); the package list shows file sizes.
  • Fix: The database dump is written as .sql.part and gets its final name only when complete, so an unfinished dump can no longer be copied over FTP by mistake.

2.7.3

  • Fix: The database export header now actually contains the source table prefix (it had been written empty since 2.5.4), so the installer detects the prefix reliably instead of guessing it from CREATE TABLE statements.

2.7.2

  • CRITICAL FIX: Plugin could not be activated — fatal error “Call to a member function exists() on null” in the activation hook (latent since 2.3.3). All WordPress Filesystem access is now guarded; activation and the admin never fail when the filesystem layer is unavailable (e.g. FTP-based hosts).
  • New admin notice when the protection files for the migration directory could not be written.

2.7.1

  • SECURITY (CVSS 10): Mandatory per-package migration secret, unified authorization gate for the installer, sensitive log data redacted, package TTL reduced to 4 hours.

For the full changelog see CHANGELOG.md.