How to Migrate Custom Post Types Between WordPress Sites
A custom post type — a Portfolio Item, a Product, a Case Study, whatever a theme or plugin registered for your site — isn't fundamentally different from an ordinary Post in WordPress's own database. So it's a fair question whether it migrates between sites the same way a Post does. Mostly, yes. There are a few specific places where "mostly" stops being good enough, and they're worth knowing before you hit one.
What actually makes a post type eligible
Posts and Pages are always eligible, no questions asked. For anything else, three things have to be true: the post type has to actually exist (obviously), it has to be public with its own admin screen, and it has to support either a title or an editor field. That last part is "or," not "and" — a post type that only supports a title, with no content editor at all, still qualifies.
A small, explicit list is excluded regardless of whether it technically passes those checks: WordPress's own media/attachment type (which already migrates through its own dedicated path, tied to whatever post actually references it — an attachment with nothing pointing at it has no post to attach the resulting file to), and a couple of page-builder/plugin-internal storage types that exist purely as internal configuration, not content anyone would recognize as "a post." Those aren't things you can opt back in — they're excluded at the same structural level Posts and Pages are guaranteed to pass, so they never show up anywhere a migratable type would.
Everything else is opt-out, not opt-in
Beyond that structural check, which post types are actually allowed to migrate is a plain list of what's been explicitly turned off — not a list of what's been turned on. That direction matters: register a brand-new custom post type next month, and it's included by default the moment it exists, exactly like every other eligible type already is. Nothing has to be remembered or re-enabled for a type nobody's told the plugin about yet.
What happens to a CPT's taxonomy terms
Custom taxonomies attached to a custom post type migrate the same way categories and tags do on an ordinary post — by taxonomy and term slug, never by the term's numeric ID, because a term ID is a database-assigned number with no guarantee of meaning the same thing on two different WordPress installs. The destination looks up a matching term by slug, creates it if it doesn't exist yet, and applies the full matching set — a repeat push replaces a post's terms for that taxonomy rather than piling up duplicates each time.
A taxonomy that isn't public is skipped — not an error, just left alone, the same way a private taxonomy would be for a normal post. And if the taxonomy itself doesn't exist at all on the destination (the plugin that registers it isn't active there), any term under it is quietly dropped rather than causing the whole push to fail.
The failure that actually stops a push
The real way a CPT migration can fail outright isn't on the sending side — it's on the destination, when the content arrives and the receiving site checks whether it recognizes that post type as something it can accept. If the plugin or theme that registers the custom post type isn't active on the destination at all, there's nothing there matching that type's name, and the push is rejected rather than falling back to a generic post or silently losing the type. The practical fix is exactly what it sounds like: the same plugin registering the same post type, the same way — public, with an admin screen, supporting a title or editor — needs to be active on both sites.
What doesn't carry over, by design
The author and the parent post are deliberately left unresolved by the generic migration path rather than guessed at — a raw source-site user ID or parent post ID means nothing on a different install, and attributing content to the wrong local account because an ID happened to coincide is worse than leaving it blank. For a hierarchical custom post type that actually relies on parent/child structure, that's worth knowing specifically: without real author and parent resolution, those relationships don't survive a plain migration — they need to be resolved to who/what they actually correspond to on the destination, not just copied as numbers.
What PostDeploy does about all of this
Every structurally-eligible post type — Posts, Pages, and any custom post type that qualifies — migrates through the identical pipeline: fields, taxonomy terms resolved by slug, featured image, and in-content media, all handled the same way regardless of what registered the type. Pro adds real author and parent resolution (a mapped user or a matched-by-email/login account, and the actual destination post a parent relationship should point at) instead of leaving them unresolved, plus a per-post-type enable/disable list on the Settings page for explicitly excluding a type you never want migrated at all.
Try it
PostDeploy Free migrates Posts, Pages, and custom post types — the same eligibility rules described here, no plugin database tricks required. PostDeploy Pro adds real author/parent resolution along with ACF, Elementor, and WPML reference resolution.