import legacy data

This support ticket is created 4 years, 2 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Our next available supporter will start replying to tickets in about 8.57 hours from now. Thank you for your understanding.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	-
-	13:00 – 18:00	13:00 – 18:00	13:00 – 18:00	14:00 – 18:00	13:00 – 18:00	-

Supporter timezone: America/Jamaica (GMT-05:00)

Tagged: Setting up post relationship, Types plugin

This topic contains 3 replies, has 2 voices.

Last updated by Shane 4 years, 2 months ago.

Assisted by: Shane.

Author

Posts

September 23, 2020 at 4:15 pm #1787853

Griffin

Tell us what you are trying to do? I'm trying to move a legacy database (Laravel/MySQL) to WP and Toolsets.
My main issue is importing the legacy data. There are many relationships, including M:M that rely on id's in the legacy data. Is there anyway to import this and map the data correctly?

For example, songs are M:M with transactions, submissions etc. Then there is the issue of taxonomy (lookup tables in Laravel talk). They also need to be imported, for example, a song can have more than one genre, or more than one mood.

I realize this is a long shot, but figured I'd ask.

Is there any documentation that you are following? No

September 23, 2020 at 7:24 pm #1788055

Shane

Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Griffin,

Thank you for getting in touch.

This is actually quite possible if your relationship data is present in the database because you can export it from the database.

Take a look at this documentation below.
https://toolset.com/course-lesson/how-to-import-posts-from-csv-files-and-maintain-relationships-when-using-the-csv-importer-plugin/

You can also have a look at this video below for further assistance.
hidden link

Thanks,
Shane

September 23, 2020 at 11:56 pm #1788235

Griffin

Well, that kind of works, but not really.

1. Taxonomies related to the custom post are not imported at all, well they just create a new taxonomy with the id not the title.
2. I am importing 16,000 plus transactions, so adding the relations to the CSV is not feasible. I can run a query to do that, but I haven't tried it.
3. One thing I forgot to mention was there is existing data. The wordpress site was the front end for a music publisher, he has a backend that is on Laravel. It's virtually impossible to map the songs in wordpress, to the songs in the Laravel app. It's a downfall of wordpress, I understand not your issue really. WP really needs to join the 1970's and learn about normalized data. I'm not sure how bad the performance will be in any case with 20k plus records and no indexes worth a damn.

Thanks

September 24, 2020 at 7:38 pm #1789533

Shane

Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Griffin,

3. One thing I forgot to mention was there is existing data. The wordpress site was the front end for a music publisher, he has a backend that is on Laravel. It's virtually impossible to map the songs in wordpress, to the songs in the Laravel app. It's a downfall of wordpress, I understand not your issue really. WP really needs to join the 1970's and learn about normalized data. I'm not sure how bad the performance will be in any case with 20k plus records and no indexes worth a damn.

I completely understand, i've worked with laravel previously. Your entire database relationship will need to be changed in order to fit into wordpress's native database structure.

Usually when you have 20k plus records you can leverage it with cache. I've seen customers with quite large websites with relational data and their website was still responsive.

Thanks,
Shane