Central-only operator tooling for the WordPress compatibility lane. Validates versioned migration bundles, reports which sections are supported today, and simulates imports against a temporary ForgeJournal without touching the live marketing journal.
This module belongs on the LuperIQ management server and is not meant to ship on customer or demo sites.
Migration Hub sits in the System layer of LuperIQ and focuses on Inspect versioned WordPress migration bundles and safely simulate supported CMS imports. For a site owner, the practical value is not the module name by itself; it is whether Versioned migration bundle schema, WordPress bundle inspection and warnings, and Safe import simulation in temp journal becomes easier to manage in the real customer or admin path.
For pricing and setup, the useful context is Management server only and the place the owner will likely manage it is WordPress. Those details help the reader understand the module without turning the page into a technical inventory.
Migration Hub works best when Theme Studio and Commerce are already understood, because those surrounding tools shape where the data, settings, or customer actions will land.
Migration Hub is documented as a practical module first. If the owner is evaluating AI help around the same area, the safer next step is to start in the WordPress admin area and only add AI when there is a real task to run.
This module is documented first around the module itself. Public AI workflow pages are focused on the currently fixed-price credit jobs registered in Nexus.