Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteTo convert existing WordPress content, change its post_type rather than creating a duplicate. For most sites, the safest route is the Post Type Switcher plugin: back up the database, test a small sample, select the destination type in the editor or Bulk Edit, save, and then check URLs, templates, taxonomies, metadata, and front-end output. Register a custom post type separately before attempting to move content into it.
Changing a post type versus registering one
Conversion reassigns an existing item—such as changing a post to a page or moving content between custom types. The content record is not supposed to be recreated as a second post. Registration is different: it defines a custom post type so WordPress can recognize, edit, route, and display that type. A target custom type must already be registered before conversion.
Prepare before converting anything
- Back up the database. The Post Type Switcher listing recommends a database backup and warns that conflicts with other plugins can occur.
- Check the destination type. Confirm its identifier exists, is spelled correctly, and is not already used by another plugin or by WordPress.
- Use a staging copy when possible. Convert one or two representative items first rather than changing an entire site at once.
- Record the current URLs. A type change can alter permalinks, archives, and the templates selected by the theme.
- Define a rollback. Keep the backup and a list of converted IDs so you can restore or reverse the change if the result is wrong.
Convert posts, pages, or custom items in the dashboard
Post Type Switcher documents conversions among Page to Post, Post to Page, Post to Custom, and Custom to Custom. Its current listing reports version 4.0.1, WordPress 6.2 or newer, and PHP 8.0 or newer; these compatibility details can change, so verify the listing and your site requirements before installation.
Convert one item
- In WordPress, open Plugins > Add New, search for Post Type Switcher, install it, and activate it.
- Open the post, page, or custom item you want to move.
- In the editor’s publishing panel, locate the Post Type selector (the listing places it above Publish).
- Choose the destination type, such as Page or a registered custom type.
- Save or update the item.
- Open the item in the editor again and visit its public URL to confirm that it remains editable and renders correctly.
Convert many items with Bulk Edit
- Open the supported list screen for the source type, such as Posts > All Posts.
- Select the items to move and choose Bulk Edit.
- Set the destination post type in the available fields, then apply the change.
- Process a small batch first. Admin fields and available destinations can vary by source type and screen.
- Review several converted items, their URLs, and the front end before processing the remaining batches.
The plugin states that it changes the item’s post_type, preserves taxonomy associations, and contains no code intended to delete content. Those are the plugin’s stated behaviors, not a guarantee that every theme, metadata provider, editor, URL structure, or integration will behave identically.
Free tools Windows power users keep installed
One-click scans. No signup required.
Register a custom post type before using it
If the destination is a custom type that does not exist yet, create the registration first. WordPress recommends putting registration in a plugin rather than a theme so the type remains available when the theme changes.
Registration requirements
- Use WordPress’s
register_post_type()API on theinithook; registrations should not run earlier. - Choose a unique, prefixed identifier shorter than 20 characters and do not use the reserved
wp_prefix. - Check existing registrations for collisions before selecting the target identifier.
- Connect taxonomies through the post type’s
taxonomiesargument or an equivalent supported registration approach. - After changing rewrite settings, refresh rewrite rules by activating/deactivating the owning plugin or manually visiting Settings > Permalinks and saving.
Registration alone does not move existing posts. Once the type is available and its labels, capabilities, taxonomies, and rewrite settings are correct, use the dashboard conversion workflow or a carefully audited migration process.
Rank #2
Using WP-CLI for auditing and controlled scripts
WP-CLI is useful when you need an inventory or a repeatable migration around a deployment process. The post-type command can inspect registered types:
wp post-type listlists registered post types.wp post-type get <post_type>displays one type’s registration details.
The post command can list and update posts, including with wp post update. The cited command references do not provide a dedicated wp post-type convert command, so do not run a guessed conversion command. A script that updates post_type must be designed for the site’s IDs, permissions, taxonomies, metadata, revisions, URLs, and rollback plan, then tested on staging and a small sample.
Recommended Free Tools
Rank #3
What to verify after conversion
Permalinks and redirects
Open the converted item’s permalink and compare it with the recorded old URL. If the path changed, create redirects from old addresses and update internal links, XML sitemaps, navigation, feeds, and canonical settings as appropriate. Refresh rewrite rules when the custom type’s rewrite configuration changed.
Single and archive templates
Custom types may use single-{post_type}.php for individual items and archive-{post_type}.php for archives. Check both views, plus any block-template or page-builder templates assigned to the destination type. Confirm that the type is publicly queryable and that its archive setting matches the intended site behavior.
Taxonomies, fields, and editor behavior
- Verify categories, tags, and custom taxonomy terms on several converted items.
- Check custom fields, featured images, revisions, author data, comments, and page-builder content.
- Confirm the destination type exposes the needed editor supports and metaboxes.
- Test search, REST/API output, feeds, menus, related-content widgets, and SEO fields if those integrations matter on your site.
Visibility and permissions
Make sure the converted item is still visible to the intended audience and that the appropriate roles can edit it. A theme or plugin may apply different capability, status, or query rules to the destination type.
Choosing an approach
| Situation | Best starting point | Audit and risk considerations |
|---|---|---|
| One post, page, or custom item | Post Type Switcher editor selector | Easy to inspect immediately; still test URLs, fields, and templates. |
| A selected group of items | Post Type Switcher Bulk Edit | Process small batches and verify representative results before continuing. |
| Destination type is not registered | Register it on init, preferably in a plugin, then convert |
Resolve identifier collisions and rewrite settings first. |
| Repeatable or large migration | WP-CLI inventory plus a site-specific, tested script | There is no documented dedicated conversion command; build rollback and validation into the process. |
Troubleshooting common results
The destination type is missing
Register the type first, confirm that the registration runs on init, and check for a naming collision. Then reload the relevant admin list.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The item saves but its page is missing
Inspect the new permalink, confirm the type’s rewrite and public-query settings, and refresh Settings > Permalinks. Check that the destination single template exists and add a redirect if the URL changed.
Fields or taxonomies disappeared
Compare the destination type’s registered supports, taxonomy assignments, and metabox rules with the source type. The switcher’s stated taxonomy preservation does not make unrelated plugin fields or theme logic automatically compatible.
Bulk conversion causes unexpected behavior
Stop the batch, restore the backup or reverse the tested IDs, identify the conflicting plugin or template, and retry on staging with a smaller set. The plugin listing specifically warns that conflicts can occur.
The Bottom Line
Use Post Type Switcher for a cautious, small-batch reassignment of existing content, and treat custom post type registration as a separate development task. Back up first, test before scaling up, and validate URLs, templates, taxonomies, metadata, permissions, and integrations after every conversion.
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.
