Migrating from WooCommerce to Classic Commerce

Projects Ecosystem
11

Yeah, that filter disables the new analytics and marketing features. It seems crazy you can’t disable this from WC settings. Plus, because the filter is called before the theme is loaded, you have to create a separate plugin with just that bit of code in. Adding it to functions.php won’t work. Apparently…

1 Like
12

Yes, this is the case. No good in functions.php. No good in a snippet plugin. Has to be in its own separate plugin. :roll_eyes:

2 Likes
13

I’m sure it was calculated. That code also hides the new top level “Marketing” menu item which looks like a place purely for pushing Woo commercial products.They don’t want to make it too easy for you to hide that little gold mine.

4 Likes
14

I’m not using a commerce plugin at this time, but, just wanted to say that I greatly appreciate all the time, effort, research, discussion (and so much more) that you’ve all put into the project. Really great work!

7 Likes
15

Just to summarise what I have found so far… there are four main areas of change to the database in WooCommerce 4.x

  1. New tables created for the action scheduler.
    actionscheduler_actions
    actionscheduler_claims
    actionscheduler_groups
    actionscheduler_logs
    Note that plugins (eg WooCommerce Subscriptions) may start to make use of these tables for their procedures.

  2. New tables created for the WooCommerce Admin reporting features
    wc_admin_note_actions
    wc_admin_notes
    wc_category_lookup
    wc_customer_lookup
    wc_order_coupon_lookup
    wc_order_product_lookup
    wp_wc_order_stats
    wc_order_tax_lookup

  3. A new table created for handling reserved stock (managing stock levels for items that may be currently in the checkout process) - wc_reserved_stock
    More details here: Reserved Stock in WooCommerce 4.3 Explained | Puri.io

  4. A change to an existing table - wc_product_meta_lookup
    This has 2 new columns added - tax_status and tax_class
    See: Add product lookup table tax columns by mikejolley · Pull Request #25428 · woocommerce/woocommerce · GitHub
    It also has a change to two existing column definitions
    min_price decimal(10,2) DEFAULT NULL and max_price decimal(10,2) DEFAULT NULL
    becomes
    min_price decimal(19,4) DEFAULT NULL and max_price decimal(19,4) DEFAULT NULL
    See: Need to change `wc_product_meta_lookup` table structure datatype size for min_price and max_price · Issue #24428 · woocommerce/woocommerce · GitHub

6 Likes
16

@Web242 - Are you going to be migrating from WooCommerce to CC, or starting from scratch. If you are migrating, what version of WC are you currently using?

1 Like
17

Hi @ozfiddler I would defintely prefer to migrate, in order to retain customer orders and information. But it’s not the end of the world if I redo.

WC Version 4.4.1

My plan is to simplify everything, so we’ll get rid of the subscriptions etc. and just keep simple orders and existing products.

1 Like
18

OK, then you’ll be wanting to follow this discussion: Migrating from WooCommerce to Classic Commerce

and also the CC channel on Slack. I’m trying to get my head around it all at the moment.

Simplify is good! :smiley:

1 Like
19

@ozfiddler Yeah I hear you! WordCommerce is complicated enough. I suspect most of the new stuff, is for their marketing addons and Gutenberg blocks. I suspect there are not huge changes to the db tables/schema - but there have been db updates on WC upgrades.

I’ll go check out your post!

1 Like
20

@ozfiddler What is the Slack channel?

21

I think that gets there. It’s classic-commerce in the CP slack account.

22

From what we’ve seen so far, this is correct.

It looks to me like any real problems would most likely come into play only if you migrate Woo → CC then upgrade back to latest Woo. However in the interest of full disclosure this process does need more testing.

Slack (also linked to from the bottom of this page, or on our main site)

Please be sure to use that link when inviting people to Slack, since that’s pretty much the only way to guarantee that users who don’t yet have an account will be able to create one.

1 Like
23

@james and @ozfiddler This is an important discussion on ClassicCommerce. Let’s split this into another topic from:
https://forums.classicpress.net/t/looking-to-make-the-switch/2438/10?u=web242

I’m not a developer, but we have quite a few clients using WooCommerce now, and I feel every-time we update we are going down the path of no return.

I hope you can keep the migration from WC to CC for some time, but I also worry once it goes into “block-mode” it’s game over. I don’t think I will ever roll-back.

24

Yes, I know what you mean. I have the same feeling with my two remaining Woo sites. I was relieved to find that the database changes wouldn’t affect my sites, but this is something you need to assess for yourself. Creating new tables wasn’t really a concern, but when they start modifying existing tables it could start to impact us.

I hope so too. We’ll certainly be working on this.

What are their situations regarding plugin and extension usage? This will obviously be the main area to watch. It will be the same story as CP… as long as plugins work with WC version 3.5.3, they should work with CC. But I would be avoiding any official WooCommerce products. :slightly_smiling_face:

1 Like
25

Well therein lays the problem. My clients and I are using official WC plugins. For them they will have to stay with WP and WC, I dont see any other choice. Unless they reach the point of frustration with it all.

But to answer your question, WooCommerce Subscriptions is the most important one, and with Stripe gateway. If CC could have subscriptions option, even rudimentary, that would be very good.

The way I see it, if I build a CP and CC site from the start, it’s a non-issue.

I think it wont be long before WC and WP become divergent from, CC and CP. I dont think you have to sweat supporting WC plugins - that is too much to ask.

What you have done, is given CP users a solid eCommerce option with CC.

2 Likes
26

Scrap that… seems like the plugin I was going to recommend has moved to WP5+

2 Likes
27

It means, that

  1. You should ask plugin developers to support CP.

  2. If rejected - fork the plugin or put it on the “WP plugins should be ported to CP” list and wait, until someone wants to take care of it.

Oh, wait. We don’t have a “WP plugins should be ported to CP” list? A major lapse. It raises the question of where and how it should be created and how promoted to the potential plugin developers.

1 Like
28

Business opportunity here: an agency with specific experience in WP → CP migrations. Sounds like a good one :wink:

1 Like
29

@james I like that idea!

1 Like
31

Hi Y’all!

Great Project! Thank you for your efforts…

I tried with use-wp-language-plugin and searched but didn’t find a way to get CC running with german language formal. Did I miss something?

I really would love to switch from WP/WC to CP/CC and get away from the growing annoyance but don’t be able to run the shop in german would be a showstopper :frowning:

Any help very appreciated…

2 Likes