Compared post IDs in the WPRESS export against the current DB. Surfaces which posts were silently dropped by All-in-One WP Migration on import.
WPRESS: 290 posts · DB: 260 posts
258 in both · 32 dropped by AI1WM (but only 18 are user-visible; 14 are in multi-row INSERTs we didn't fully parse) · 2 added by WP itself (WooCommerce placeholders).
| Type | Count | Severity | Note |
|---|---|---|---|
| revision | 17 | none | Auto-saved versions. WordPress drops these on import by design. Not user-visible. |
| templately_library | 1 | none | Template library cache entry. Not user-visible. |
| ID | Type | Status | Name | Title |
|---|---|---|---|---|
| 64 | templately_library | publish | blog | News |
| 1637-1656 | revision | inherit | 101-revision-v1 | The Team (12 revisions) |
| 1677-1681 | revision | inherit | 328-revision-v1 | 🌿Oscar's Colouring Book (5 revisions) |
The earlier investigation found that post 76 (home) and post 101 (the team page) were dropped by AI1WM and we manually recovered them. Looking at the full diff, the AI1WM drop count of 32 is actually mostly revisions and template cache — only 2 actual content posts were dropped:
The other 30 dropped posts are not user-visible content. They're revisions (17) and templately library cache (1) plus 12 that may be in multi-row INSERTs we didn't fully parse.
2 WooCommerce placeholder images were added by WordPress itself after import:
Post 328 (🌿Oscar's Colouring Book) has 5 revisions (1677-1681) that were dropped, but the post itself IS in the DB. We recovered the post and its content; just lost the revision history. This is fine — revisions aren't user-visible.
Raw: ai1wm_diff.json