Support

May 30, 2014 at 9:45 pm

Hi Frank,

One thing to make sure is the data being migrated is from a recent version of Event Espresso (at least 3.1.35 or newer). If you’re runnning an older version than that, you can reset EE4 data from its maintenance page, which will deactivate EE4. Then you can update to the latest version of Event Espresso 3, then try the migration again.

May 30, 2014 at 10:32 pm

Thanks for letting us know about the versions. The more we know, the less we have to guess about your system.

One thing you can try is free up some memory. If WordPress is already near its allocated memory limit and the migration process starts there’s a potential for things freezing up.

Memory allocation can often be increased by making a small edit to the wp-config.php file, and memory can be freed up by temporarily deactivating all other activated plugins.

Please also be sure to start fresh with a new migration by resetting Event Espresso 4’s data before restarting a migration.

June 11, 2014 at 2:55 pm

Hi, I am attempting to migrate to EE4 today on a local install. I have all the latest updates for EE plugins and WordPress is the lastest update. I also increased my memory size but it still locks up at record 8637 out of 19,742. I’ve done this three times now. If someone could shed some light on what to do I’d appreciate it.