|
mgregor
|
April 2, 2018 at 2:42 pm
hi, we have been developing a new site on a staging server. we are about ready to launch, but the staging site points to a version of the database where the ee data is a few weeks old and new events and registrations have been added on the live server since then. is there documentation on how best to merge data? can it be done by dropping and importing tables in phpmyadmin?
|
|
Josh
|
April 2, 2018 at 3:03 pm
Hi there,
We recommend using a tool like mergebot if you need to merge data. This cannot be done by dropping and importing tables in phpmyadmin because event and attendee data is partially stored in the wp_posts table.
|
|
mgregor
|
April 2, 2018 at 3:29 pm
wow. got any recommendations that don’t cost $250 minimum? that wasn’t what i was expecting at all.
|
|
mgregor
|
April 2, 2018 at 3:42 pm
what does the ‘import events’ button at the bottom of the event overview page do? can i export new events from the live site into the dev site?
|
|
Tony
|
April 3, 2018 at 4:40 am
wow. got any recommendations that don’t cost $250 minimum? that wasn’t what i was expecting at all.
You’re going to need to merge the data in from one database into another, its not a simple task so there are no cheap solutions.
The import events feature is from EE3 and allowed you to create a CSV file of events you wanted to create and then import them in batch into Event Espresso.
Are you still using EE3 on the new site?
If so is there something preventing you from updating to EE4?
If you are using EE3 then the data is handled differently and it may be a little easier for you depending on what you’ve changed.
|
|
mgregor
|
April 3, 2018 at 8:27 am
yes. we are still using ee3. it’s working for us so we didn’t move to EE4 yet.
|
|
Josh
|
April 11, 2018 at 4:05 pm
With EE3, the event and registration data is held in tables with _events_ in their table names. If you leave those be then you won’t need to merge any event data. It will just remain unchanged.
|
|
mgregor
|
April 16, 2018 at 8:16 am
oh thank goodness. that made it very easy once i figured out how to export the tables properly. i exported each _events_ table individually via phpmyadmin, then imported each table into the development server, after i had dropped the same-named tables. now that they were all imported EE is working as expected and with up to date information for all of our events. i won’t switch to EE4 if data migration is not a simple-ish process like this was.
|
