Custom Packages Do Not Migrate

Hi @escwebs,

Thank you for reaching out.

I understand you’re facing an issue with custom packages. Looking at a similar issue here, the merchant was able to migrate the data without having any issues. Do you mind giving this another try to check if the issue persists?

You can also find more suggestions from this thread here.

Let us know how this goes.

LOL, the thread you referred me to is … me.

That is a different issue: the migration of shipping history and tracking numbers. As mentioned above and in the previous thread of mine you referred to, that’s working fine.

Keeping support issues separate, this is a new issue:

When preparing a shipment, the custom packages I’d added previously under WooCommerce Shipping & Tax did not migrate to the new WooCommerce Shipping plugin.

Thanks,

Mike

Hi @escwebs

When preparing a shipment, the custom packages I’d added previously under WooCommerce Shipping & Tax did not migrate to the new WooCommerce Shipping plugin.

It seems like this issue might be the same as the previous one. Could you give the migration tools another shot and let us know if there’s any change?

Let us know how that goes. Looking forward to helping you.

@escwebs, would you be able to tell us where you are looking for your migrated packages? Saved packages have moved to the label purchase screen under the section “Saved Templates”.

Can you confirm if you are seeing your packages there?

Another thing to confirm is if your migration has completed, ie are you still seeing a message indicating that the migration is in progress? Depending on how many labels you have to migrate it can take a while to migrate everything over.

–

• This reply was modified 2 months, 2 weeks ago by grangep. Reason: wrong thread

Yes, as mentioned in my original post, none of the custom package types I had saved under WooCommerce Shipping & Tax migrated to the new Saved Templates feature of WooCommerce Shipping. They did not migrate to the Saved Templates section of WooCommerce Shipping.

Yes, migration was complete.

There does not appear to be a way to run the migration process again once it has completed. Not that I can find anyway. If there is a way to re-run the migration, I’ll happily attempt it.

That’s okay. I’ll hold off upgrading client sites until this issue is resolved in a future release. Although if there isn’t a way to re-run the migration…I’m not sure how I would know that it’s fixed?

Thanks,

Mike

Hi @escwebs,

At the time there’s no option to re-run the migration. Thank you for bringing this to our attention. Our developers are actively monitoring these forums for feedback to improve this new version of the plugin.

In the meantime, considering the issue you’re currently facing, it’s best to keep using the original plugin on your customer’s sites. We’ll keep you posted with the latest developments so you can test this again later.

Thanks!
-OP

Follow Up:

1) I restored my database from prior to the migration so I would be prompted to migrate once again.

2) I installed the latest version of WooCommerce Shipping 1.1.2

3) I installed the latest version of WooCommerce Shipping & Tax 2.8.1

4) I activated WooCommerce Shipping and then click the button to initiate the migration.

5) Migration completed with the following message:

“Your shipping settings and label history have been successfully migrated — enjoy the new WooCommerce Shipping experience.”

Unfortunately, once again, my custom package types created under WooCommerce Shipping & Tax did NOT migrate to the new Saved Templates feature of WooCommerce Shipping.

As is, the migration of custom package types originally created under “WooCommerce > Settings > WooCommerce Shipping > Packaging” does not appear to work as it should. These custom package types do not appear within the new Saved Templates feature after migration.

I’ll test again with future releases if the changelog indicates a potential fix, but it will be critical for this to work correctly for my clients who depend upon the custom packages they created to be there, so I agree with @omarfpg, we’ll stick with WooCommerce Shipping & Tax for now.

Thanks,

Mike

Hello escwebs,

Thank you for conducting this test and sharing the results with me.

I will share these findings with our development team for further investigation.
In the meantime, I agree that sticking with WooCommerce Shipping & Tax is the best approach until we have a fix in place.

Best regards.