Support

January 24, 2020 at 6:21 am

Hi there,

Something important to point out is that EE4 uses events (along with other entities) that are a custom post type which means you can’t migrate EE3 to EE4 on one site and then pull those migrated events into another. I’m not sure if your trying to do that but it wasn’t clear above so wanted to clarify.

We have also configured another server with database of old site which is using EE3. We have followed this steps: https://eventespresso.com/wiki/how-to-upgrade-event-espresso/#complete-the-migration. Tried to install EE4 as per instruction but there is no migration process.

Did you pull ALL tables from the original site into this one? If so that usually means EE4 has been activated on that site previously.

Migrations are only offered on the initial EE4 activation, after that, you won’t see them again unless you reset EE4.

You can confirm that on this additional site by resetting EE4, you do that by activating EE4 and navigating to:

Event Espresso -> Maintenance -> Reset/Delete Data

Click the Reset Event Espresso Data button
(Note that any EE4 data you have on that site currently will be deleted)

EE4 should go into maintenance mode and show you a migration option.

To do this on your new staging site (which has never had EE3 installed, correct?) you’ll need to copy all of the _events_ tables from the original database over to the new sites database.

Then install the latest version of EE3 on that site to setup the data that EE4 will be looking for. You can set up your organization data in the EE3 settings if preferred or do it after the migration.

De-activate EE3 again.

Activate EE4 and it will detect the EE3 data in that database and offer a migration.