Data migration from EE3 to EE4 is only available from EE3 versions 3.1.36+
I would recommend creating a Full Site Back-up before continuing any further, just to be safe.
You’ll need to de-activate EE4, update EE3 to the latest version, then activate EE4 & migrate your data (you may also need to ‘Reset’ EE4 after updating EE3 to force EE4 to re-run migrations, you can do this via Event Espresso -> Maintenance -> Reset/Delete Date tab which will remove ALL EE4 data but leave EE3)
The reason for this is there have been database changes within EE3 from 3.1.27 to 3.1.36 which EE3 handles itself. Then EE4 runs the migrations based on the latest version of the DB.
Your instructions worked Tony but I did get some “Warnings” after the migration about specific registrants, I then ran the migration again and everything seems to be fine. Weird.
If you still have the warnings saved somewhere we may be able to investigate further, although this depends on the warning itself.
Do you still have them saved?
Viewing 4 reply threads
The support post ‘Upgrading from 3.1.27.1 to 4.2.5 no events data’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
Support forum for Event Espresso 3 and Event Espresso 4.