Support

Home Forums Event Espresso Premium Migrating data from EE3 to EE5

Migrating data from EE3 to EE5

Posted: April 16, 2024 at 7:46 am


tgcc

April 16, 2024 at 7:46 am

Hi,
I’m trying to upgrade my EE install from 3.1.37.8.P to 5.0.19.p. After deactivating the old plugin, and activating the new one, the migration UI appeared, but only copied across one event (‘Test Event 1’), and no attendee data. How do I move the data over to the new tables?
Thanks!


Sam

  • Support Staff

April 16, 2024 at 10:42 am

Hi There,

You can follow the migration process here to migrate from EE3 to EE5: https://eventespresso.com/wiki/how-to-upgrade-event-espresso/#update-event-espresso-4

Hope that helps.


tgcc

April 16, 2024 at 10:55 am

Sam, thanks for your swift response, but reading the documentation was the first thing that I did. If you take another look at my message, you’ll find that I followed the instructions in your link already (the steps under the heading “Complete the Migration”) but having completed the steps, EE5 only has one event called ‘Test Event 1’, whereas if I disable EE5 and re-enable EE3, all of my actual events are still there.

I tried dropping all the new wp_esp_ tables and starting again, to the same effect. My existing EE3 data is in wp_events_ tables in the DB. Do you have any more helpful suggestions?


Sam

  • Support Staff

April 16, 2024 at 11:53 am

Can you please share the login so that we can check: https://eventespresso.com/send-login-details/


tgcc

April 16, 2024 at 12:01 pm

Hmmm. I think the only way to find that out would be to read my first message again, Sam.


Sam

  • Support Staff

April 16, 2024 at 12:14 pm

Sorry for the confusion above.

Can you please reset EE4 again and click to activate it once again, can you add a screenshot of the next page you see on that page here, please?

https://eventespresso.com/wiki/troubleshooting-checklist/#screenshots

Make sure to keep a database backup before migration.

Looking forward to helping you.


Tony

  • Support Staff

April 16, 2024 at 1:42 pm

Hi there,

Have you previously installed ee4 to test it out before?

It sounds like the EE4 -> EE5 migration may have triggered, which will happen if you’ve previously installed EE4.

We can walk through resetting EE4/5 to retrigger the migrations if that’s the case.


tgcc

April 16, 2024 at 3:24 pm

It sounds like the EE4 -> EE5 migration may have triggered, which will happen if you’ve previously installed EE4

Thank you. This sounds likely. How can I reset to a pre-EE4/5 state?


Tony

  • Support Staff

April 16, 2024 at 4:09 pm

Backup your database before moving forward (these steps drop tables, if something goes wrong the only way you’ll be able to get that data back is if you have a backup, so please don’t skip backing up).

Activate the latest version of EE4/5 you have installed.

Go to Dashboard -> Event Espresso -> Maintenance -> Reset/Delete Data.

Hit the ‘Permanently Delete ALL Event Espresso Data’.

EE will wipe all related EE4+ data and deactivate.

Re-acitvate it again and it should trigger the EE3 migrations.


tgcc

April 16, 2024 at 4:16 pm

Well, that didn’t go very well:

“Data Migration Error
Your last Database Update had a fatal error and was halted.
Internal Server Error”

I used the form on the page this message was shown to send in the crash report.


Tony

  • Support Staff

April 16, 2024 at 4:21 pm

This reply has been marked as private.


tgcc

April 16, 2024 at 4:37 pm

Tragically, activating that version of EE4 causes the fatal “critical error on this website” error. I’m running PHP 8.3, I’m able to downgrade to 8.1 at the earliest. Would that help?


Tony

  • Support Staff

April 16, 2024 at 5:11 pm

I need to know what the fatal is to be able to answer.

Do you have the full error? It will usually be saved in the server’s PHP error logs.


tgcc

April 17, 2024 at 4:05 am

Deprecated: Return type of EventEspresso\core\services\container\RegistryContainer::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /httpdocs/wp-content/plugins/event-espresso-core-reg/core/services/container/RegistryContainer.php on line 68

Deprecated: rtrim(): Passing null to parameter #1 ($string) of type string is deprecated in /httpdocs/wp-includes/formatting.php on line 2831

Deprecated: rtrim(): Passing null to parameter #1 ($string) of type string is deprecated in /httpdocs/wp-includes/formatting.php on line 2831

Deprecated: rtrim(): Passing null to parameter #1 ($string) of type string is deprecated in /httpdocs/wp-includes/formatting.php on line 2831

Deprecated: rtrim(): Passing null to parameter #1 ($string) of type string is deprecated in /httpdocs/wp-includes/formatting.php on line 2831

Deprecated: Creation of dynamic property EE_DMS_4_1_0_shortcodes::$_old_table is deprecated in /httpdocs/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/4_1_0_stages/EE_DMS_4_1_0_shortcodes.dmsstage.php on line 14

Deprecated: Creation of dynamic property EE_DMS_Core_4_1_0::$_new_table is deprecated in /httpdocs/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php on line 798

Deprecated: Creation of dynamic property EE_DMS_Core_4_1_0::$_old_table is deprecated in /httpdocs/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php on line 798

Deprecated: Creation of dynamic property EE_DMS_4_1_0_org_options::$_new_table is deprecated in /httpdocs/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Stage.core.php on line 126

Deprecated: Creation of dynamic property EE_DMS_4_1_0_org_options::$_old_table is deprecated in /httpdocs/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Stage.core.php on line 126

Deprecated: Creation of dynamic property EE_DMS_4_1_0_shortcodes::$_new_table is deprecated in /httpdocs/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Stage.core.php on line 126

Deprecated: Creation of dynamic property EE_DMS_4_1_0_gateways::$_new_table is deprecated in /httpdocs/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Stage.core.php on line 126

Deprecated: Creation of dynamic property EE_DMS_4_1_0_gateways::$_old_table is deprecated in /httpdocs/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Stage.core.php on line 126

Fatal error: Uncaught Error: Cannot access private property EE_DMS_4_1_0_events::$_new_table in /httpdocs/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Stage.core.php:126 Stack trace: #0 /httpdocs/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(809): EE_Data_Migration_Script_Stage->instantiate_from_array_of_properties() #1 /httpdocs/wp-content/plugins/event-espresso-core-reg/core/EE_Data_Migration_Manager.core.php(272): EE_Data_Migration_Script_Base->instantiate_from_array_of_properties() #2 /httpdocs/wp-content/plugins/event-espresso-core-reg/core/EE_Data_Migration_Manager.core.php(324): EE_Data_Migration_Manager->_get_dms_class_from_wp_option() #3 /httpdocs/wp-content/plugins/event-espresso-core-reg/core/EE_Data_Migration_Manager.core.php(512): EE_Data_Migration_Manager->get_data_migrations_ran() #4 /httpdocs/wp-content/plugins/event-espresso-core-reg/core/EE_Maintenance_Mode.core.php(152): EE_Data_Migration_Manager->check_for_applicable_data_migration_scripts() #5 /httpdocs/wp-content/plugins/event-espresso-core-reg/core/EE_System.core.php(527): EE_Maintenance_Mode->set_maintenance_mode_if_db_old() #6 /httpdocs/wp-content/plugins/event-espresso-core-reg/core/EE_System.core.php(484): EE_System->detect_if_activation_or_upgrade() #7 /httpdocs/wp-includes/class-wp-hook.php(324): EE_System->detect_activations_or_upgrades() #8 /httpdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #9 /httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action() #10 /httpdocs/wp-content/plugins/event-espresso-core-reg/core/EE_Bootstrap.core.php(35): do_action() #11 /httpdocs/wp-includes/class-wp-hook.php(324): EE_Bootstrap::detect_activations_or_upgrades() #12 /httpdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #13 /httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action() #14 /httpdocs/wp-settings.php(550): do_action() #15 /httpdocs/wp-config.php(90): require_once(‘…’) #16 /httpdocs/wp-load.php(50): require_once(‘…’) #17 /httpdocs/wp-blog-header.php(13): require_once(‘…’) #18 /httpdocs/index.php(17): require(‘…’) #19 {main} thrown in /httpdocs/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Stage.core.php on line 126


Tony

  • Support Staff

April 17, 2024 at 1:33 pm

Hi there,

Rather than me chippin away at individual errors, do you mind if I clone the site so I can see all of the errors being thrown and get a fix for the migration?

I can then send you a patch copy of EE5 with any changes required so you can run the migration yourself.

To do the above I usually use UpDraft and create a backup, download it locally and and install, then work through the issues being thrown. If that’s ok just send temp login details for the site over using this form:

https://eventespresso.com/send-login-details/

I’ll get a patch ready for you asap.

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

Event Espresso