Hi Kelechi,

Ideally, it's best that you create an export dump through phpmyadmin and export the tables over. Here's the general guideline that you could use and it is also what we used previously when we migrated from old site to new site.

NOTE:*Backup your data first before perform migration !important
NOTE:*Migrate all the old site user to new site first using 3rd party extension (make sure all the user id is same as old site)


1. Export all your EasySocial related table, that has prefix of #__social_*
NOTE: Please change the prefix #__ according to your database.
2. Download the exported tables .sql file and save it on your desktop.
3. Checks the database prefix for the new site. If the database prefix is the same with your old site/domain, you may skip this step. However, if the live site uses different database prefix, you'll need to edit the exported tables .sql file above and do a search and replace all database prefix accordingly.
4. Import your edited .sql file on steps 3, into your new site.
5. Then install latest EasySocial version on your new site.

NOTE:
You also have to migrate all your media files at ../media/com_easysocial/.. (for photos, avatars, videos, comments, conversation attachments, links images and files.

Hi,

I've done this exact steps before and have a problem with database, with auto increment. What could possibly cause this?

Please advice, thanks.

Hi Syabab,

May I know which table that having the issue? Perhaps, can you create a new ticket so that we can further check on this?

Thanks for your cooperation and understanding.

I had this issue about a year ago. Thanks to Mark who pointed it to auto increment issue.

It's started as a video problem then further checking found out that there are several other table (not just a #__social_videos) that is missing the auto_increment value. (I'm referring to this issue; https://stackideas.com/forums/fatal-error-when-accessing-video-at-backend). This is a nightmare

For your step number 5, is there a different if we install ES first, then replace all #__social_* with an edited .sql file, with import the edited .sql file first, then install a fresh version of ES?

Perhaps, can you create a new ticket so that we can further check on this?

I've open a new one here; https://stackideas.com/forums/import-from-another-es-site

Please advice, thanks.

Hi Syabab,

Ah I see, thanks for creating new ticket for that

For your step number 5, is there a different if we install ES first, then replace all #__social_* with an edited .sql file, with import the edited .sql file first, then install a fresh version of ES?

If you have the same Easysocial version from old site, it could no issue.