WordPress treats each post type as its own distinct structure with its own fields, templates, and taxonomy relationships, so content created as the wrong type from the start — a page that should have been a blog post, entries that should be a custom post type rather than generic pages — can’t simply be relabelled; moving it properly means recreating it correctly in the destination type while preserving everything that made the original complete. This kind of mismatch tends to happen gradually rather than all at once — a site starts using pages for something that later turns out to need its own dedicated post type, and by the time that becomes clear, dozens or hundreds of entries already exist in the wrong place.
Confirm the scale before ordering
Count roughly how many pieces of content actually need to move, and note whether they carry featured images, custom fields, or category and tag assignments, since each of those needs to be deliberately carried across rather than assumed to follow automatically.
A handful of items is a very different job from hundreds, so even a rough count helps us give you an accurate scope.
It’s also worth thinking about whether any of this content is linked to from elsewhere on your site, or externally, since preserving those links correctly is part of what a careful migration needs to account for.
Content migration between post types
Content sitting in the wrong post type — pages that should be posts, products that should be a custom type. We migrate it across cleanly.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- The source post type and the destination post type content should move to
- Which specific content is in scope, or confirmation you want everything of that type moved
- Any custom fields, taxonomies, or relationships that must be preserved
This or something else?
| Content exists as the wrong post type and needs to be properly recreated as the correct one | This fix covers it |
| You want Classic Editor content converted to blocks, not moved between post types | Classic-to-block content conversion, a different service |
| You want bulk content imported from an external file, not moved within the site | Bulk content import from supplied file, a different service |
| You’re unsure which post type your content should actually be, and want advice first | Worth a quick conversation before ordering; we can advise as part of scoping |
| Only a field or two needs correcting, not the entire post type | Often a smaller, more targeted fix; worth checking before committing to a full migration |
What we do
- Map every field, taxonomy, and relationship the content currently has in its source type
- Confirm how each maps to the destination post type’s own structure
- Recreate the content correctly in the destination type, preserving URLs where practical
- Carry across featured images, custom fields, and taxonomy assignments
- Verify the migrated content displays and functions identically to the original
- Remove or archive the original entries once migration is confirmed successful
What is included
- Content correctly recreated in the destination post type
- Featured images, custom fields, and taxonomy assignments carried across
- Verification that migrated content displays and functions correctly
- The pre-migration content backed up and retained for 30 days
Not included
- Redesigning the content or its templates beyond the migration itself
- Preserving URLs in every case, where the destination type’s structure genuinely prevents it
- Ongoing migration as new content is created in the wrong type going forward
- Deciding which post type is correct for your use case, beyond initial scoping advice
Questions about this fix
Will my URLs stay the same after the migration?
Where practical, yes, though some post type structures make that harder to guarantee — we'll tell you upfront if your specific case has a URL change and can set up redirects if needed.
What happens to comments on the original content?
We carry those across along with the content itself, so discussion history isn't lost in the move.
Can this be done gradually, rather than all at once?
Yes, if you'd rather migrate in batches to verify each one before continuing, that's a perfectly reasonable way to approach a larger migration.
Will SEO be affected by moving content between post types?
It can be, particularly if URLs change, so we address that specifically as part of the migration rather than as an afterthought.
What if some content doesn't cleanly map to the new post type's fields?
We flag those cases specifically and discuss the best approach with you, rather than forcing a poor fit silently.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.