Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
To change an existing WordPress item from a post to a page—or to or from a registered custom post type—use a post-type conversion tool such as Post Type Switcher, then check the item’s URL, taxonomy, metadata, and templates. This reassigns the existing content; it does not create a new post or register a new post type.
What changing a post type actually does
A post type is the value WordPress stores for an item, such as post, page, or a custom identifier. Conversion changes that value on the existing item. The title, content, ID, and other stored data remain associated with the same record, but the editor, URL rules, archives, templates, taxonomies, and plugin behavior can change.
Registering a new custom post type is a separate task. The destination type must already be registered before any content can use it.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Before you convert anything
- Back up the database. The Post Type Switcher listing recommends a database backup and warns that plugin conflicts can occur.
- Test a small sample. Convert one or two representative items before changing a whole section.
- Check the destination type. Confirm that the custom post type is registered, has the capabilities and taxonomies you need, and is not using an identifier that collides with another type.
- Record the current URLs. A post-to-page or custom-type conversion can change the permalink structure, so keep a list for redirect planning.
Method 1: Convert in the WordPress dashboard
Install and open the converter
- In the WordPress dashboard, go to Plugins > Add New.
- Search for Post Type Switcher, install it, and activate it.
- Open the post, page, or supported custom-type item you want to change.
Change one item
- In the editor, find the Post Type selector above the Publish/Update controls. The exact placement can vary with the editor and screen.
- Choose the destination type, such as Page or a registered custom type.
- Save or update the item.
- View the item on the front end and reopen it in the editor to confirm that it remains visible and editable.
Convert several items
- Open the supported list screen for the source type, such as Posts > All Posts.
- Select the items to change.
- Choose Bulk actions > Edit, apply the bulk edit, and select the destination post type when that control is available.
- Save the bulk edit, then inspect a sample from the converted set.
Post Type Switcher documents Page to Post, Post to Page, Post to Custom, and Custom to Custom conversions. Available choices can depend on the source, destination, and admin screen.
Method 2: Use WP-CLI for auditing and scripted work
WP-CLI is useful for discovering the site’s registered types and reviewing posts before or after a change:
wp post-type listlists registered post types.wp post-type get <post-type>displays details for one type.- The
wp postcommands can list and update posts, including withwp post update.
The cited WP-CLI references do not document a dedicated wp post-type convert command. Do not paste a guessed conversion command into production. Any scripted migration should be designed for the site’s IDs, taxonomies, metadata, URLs, and rollback plan, then tested against a backup or staging copy.
Rank #2
When the destination is a custom post type
Register it first
WordPress’s register_post_type() API creates the type; conversion tools can only assign content to a type that exists. WordPress recommends registering custom types in a plugin rather than a theme so the type remains available when the theme changes. Register it on the init hook.
Choose a safe identifier
- Prefix the identifier to reduce collisions with other plugins and core.
- Keep it under 20 characters.
- Do not use the reserved
wp_prefix, and check that the identifier is not already registered.
Connect taxonomies and refresh rewrites
Declare associated taxonomies with the registration’s taxonomies argument or connect them through the appropriate registration code. If the type has custom rewrite settings, refresh permalink rules after activation or by visiting Settings > Permalinks and saving the page. WordPress’s reference recommends handling rewrite flushing on plugin activation and deactivation rather than on every request.
Rank #3
What to verify after conversion
| Area | What to check | Why it can change |
|---|---|---|
| Editor | The item opens, remains editable, and exposes the fields expected for the destination type. | Post-type support and metabox registration can differ. |
| Taxonomies | Categories, tags, and custom taxonomy terms still appear and have the intended assignments. | Taxonomies may be registered for only selected types. |
| Metadata | SEO fields, custom fields, featured images, and plugin-specific data still behave correctly. | Plugins may conditionally load metadata by post type. |
| Permalink | Open the new URL and compare it with the recorded old URL. | Rewrite settings and type slugs can produce a different path. |
| Templates | Check the single item and any archive page. | Custom types commonly use single-{post_type}.php and archive-{post_type}.php. |
| Navigation and feeds | Check menus, internal links, search results, XML sitemaps, and feeds where relevant. | Queries and inclusion rules often filter by post type. |
The Post Type Switcher listing says its action changes the post_type property, preserves taxonomy associations, and contains no code intended to delete content. Treat those as the plugin’s stated behavior, not a guarantee that every theme, plugin, URL, or metadata integration will remain unchanged.
Redirects and recovery
If the permalink changed, create a permanent redirect from the old URL to the new one after confirming the destination works. Update internal links and any external systems that stored the old address. If the result is wrong, stop the bulk operation, restore the database backup if necessary, and investigate conflicts or missing destination-type support before trying again.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choosing the right approach
| Situation | Best fit | Main consideration |
|---|---|---|
| One or a few items | Dashboard conversion with Post Type Switcher | Fastest visual confirmation, but still requires URL and template checks. |
| Many selected items | Supported bulk edit | Efficient, but sample-check the result and keep a rollback backup. |
| Repeatable migration across many records | WP-CLI-assisted audit and a purpose-built script | More auditable, but there is no documented one-command converter in the cited references. |
| New custom destination | Register and configure the type first, then convert | Rewrite, taxonomy, capability, and template setup are prerequisites. |
Compatibility notes
The WordPress.org listing reports Post Type Switcher version 4.0.1, WordPress 6.2 or higher, and PHP 8.0 or higher. These details and the available conversion controls are volatile; verify the current listing and your site’s compatibility before installation. Test on staging or a backup before changing production content.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
