Support

Home Forums Event Espresso Premium Compatibility and migration questions

Compatibility and migration questions

Posted: March 8, 2019 at 4:42 pm


Matrixparents

March 8, 2019 at 4:42 pm

Our current website uses WP 4.8.3 with Event Espresso 3.1.37.12P and Event Espresso-Calendar 2.2.7p. We have trainings booked through May 2019. We hope that by May 1 we will be going live with a new WP5 website.

Can we update the EE and EECalendar on our current (somewhat delicate) website to 4 without technical problems? Or should we purchase a new EE4 plugin and calendar addon, put it on the new website and migrate events over from old site using EE3? BTW is migration easy for low tech folks?

We don’t want people to be bounced out of events and have limited resources.
What do you recommend? thanks…Angela


Tony

  • Support Staff

March 11, 2019 at 5:35 am

Hi Angela,

Can we update the EE and EECalendar on our current (somewhat delicate) website to 4 without technical problems?

Whilst a migration from EE3 to EE4 is generally pretty smooth (we have migration scripts build into EE3 to pull over as much info from you EE3 tables into EE4 as we can) the ‘somewhat delicate’ comment is a little worrying. If customizations have not been made within EE3 and the features of EE3 have been used as they were intended to be then the migration should work fine.

However, we recommend that you create a development copy of the site and run migration there just to confirm everything works first. The reason for this being that if you run it on your live site and find there is an issue, its then a panic to get everything fixed up, which with limit resources can be frustrating for yourselves, or expensive if you need to pay for support tokens (or another developer) to quickly dig in and troubleshoot.

Or should we purchase a new EE4 plugin and calendar addon, put it on the new website and migrate events over from old site using EE3? BTW is migration easy for low tech folks?

You have access to EE4 with your current license, all EE3 license holders do as eventually, we’d like for all EE3 users to migrate over to EE4, having access to both gives you the opportunity to test it and see when it suits your needs (for example EE4 doesn’t support ‘recurring events’ at this time, so EE3 is often a better fit for those user).

Migration from EE3 is just following the on screens instructions which is basically just, click to start a migration step, click to accept it has finished that step and click to start the next step until they are all complete (if there’s an Error, EE will tell you and you can send us a report to review).

Again, we recommend you do this on a development copy (a clone of your live site) first just to confirm it all works and that your events still work afterwards.

—-

If I may. I have a question from the above, you mentioned this:

We hope that by May 1 we will be going live with a new WP5 website.

You’ve mentioned ‘new WP5 website’ there, so is that currently a different site to the site you have EE3 installed on? If so how are you planning on pulling the event data from EE3 to the new site?


Matrixparents

March 11, 2019 at 2:03 pm

Hi Tony,

Thank you for all of your helpful responses. We will be looking them over and talking with the folks who are developing our new site. Yes, the new WP5 site is still a development site and EE3 is on our current (active) site. I call the site delicate because it’s old and in need of much more than a facelift…which is why it is being rebuilt. It sounds like the best way to migrate the events would be to have the developers of the new site do it on their development site.

I notice that our renewal is coming up March 16. What do you recommend? should we update to EE4 and renew that way (on our current site)? Or should we renew EE3 on our current site, put EE4 on the new site, and have the developers migrate the EE3 calendar to the new development site?

Our families in the Special Needs community depend on being able to register for our events and it’s critical that we don’t have a break in website registration service. While we are fortunate to have help with developing a new website, we do not have any in-house tech support and have limited help from the developers. That’s why I want to be clear before moving forward.

I appreciate your help and your thoughtful responses. I still need to review them with others in the office tomorrow. We will follow your recommendations so our transition will be smooth. Please send your thoughts regarding the best way to migrate our events. Thanks so much…Angela


Matrixparents

March 12, 2019 at 11:54 am

Hi Tony,
I was searching to find out if EE3 will work with WP5. I found a one word response on a blog site (not your forum) where someone asked if Event Espresso 3 works with WordPress 5 and another person responded said “yes”. However, I’m not sure if they were from EE support or not.

Does EE3 work with WP5? What about the Event Espresso-Calendar 2.2.7 that we are using along with EE 3.1.37.12P? Do we need to update that to 3? Will both work with WP5?

You have made have changes EE3 and EE4. I believe the Calendar plugin was included when we started using EE. I’m just trying to understand what we can do that is the most economical and also the most reliable. As a nonprofit we need both economy and reliability to continue serving our community.

thanks
Angela


Tony

  • Support Staff

March 13, 2019 at 5:24 am

I call the site delicate because it’s old and in need of much more than a facelift…which is why it is being rebuilt.

Ok, so did you have any custom work done on EE3 at all or is all default?

It sounds like the best way to migrate the events would be to have the developers of the new site do it on their development site.

Do you have ‘active’ events?

Meaning events that you MUST migrate over from EE3 with current registrations etc?

If so the new site will need all the event data moved over to it, then migrated to EE4, however that’s going to need to be done as the very last step to prevent you from losing registrations. For example, if you copy the EE3 tables over today, migrate the new site over to EE4 and then don’t launch the new site for 2 weeks, the registrations made on the old site between now and when you launch will be ‘lost’ (they will be on the old site but you can not migrate them over).

I notice that our renewal is coming up March 16. What do you recommend? should we update to EE4 and renew that way (on our current site)? Or should we renew EE3 on our current site, put EE4 on the new site, and have the developers migrate the EE3 calendar to the new development site?

Ok, my advice for the current site is to NOT migrate over to EE4 on that site. You can’t easily pull the events/registration etc from EE4 on one site onto another, so you currently have a working EE3 site, don’t migrate that over and then try to migrate that to the new site, it’s just not going to work smoothly, especially with limited resources.

With regards to renewal, I’d recommend discussing your options with our sales team. As your current license gives you access to both EE3 and EE4 you may find renewing your current license fits best.

Our families in the Special Needs community depend on being able to register for our events and it’s critical that we don’t have a break in website registration service. While we are fortunate to have help with developing a new website, we do not have any in-house tech support and have limited help from the developers. That’s why I want to be clear before moving forward.

So do you not have any breaks in your events at all?

Whilst it is possible to migrate EE3 to EE4 it’s going to take some planning and testing to confirm everything works on your new site. As your taking live registrations in EE3 at this time you’ll need to get everything ready, close registrations on the EE3 site, pull the EE3 tables to the new site, activate EE4 to migrate over, run through all of the migration steps and then open registrations again.

You mentioned its critical there is no break in the registration service, however, your not just switching from one version of EE3 to another, your switching to both a new site and a completely different event registration system (EE3 works differently to EE4) so you are going to have some downtime, though with planning you can keep that minimal.

The alternative is you’ll lose registrations as once you’ve migrated the data from EE3 to EE4 on the new site, it can’t be done incrementally after that. So registrations made on the old site with EE3 cannot be migrated to the EE4 site automatically, but you can do it manually at a push (that’s not going to be fun if you have a large gap between the migration and the switch).

So the steps I would take are:

Old site = the current EE3 site.
New site = the new site which you want to be running EE4 on.

#1. Create a full database backup of the new site now, OR create a copy of this new dev site. (IMPORTANT you are creating a copy of the site here, as after you’ve tested below, you want to revert back to this)

#2. Pull all of the _events_ tables (thats th EE3 database tables) from the old site and import them into the new new sites database. (Note – this is not the real migration, you are doing a test run on the current data, running the migration and confirming everything works on the DEV site, leaving the old site to continue to run)

#3. After running the migration on the new site, confirm your events, registration etc all work as expected.

#4. If all works as expected, great, it means the new site should not run into any issues when you run the live migration.

#5. Revert back to before you imported the tables (Note to developer, dropping the EE3 tables here is NOT sufficient, EE4 doesn’t use those tables, it pulls the tables and creates it’s own + muliplte custom post types within _posts, you need to revert for this to be ‘clean).

#6. When your are ready to move over, you close the registrations on the EE3 site, put it in maintenacne mode or whatever, but you need to temporarily close registrations to prevent data loss.

#7. Repull the _events_ tables the old site into the new.

#8. Run the migrations on the new site and confirm it works again.

#9. Open up the NEW site for registrations.

As you can see, this isn’t a simple process an will require planning to get right if you need to keep registrations open (or at least down for a minimal amount of time). Skipping the ‘test’ migration (1-5) could mean on the day you are ready to switch over, nothing works because the migrations fail, so I recommend doing it correctly.

Again, due to the changes you are making, you are going to have some downtime but you can keep it to a minimal.

If I may ask, do you absolutely need the current (and previous) EE3 events or, could you set up a deadline for the events on the current site in which registrations close, then direct users to the new site for registrations after that date? Meaning you can start with a fresh install of EE4 with none current event data from EE3 which may not be an option for you, it depends on the data you need.

Doing it that way will reduce the stresses from above.

Ideally, you need a developer familiar with migrating sites to help with this as there’s a lot of moving parts to get this right.

Does EE3 work with WP5?

We’ve had no reports of EE3 not working on WP5 and I run all of my test sites on the latest versions with no issues.

It is important to note that EE3 is no longer under ‘active’ development and only receives security updates at this time so whilst we do still continue to test it on the latest version of WordPress it does not receive the same amount of testing that EE4 does.

What about the Event Espresso-Calendar 2.2.7 that we are using along with EE 3.1.37.12P?

The latest version of EE3 is v3.1.37.14.P so if you are going to continue to use EE3, you’ll need to use that version.

The calendar version mentioned is the latest version for EE3.

We have no known issues with WP5 on either of those at this time.

Do we need to update that to 3?

Do you mean EE4 here?

We recommend everyone switch to EE4 as EE3 is no longer under active development, however, there are use cases in which EE3 fits better, for example, if you rely on the ‘recurring events’ add-on/features within EE3 then you’ll need to stick with it as EE4 does not support recurring events yet.

(I notice you don’t have REM on your license currently but you may already have the add-on so just covering all bases)

You have made have changes EE3 and EE4. I believe the Calendar plugin was included when we started using EE. I’m just trying to understand what we can do that is the most economical and also the most reliable. As a nonprofit we need both economy and reliability to continue serving our community.

To discuss which is the best fit for you I’d recommend contacting our sales team which can do using this form: https://eventespresso.com/contact/

Your current license gives you access to both EE3 and EE4 + the equivalent add-ons.

  • This reply was modified 6 days, 6 hours ago by  Tony. Reason: Typo, spacing


Matrixparents

March 13, 2019 at 10:18 am

Hi Tony,

Thank you for your complete and thoughtful response to my many questions. It gives us a lot to consider. Now we have a clear idea of how to move forward and can look at our options.

So grateful for your excellent support.
Angela

You must be logged in to reply to this support post. Sign In or Register for an Account

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3

Documentation for Event Espresso 4

Status: publish

Updated by  Matrixparents 6 days, 6 hours ago ago

Topic Tags

Notifications

This topic is:
pending
Do NOT follow this link or you will be banned from the site!