After your import
When a migration job completes, open Settings → Import Site → Reports to read counts and download the JSON report, publish imported pages in Pages, fix any asset warnings, then connect your custom domain when the site is ready for visitors.
Import jobs run in the background. When status shows Completed, your content is in the workspace—but visitors do not see it until you publish pages and point your domain.
Prerequisites
- A completed job on Settings → Import Site → Reports.
- Workspace owner access (same role that ran the import).
Step 1: Read the migration report
- Open Settings → Import Site.
- Switch to Reports.
- Find your job row — summary text shows counts such as pages, posts, and media.
- Click Download report for the full JSON artifact.
Report fields that matter
| Field | What it tells you |
|---|---|
| processed / failed / skipped | How many entities finished vs errored |
| assetFailures | Images that could not be downloaded (page still imported; original URL may remain in HTML) |
| contentFailures | Pages or posts that failed to write — investigate before cutover |
| redirectMap | SEO redirects applied — see Preserving SEO and redirects |
| pages (per page) | importMode: componentTree (editable layout) vs snapshot (refine in editor) |
A job can complete with asset failures—the worker exits successfully but lists warnings. Treat asset failures as a checklist, not necessarily a failed migration.
Step 2: Publish and refine content
- Open Pages — imported pages appear with their titles and slugs.
- Open each priority page, review layout in the page editor, and click Publish.
- For snapshot imports, expect to adjust spacing, swap blocks, or reconnect portfolio embeds — see Introduction to the page editor.
- Open Posts for blog content — set featured images if any failed to import.
- Open Portfolio for imported collections — confirm cover image and public page toggles.
- Open Media — verify key assets arrived; upload any missing files manually if needed.
Imported drafts do not replace your existing homepage automatically. Set home page under Pages if you imported a new front page.
Step 3: Fix missing images
Asset failures usually mean the importer could not reach the image URL:
- Local or staging URLs (
192.168.x.x,localhost) — not reachable from ArtInStack production; re-import after exporting with a public domain or upload files to Media manually. - Offline WordPress — bring the site online temporarily or re-export with attachments included.
- Wrong public site URL — re-scan with the correct domain and run a media-focused import pass.
After fixing sources, you can run another import selecting only missing Media rows (already-imported items are marked).
Step 4: Configure what import does not cover
| Area | Next guide |
|---|---|
| Site header, footer, menu | Header, footer, and navigation |
| Store and checkout | Products and selling section |
| Blog listing page | Create a Blog Listing block page if you imported posts but have no index page |
| Client galleries | Galleries and Portfolio |
| Custom domain | Set up your workspace |
Step 5: Go live
When preview looks right on your workspace URL and redirects check out:
- Verify domain in Settings → General.
- Update DNS at your registrar.
- Wait for SSL propagation (up to 48 hours in some cases).
- Re-test legacy URLs and key pages on the custom domain.
Your old WordPress site can stay online on a staging URL until you are confident—just avoid serving duplicate public content on the same hostname.
Verifying your setup
- Reports shows Completed with acceptable failure counts.
- Priority pages and posts are published and load on your workspace URL.
- Media contains hero and gallery images you care about.
- Sample legacy URLs 301 to the correct new paths.
- Navigation and header/footer match your brand (manual step post-import).
Troubleshooting and common pitfalls
| Symptom | What to check |
|---|---|
| Job stuck on Queued | Wait a few minutes in production; contact support if it does not progress |
| Job Failed with content errors | Open report JSON errors; fix export and re-import affected entities |
| Page looks nothing like WordPress | Snapshot import — rebuild sections in the page editor using blocks |
| Portfolio page empty | Collection may exist without Public page enabled — open Portfolio → Manage portfolio → Settings |
| Team member cannot import | Only workspace owner — owner must run Import Site |