Open Migration > Migration jobs in the site admin and select the job you are reviewing with Amadalis. Use this guide to see which imported WordPress pages are ready before agreeing to replace your website.
Checked against the product’s code on 7 November 2026.
Before you start: arrange the move with Amadalis through the migration service. This guide starts with an imported job to review.
The Migration workspace brings imported content and review evidence together. A successful import is the beginning of review, not permission to switch the public domain. Read any items held for a site Admin, including redirects, SEO fields or content-type settings and site accounts. Ask an Admin to complete those parts; imported pages do not prove they were applied.
Review each imported item
Section titled “Review each imported item”A migration handoff does not recreate a missing page. If the site can be read and the imported page is no longer there, the copilot receives that fact instead of being sent to edit a stale page address.
A shared colour that cannot be resolved remains a finding to review. When its control’s explanation already names the missing binding, the report avoids a second explanation for that same binding. An explanation is not proof the original colour, gradient or video was reproduced.
- Search Imported items. Use the available filters or CSV spreadsheet file to inspect the list.
- Open the page by its title. Its review shows Before, After and Split.
- Choose Split to compare the original with the destination at the same browser width.
- Choose Open the page when offered to inspect the destination’s editable page.
If the comparison says Oracle, it is a source reference, not the editable page on your new site. Ask the migration engineer for that page before accepting it.
Supported parts of a source page become sections you can edit. A part that cannot be rebuilt exactly is kept as it was and listed for review. Anything not listed may still need a manual check.
On an Elementor import, a shared color missing from the export can be read from that page’s saved styles. The export’s shared color definitions take priority. Review any colors still listed as missing.
An import can bring in pages while leaving other site parts unfinished. A review item can say Your menus, categories, tags, authors, SEO settings, sections, header and footer, and widgets were not imported. Its full reason continues: None of them were written to your site. Please contact support so we can finish the import. Pages already imported stay in place.
Another review item can say Your authors, SEO settings, section previews, header and footer, and widgets were not imported. Menus, categories, tags and sections can already be in place. Follow its request to contact support.
Use the offered conversion action or Undo conversion according to the item. For a finding, use Fix with Copilot, Accept or Mark manual. The whole page has Accept the page and Mark manual. Read the actual proposed change and its result. Accepting an item is different from hiding a finding you have not inspected.
Inspect the review tabs
Section titled “Inspect the review tabs”When a page review is open, choose All pages to return to the job. Choose Inspect to reveal the tabs below.
Workflow shows progress. Honesty report and Scan expose reported gaps and the estimate of what the source contains and what can move. Scan complexity is an estimate, not a measured promise of how long the project will take. Native site shows how the site’s page addresses, menus, redirects and search settings work.
Cutover brings the candidate’s required comparisons, checks for content still served by the source site and acceptance together. It counts only the gaps nobody has accepted yet. Items you accepted as they are stay listed beside the original import totals, which do not change.
Before approving, ask the migration engineer to finish and record the comparison evidence.
- Open Cutover.
- Read Review and fidelity acceptance, including each remaining blocker.
- Choose Approve publication and cutover only when it is available and you accept the reviewed version.
- Read the result. The button becomes Publication and cutover approved. This records permission; it does not publish pages or switch traffic.
- Read Native cutover receipt. Ask the engineer to resolve any blocked check.
- Choose Issue receipt only when it is available.
- Check that the receipt reads issued before arranging the switch.
Publish and switch separately
Section titled “Publish and switch separately”For eligible drafts:
- Choose Review to return from Inspect to Imported items.
- Select each intended page using its checkbox. The bulk actions appear when items are selected.
- Choose Publish N, where N is the number of eligible selected drafts.
- Review the selection and any warning about pages that were drafts on the source.
- Choose Confirm publish N to publish through your own session.
- Read how many pages published and any failures. Failed pages remain selected.
Limits. Pages can succeed or fail separately; failed pages remain selected for review or retry. Publishing the whole imported site is not an all-or-nothing operation.
Anything the copilot publishes pauses for its approval card. Arrange the domain switch only after the reviewed candidate and required evidence are accepted. Domain verification, routing and certificate readiness remain separate checks. Follow Add your own domain with the migration engineer, keeping the domain pointed at the old site until the account’s domain card gives the switch instruction. Keep the source site available until the migration engineer confirms the switch. After the switch, check the published pages, menus, pictures and forms at the public address.