DeepakNess

Bulk Classic to Block is a powerful WordPress plugin designed to help you seamlessly migrate from the Classic Editor to the Gutenberg Block Editor. If you’ve upgraded to WordPress 5.0+ and have existing content created with the Classic Editor, this plugin automates the conversion process, saving you hours of manual work.
The Problem: 
When you upgrade to WordPress 5.0+, all your existing Classic Editor content gets wrapped in a “Classic” block. To properly convert this content to individual Gutenberg blocks, you would normally need to edit each post manually and click “Convert to Blocks” – a tedious process if you have hundreds or thousands of posts.
The Solution: 
Bulk Classic to Block automates this entire process. It scans your entire site, identifies all classic editor content, and allows you to convert everything to proper Gutenberg blocks with just a few clicks.
Key Features: 
* Universal Post Type Support – Works with posts, pages, and all custom post types 
* Smart Scanning – Automatically detects classic editor content across your entire site 
* Flexible Conversion – Convert all content at once or select specific posts to convert 
* Post Type Filtering – Filter and convert by specific post types (posts, pages, or custom types) 
* Status Filtering – Filter by post status (published, draft, scheduled, private) 
* Individual Control – Convert posts one at a time or use bulk actions 
* Automatic Indexing – New content is automatically indexed as you create it 
* Safe & Efficient – Uses WordPress core APIs for reliable conversion
How It Works: 
1. Scan – The plugin scans your content to identify posts created with the Classic Editor 
2. Review – View a detailed list of all posts that need conversion, organized by post type 
3. Convert – Choose to convert all posts at once, or select specific posts using checkboxes 
4. Done – Your classic content is now properly structured as Gutenberg blocks
Perfect For: 
* Sites migrating from Classic Editor to Gutenberg 
* Users with large amounts of existing content 
* Developers managing multiple sites 
* Anyone who wants to modernize their content structure
Important: The conversion process is irreversible. Always create a full backup of your site before converting content. We recommend testing on a staging site first.

Bulk Classic to Block


This worked great. I liked the way that before it did any work it showed me which posts it was going to work on AND let me do individual posts first as a test. It made me feel a lot more comfortable about proceeding.


It let me work with confidence

Convert classic editor content to Gutenberg blocks in bulk. Supports all post types including custom post types.

migrate

nick843

Try it out on your free dummy site: Click here => <a href="https://tastewp.com/plugins/wp-clone-by-wp-academy" rel="nofollow ugc">https://tastewp.com/plugins/wp-clone-by-wp-academy</a>. 
(this trick works for all plugins in the WP repo – just replace “wordpress” with “tastewp” in the URL)
WP Clone is a great way to backup, migrate or clone a WordPress site to another domain or hosting server.
You can also use it to backup, migrate or clone your site to/from local server hosting, to create backup of your site for development or testing purposes, and to install pre-configured backups of WordPress.
WP Clone is a superior to other backup & migrate plugins for the following reasons:
<ul>
<li>It does not require FTP access to backup files you migrate or clone, neither the source or destination site; just install a new WordPress on the destination site, install our backup plugin, and follow the prompts to migrate or clone your site.</li>
<li>It does not backup or restore the WordPress system files (it just creates user content and database backups); reducing upload time for migration and improving security of your site</li>
<li>It fetches the site backup via your host’s direct http connection, which saves you from having to upload large backup files, making it easier to migrate.</li>
</ul>
<h4>What are today’s limitations?</h4>
Today:
<ul>
<li>90% of cases: Backups & migrations work flawlessly (we fixed some key bugs in the most recent version)</li>
<li>9% of cases: Backups or migrations fail due to your hoster’s configurations (most likely limits in up- and downloads) which is typically the case when you backup or migrate very large sites. However, there’s a workaround: simply do a “Database Only” backup (use “Advanced Settings”), transfer the wp-content directory over with FTP, and then restore new site. Then backup and migration also works.</li>
<li>1% of cases: Your site/hosting is abnormal (pardon our French) and backup or migration doesn’t work. However: that’s what we’ll now be working on, so that eventually backups and migrations will work in all cases.</li>
</ul>
The 1% case means:
<ul>
<li>Basic rule: DO NOT use it as your only backup solution! Only use it for migrations (so that if something fails, you still have the files on your old site as backup).</li>
<li>If you want to use it as backup, test it by restoring the backup file on a new site. If that works fine you should be safe.</li>
<li>In any case, we cannot take any responsibility if backup or migration fails.</li>
</ul>
Note: 
* There is never an issue in damaging the source installation (i.e. on the site where you create the backup). So backup sites at your pleasure. If your backup succeeds then chances are good that the migration (i.e. restore on another site) will also succeed. But don’t take any chances. 
* If backup or migration (restore) fails, just try it again. Often it works on second attempt.
<h4>Other tips how to backup and migrate</h4>
<ul>
<li>NEVER overwrite an installation for which you do not have an alternate backup source (e.g. a cPanel backup). Normally you would restore the backup onto a fresh WP installation on another host or on a subdomain. If the restore fails your destination site might become unusable, so be prepared to enter cPanel and then destroy / recreate the new installation if necessary.</li>
<li>DO NOT use our backup plugin on WP Engine or any hosting system with proprietary operating system. Instead, use their built-in backup tools.</li>
<li>Large sites (>2GB) might take as long as an hour to backup and migrate. Sites of 250 MB or less should take no more than a minute or two to backup, depending on your server.</li>
<li>We recommend you deactivate and delete page caching, security and maybe redirection plugins before you migrate, and re-install them on the new site, if necessary. In general, delete all unnecessary plugins and data from your site before you backup. You can also use the “Exclude directories” option if you have large media files, which you can then copy back to the new site with FTP.</li>
<li>How to copy from local server to your hosted website: Create a backup of the local site in the usual way, then save the backup file (right-click > Save) to your local disk. Upload this file to the root directory of your destination website and then use this url in the “Restore” dialog of the new site: http://yourdomain.com/.</li>
</ul>
<h4>Help Video</h4>
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/xN5Ffhyn4Ao?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
<h4>Credits</h4>
WP Clone uses functions from the “Safe Search and Replace on Database with Serialized Data” script first written by David Coveney of Interconnect IT Ltd (UK) http://www.davidcoveney.com or http://www.interconnectit.com and released under the WTFPL http://sam.zoy.org/wtfpl/. Partial script with full changelog is placed inside ‘lib/files’ directory.
This plugin is part of the Inisev product family – <a href="https://inisev.com" rel="nofollow ugc">check out our other products</a>.

Bulk Classic to Block vs Clone