Isamu Takeda

<p>This plugin provides the ability to migrate individual WordPress post data to another WordPress site.<br />
Specifically, it provides the following features that are not provided by the standard import and export tools provided by WordPress.<br />
1. The standard tool does not export images and other media data. Instead, the importer reads the image URL in the XML and attempts to re-download the file from a remote location. However, this requires that the import source site is public and the media file URL is accessible. If the site is local or private, the media download will fail and only an empty attachment post will be created.<br />
This plugin extracts images and other media data and WordPress database information and exports them together in a single ZIP file, eliminating such problems.<br />
2. The standard tool does not export revisions, but this plugin provides export and import functions.<br />
3. The standard tool allows you to select what to export for each post type, but not for each individual post.<br />
This plugin allows you to select what to export for each individual post.</p>
<h3>Related Links</h3>
<ul>
<li><a href="https://github.com/itmaroon/post-migration" rel="nofollow ugc">POST MIGRATION:Github</a></li>
<li><a href="https://github.com/itmaroon/block-class-package" rel="nofollow ugc">block-class-package:GitHub</a>  </li>
<li><a href="https://packagist.org/packages/itmar/block-class-package" rel="nofollow ugc">block-class-package:Packagist</a> </li>
<li><a href="https://github.com/itmaroon/wpsetting-class-package" rel="nofollow ugc">wpsetting-class-package:GitHub</a>  </li>
<li><a href="https://packagist.org/packages/itmar/wpsetting-class-package" rel="nofollow ugc">wpsetting-class-package:Packagist</a></li>
</ul>
<h3>Arbitrary section</h3>
<p>PHP class management is now done using Composer.<br />
<a href="https://github.com/itmaroon/block-class-package" rel="nofollow ugc">GitHub</a><br />
<a href="https://packagist.org/packages/itmar/block-class-package" rel="nofollow ugc">Packagist</a></p>
<h3>Third Party Libraries</h3>
<p>This plugin uses the following third-party libraries:</p>
<h3>FileSaver.js</h3>
<ul>
<li>Purpose: Used to enable client-side file saving functionality (e.g., downloading generated ZIP files in the browser).</li>
<li>Library URL: https://github.com/eligrey/FileSaver.js/</li>
<li>License: MIT License</li>
<li>Resources : https://github.com/eligrey/FileSaver.js</li>
</ul>
<p>Copyright (c) 2016 Eli Grey.</p>
<p>Permission is hereby granted, free of charge, to any person obtaining a copy<br />
of this software and associated documentation files (the “Software”), to deal<br />
in the Software without restriction, including without limitation the rights<br />
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell<br />
copies of the Software, and to permit persons to whom the Software is<br />
furnished to do so, subject to the following conditions:</p>
<p>The above copyright notice and this permission notice shall be included in<br />
all copies or substantial portions of the Software.</p>
<p>THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR<br />
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,<br />
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE<br />
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER<br />
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,<br />
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN<br />
THE SOFTWARE.</p>
<h3>JSZip</h3>
<ul>
<li>Purpose: Used to create ZIP files directly on the client side in the browser.</li>
<li>Library URL: https://github.com/Stuk/jszip</li>
<li>License: MIT License</li>
</ul>
<p>Copyright (c) 2009-2022 Stuart Knightley, David Duponchel,<br />
          Franz Buchinger, António Afonso</p>
<p>Permission is hereby granted, free of charge, to any person obtaining a copy<br />
of this software and associated documentation files (the “Software”), to deal<br />
in the Software without restriction, including without limitation the rights<br />
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell<br />
copies of the Software, and to permit persons to whom the Software is<br />
furnished to do so, subject to the following conditions:</p>
<p>The above copyright notice and this permission notice shall be included in<br />
all copies or substantial portions of the Software.</p>
<p>THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR<br />
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,<br />
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE<br />
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER<br />
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,<br />
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN<br />
THE SOFTWARE.</p>


POST MIGRATION

This is a plugin that transfers data for individual posts to another WordPress site.

Plugin Atlas

<h4>Official WooCommerce 9.6 Brand Migration Tool</h4>
<p><strong>With WooCommerce 9.6 launching on January 20th, 2025, all stores will have the Brands feature enabled by default.</strong> This creates a migration challenge for stores that already use brand attributes – your existing brand data won’t automatically transfer to the new system.</p>
<p>Transfer Brands for WooCommerce provides the missing link that WooCommerce doesn’t offer – a safe, reliable way to migrate all your existing brand attributes (both taxonomy-based and custom) to the new WooCommerce 9.6 brand taxonomy without losing any data.</p>
<p>Unlike manual migration that risks data loss, our plugin:<br />
* Preserves all brand relationships and hierarchies<br />
* Transfers brand images automatically<br />
* Provides complete backup and rollback functionality<br />
* Shows real-time progress with detailed statistics<br />
* Handles stores of any size with batch processing</p>
<p>Transfer Brands Enhanced for WooCommerce is a powerful tool that simplifies the process of migrating your product brand attributes to a dedicated product_brand taxonomy. This is particularly useful for store owners who want to improve their brand management and enhance storefront navigation.</p>
<h3>Key Features</h3>
<ul>
<li><strong>User-friendly Interface</strong>: With an intuitive admin interface showing real-time progress during transfers.</li>
<li><strong>Universal Image Transfer</strong>: Automatically detects and transfers brand images from 30+ different themes including Woodmart, Porto, Flatsome, XStore, Electro, and more.</li>
<li><strong>Theme Compatibility</strong>: Full support for popular WooCommerce themes – your brand images will transfer regardless of which theme you use.</li>
<li><strong>Custom and Taxonomy Attribute Support</strong>: Works with both custom and taxonomy-based brand attributes.</li>
<li><strong>Batch Processing</strong>: Process products in batches to avoid timeouts on large stores.</li>
<li><strong>Backup System</strong>: Built-in backup and rollback functionality for risk-free transfers.</li>
<li><strong>Analysis Tool</strong>: Analyze your brands before transfer to identify potential issues.</li>
<li><strong>WooCommerce Integration</strong>: Automatically uses the brand permalink settings from WooCommerce.</li>
<li><strong>HPOS Compatible</strong>: Fully compatible with WooCommerce High-Performance Order Storage.</li>
<li><strong>ACF Support</strong>: Works with Advanced Custom Fields brand images.</li>
<li><strong>Detailed Logging</strong>: Comprehensive logging for troubleshooting (in debug mode).</li>
</ul>
<h3>Use Cases</h3>
<ul>
<li>You want to migrate your brand attributes to prepare for WooCommerce 9.6 update</li>
<li>You need to replace an existing brand attribute with a proper taxonomy for better store organization</li>
<li>You want to improve your store’s SEO by using proper brand taxonomy pages</li>
<li>You need to implement brand filtering on your shop pages</li>
<li>You want to consolidate different brand attributes into a single taxonomy</li>
</ul>
<h3>Why Use a Brand Taxonomy?</h3>
<p>Converting your brand attributes to a taxonomy offers several advantages:</p>
<ul>
<li>Better SEO with dedicated brand archive pages</li>
<li>Enhanced filtering options in your store</li>
<li>Simplified brand management</li>
<li>Ability to add additional brand metadata (like logos, descriptions, etc.)</li>
</ul>
<h3>Additional Information</h3>
<h4>How to test before transferring</h4>
<p>Before running a full transfer, we recommend:</p>
<ol>
<li>Using the “Analyze Brands” function to check your data</li>
<li>Ensuring you have a recent database backup</li>
<li>Testing on a staging site if possible</li>
<li>Verifying that the backup feature is enabled in settings</li>
</ol>
<h4>Transfer Process</h4>
<p>The transfer process operates in three phases:</p>
<ol>
<li><strong>Backup</strong>: Creates a backup of existing brand data</li>
<li><strong>Terms Transfer</strong>: Creates or maps taxonomy terms</li>
<li><strong>Product Assignment</strong>: Associates products with the new taxonomy terms</li>
</ol>
<h4>After Transfer</h4>
<p>After completing a transfer, you can:</p>
<ul>
<li>Keep both the old attribute and new taxonomy (default)</li>
<li>Remove the old brand attribute data (optional)</li>
<li>Further customize your brand taxonomy</li>
</ul>
<h4>Support</h4>
<p>For support requests, please use the WordPress.org support forums.</p>


Transfer Brands for WooCommerce

Migrate brand attributes to WooCommerce brand taxonomy with backup, image transfer, and progress tracking.

POST MIGRATION vs Transfer Brands for WooCommerce