Website Migration Database Support
Different applications stress different parts of a migration. WordPress is usually balanced, Magento can be file and database heavy, Matomo is database heavy, Nextcloud is file heavy, and Node.js may depend on an external database or runtime service.
Database engines
Migration Monkey’s v1 production path is strongest for WordPress on MySQL or MariaDB. The app also tracks PostgreSQL, SQLite, MongoDB, Redis, and external app-managed data stores as job metadata so operators can choose the correct runbook instead of guessing.
Why the credit math varies
Credits are based on the detected app profile, file size, database size, route method, source constraint, and domain rewrite needs. This avoids penalizing a file-heavy app the same way as a database-heavy app.
Current support posture
- WordPress with MySQL/MariaDB: direct file and database migration path.
- Magento, Drupal, Joomla, Laravel, and Node.js: app-aware setup with guided database runbooks.
- PostgreSQL, SQLite, MongoDB, Redis, and external databases: tracked as migration requirements and routed for assisted support until tested paths are promoted.