Skip to content
GPLWP Guides

How to migrate galleries between WordPress plugins

Backup & Migration Time About 30 minutes for a small library; longer for hundreds of galleries 6 steps Updated 10 Oct 2026

BACKUP & MIGRATION
The short answer

Migrating galleries between WordPress plugins is rarely a database-only job because each plugin stores images, albums, metadata and display settings differently. You can rebuild galleries manually, but for a NextGEN-to-Envira move, an importer is the faster and safer route after a complete backup.

The route
  1. 01Inventory the galleries first
  2. 02Back up files and database
  3. 03Rebuild galleries manually if needed
  4. 04Install the destination plugin
  5. 05Import in small batches
  6. 06Replace embeds and check everything

What you need

  • Administrator access to WordPress
  • A complete database and files backup
  • Access to the source gallery plugin and its image files
  • A staging site for large or business-critical migrations

Inventory the galleries first

List the galleries, albums, tags, image counts and pages or posts that display them. Note any custom captions, descriptions, lightbox settings, watermarks, password protection or gallery-specific styling that you must reproduce.

Do not delete the old plugin yet. Its galleries may be stored in plugin-specific database tables and its images may not be ordinary WordPress Media Library attachments. NextGEN, for example, stores gallery and picture information separately from standard WordPress content.

Back up files and database

Create a full backup before importing anything. Keep both the database export and the WordPress files, including uploads, themes, plugins and configuration files. A database backup alone will not restore the image files, and a file backup alone will not restore gallery records or page content.

Use a staging copy where possible, and make a second backup immediately before the final migration. If an importer times out or creates duplicates, you need a clean rollback rather than a half-converted site.

Rebuild galleries manually if needed

The manual route is to install the destination gallery plugin, create each gallery again, upload or attach the original image files, then re-enter titles, captions, descriptions, tags and ordering. Recreate albums after their component galleries exist, and replace the old gallery blocks or shortcodes in each page and post.

This works for a small number of galleries, but it is slow and easy to get wrong. You can lose image order, captions, tags, album relationships or links when copying records by hand. Never copy database tables directly between unrelated gallery plugins unless the destination plugin documents that process.

Install the destination plugin

Install and activate the gallery plugin you are moving to, but keep the source plugin active while you verify the imported content. If you are moving from NextGEN Gallery to Envira Gallery, install Envira first and make sure its required importer or add-ons are available.

For a temporary display-only change, some gallery systems can output a NextGEN gallery through a dynamic gallery feature without recreating the images. That is a presentation workaround, not a full migration, because the source plugin still owns the gallery data.

Import in small batches

For a NextGEN-to-Envira migration, open Envira Gallery and the NextGen Import screen, select the galleries, and start the import. Import all galleries before importing albums so the album relationships have destination galleries to reference. The documented importer also provides separate areas for galleries and albums, and the supporting guide describes importing tags as well.

Do not select a very large library if the server has limited PHP execution time or memory. The importer documentation warns that too many galleries can time out, so process a few at a time and confirm the success status before continuing.

Replace embeds and check everything

Open every important page and post and confirm that the new gallery is displayed, not just that the gallery exists in the destination plugin. Gallery records and page embeds are separate pieces of content, so an import may not rewrite every old shortcode or block automatically. Update those embeds manually if necessary.

Check desktop and mobile layouts, image order, captions, alt text, links, lightboxes, albums, tag filters and thumbnail sizes. Only after the checks pass should you disable the old plugin. Keep its files and database backup until search-engine URLs, redirects and visitor-facing galleries have been monitored.

The fast route

Let Envira Gallery NextGEN Importer Addon do it

Imports NextGEN galleries, albums, tags, and metadata into Envira; choose it for a one-click gallery-plugin migration.

Get Envira Gallery NextGEN Importer Addon

Sources

  1. wordpress.org /support/topic/finding-images/?utm_source=openai
  2. developer.wordpress.org /advanced-administration/security/backup/?utm_source=openai
  3. enviragallery.com /docs/dynamic-addon/?utm_source=openai
  4. enviragallery.com /docs/nextgen-importer-addon/?utm_source=openai
  5. enviragallery.com /import-nextgen-galleries-albums-envira-gallery/?utm_source=…

Questions

Can I migrate galleries without a plugin?
Yes, but manual migration is practical only for a small number of galleries. You must copy the original image files, recreate each destination gallery, re-enter or transfer metadata, rebuild albums and replace the old embeds in posts and pages. Because gallery plugins use different data structures, copying database tables directly is unsafe unless the destination documentation explicitly supports it.
Will migrating galleries preserve captions and metadata?
An importer may preserve captions, tags and other metadata when it supports those fields, but you should verify a sample before removing the source plugin. Manual recreation does not preserve anything automatically: titles, descriptions, captions, tags, image order and gallery settings must be copied or re-entered. Envira’s NextGEN migration material specifically describes importing galleries, albums, tags and metadata.
Why did my gallery migration time out?
Large imports can exceed the server’s execution time, memory or request limits. Import fewer galleries per batch, wait for each batch to report success, and check whether duplicate images were created before retrying. The Envira importer documentation specifically warns that importing too many galleries at once can cause a timeout.
Do I need to replace gallery shortcodes after migration?
Usually, you should check and replace them where necessary. Importing gallery records does not guarantee that every post, page, widget or template will automatically point to the new plugin. Search your content for the old gallery blocks or shortcodes, update important pages, clear caches and test the front end while the original plugin is still available for rollback.
When should I deactivate the old gallery plugin?
Deactivate the old gallery plugin only after the new galleries, albums and page embeds have been checked on a staging or live copy. Keep a complete backup and do not delete the source images or database tables immediately. If a page breaks, captions disappear or an old shortcode remains, you may need the source plugin enabled while you correct the content.