Migrate Attributes from WebShopApps to ShipperHQ for Magento 1
Effortlessly Transition Your Shipping Attributes from WebShopApps to ShipperHQ on Magento 1
Table of Contents
- Overview
- Configuration
- Prerequisites
- Example Migration for Dropship to ShipperHQ
- Deleting WebShopApps Attributes
Overview
😊 If you're moving from WebShopApps stand-alone extensions to ShipperHQ on Magento 1, we have a handy tool to help set up your catalog's configuration. The Migration Manager, available on Github, maps your existing WebShopApps product attribute values to your selected ShipperHQ configuration values. This article explains how to use the Migration Manager effectively.
Configuration
The Migration Manager tool currently supports migration from:
- Dropship
- Product Matrix
- Shipping Override
- Freight modules
💡 If there are other extensions you'd like to use this tool with, please let us know. For example, if you have been using Dropship from WebShopApps and are moving to ShipperHQ, you can use the Migration Manager to ensure all products previously assigned to a warehouse will be assigned to a ShipperHQ Origin (warehouse) you choose.
Prerequisites
- ShipperHQ installed in Magento
- You've configured your Origins and Shipping Groups in ShipperHQ
- You have synchronized your Magento site with ShipperHQ
Example Migration for Dropship to ShipperHQ
- Go to Catalog > ShipperHQ > Migration Manager
- The migration dialog will list each warehouse you have created for Dropship. For each warehouse, select a value for ShipperHQ Origin
- Click Migrate
- This will assign every product with a warehouse value of "New York Warehouse" from Dropship to a ShipperHQ Origin value of "New York"
- Similarly, this will assign every product with a warehouse value of "California Warehouse" from Dropship to a ShipperHQ Origin value of "California"
- Once the migration is complete, you will see how many products have been updated
Deleting WebShopApps Attributes
⚠️ If you need to delete WebShopApps attributes, we recommend doing this from the Magento admin for a clean removal. If the delete capability is not available for an attribute, ask your developer to update the attribute in the eav_attribute
table, setting user_defined
to 1. You can then delete it from the admin. Please proceed carefully, as we are not responsible for any mishaps.