MuRu Migration

Export scope

Export selected modules or all modules at once, filterable by client -- Site, Administrator, or both.

Full configuration preserved

Params, position, ordering, access levels, and language all come across intact.

Menu assignments

Which pages each module appears on is preserved and remapped through the stored menu ID map on import.

SP Page Builder support

mod_sppagebuilder modules automatically bring their content from the #__sppagebuilder table with them.

Overwrite matching

Import can match existing modules by ID or by title + type when overwrite is enabled.

Type validation

Module types are checked against what's installed on the target; unrecognized types are skipped with a warning instead of importing broken.

Export scope

Export selected menu items, or export by menu type.

Structure preserved

Parent-child hierarchy, link, type, component ID, params, and access levels all carry over.

Missing menu types created

If an imported item references a menu type that doesn't exist on the target, it's created automatically.

All item types supported

Component, URL, alias, separator, and heading items all import.

Component validation

Component-type items are checked against installed extensions on the target before import; missing ones (e.g. com_virtuemart, com_k2) are skipped with a warning. Non-component items always import safely.

Home page conflicts

If the target already has a default (home) page for a language, an imported home item comes in with home disabled and a warning, instead of creating two home pages.

Alias & article links remapped

params.aliasoptions references and com_content article links in menu items are rewritten to the target's IDs when the linked articles or menus were imported first.

Export scope

Export selected articles, all articles, articles filtered by category, or categories only.

Full content preserved

Introtext, fulltext, images, URLs, metadata, featured flag, and custom fields all come across.

ZIP-based media

Article exports produce a .zip with a clean data.json plus a media/ folder of raw image files -- intro, full-article, inline <img>, and CSS background images.

Supported formats

JPG, JPEG, PNG, GIF, WebP, SVG, BMP, ICO, up to 10 MB per file.

Import formats

Accepts both .zip (recommended) and legacy .json exports for backward compatibility.

Category tree safety

Category hierarchy (parent-child, level, path) is preserved, parents resolved by remapped ID or alias, and the category tree is rebuilt after import so existing categories aren't corrupted.

Overwrite matching

Articles matched by ID or alias; categories matched by alias + extension.

Export scope

Export selected users or all users, optionally filtered by user group.

Data preserved

Name, username, email, password hash, registration date, last visit, and block status.

Groups matched by title

Source group IDs aren't assumed to exist on the target -- groups match by title, missing ones are created under the correct parent, and the usergroup tree is rebuilt afterward.

Profile data restored

#__user_profiles data comes across alongside the account.

Passwords preserved

Password hashes are kept as-is, so users log in with their existing password on the new site.

Duplicate handling

Import matches by ID, username, or email; users with an existing username or email are skipped unless overwrite is enabled.