857
Import/Export Data
candidate
Activity
Newest
Oldest
J
Juan Lanus
It is essential to allow users to specify the encoding of the input data.
Not-very-technical users might be surprised to see that their taxtual data does not look as expected.
C
Contact
I've done a lot of site migrations across a ton of different platforms and I think what WPAllImport / WPAllExport have is a great solution compared to most. It allows for custom imports assigning values by column as well as site wide or "collection" specific exports in wordpress. I think a similar feature set would be a big success for the strapi ecosystem as a whole.
Custom imports specifically would make strapi far more accessible to people trying to migrate away from platforms like shopify, wix, and wordpress.
Derrick Mehaffy
candidate
We are currently evaluating this feature for development, please share any expectations or use-cases you might have. Thank you!
Raymond Sellars
Derrick Mehaffy: Features/capabilities we've been considering are:
matching content between environments.
full replacement imports, and delta imports , selection of imports
Categorising data so you can manage them as sets, i.e. FAQ pages, domain specific content (categories) etc
Can be ran by users + admins, ACLs on some content. Allow uses to migrate new sections of information vs change core pages of a website
Can be API driven not just UI, i.e. for automation
Pretty much standard features of data management. With an eye to customer and operational team distinction. Content managers != system operators.
J
Jdcreativedigitallab
Derrick Mehaffy: Currently I'm migrating data (over 7,000 field inspections) from a WordPress website to my new project on Strapi. I'm using WP All Import/ Export to export the data from WordPress and upload it into a Google Sheet, clean up and format the data, then import it to PostgresSQL so Strapi can recognize it. It's a tedious process and very dangerous. So with a feature like this, It will simplify the process of importing data to Strapi. Also sometimes I need to export data, so I have to export data, when this is the case I have to export from the database.
S
Santiago Santana
Derrick Mehaffy: We have an instance of Strapi in the staging environment and another instance of Strapi in the production environment.
To allow the customer to create their own pages we provide a pages collection with a dynamic zone with a twentyish components. Each page has between 5 and 13 components in average, the components have various levels of nesting in them (we needed to remove the nesting limit because it put a limit on the flexibility we needed for the components).
New components and pages are tested in staging environment, we need an easy export/import workflow for pages when new changes are merged into the production environment.
Raymond Sellars
Would be good to use import/export (with categories some how) as part of publication workflows. Particular where content is authored in one environment and then migrated in to a production or test environment. Recognition that blocks of content have different project management or curation lifecycles so you don't import/export everything. But logical blocks.
A
Alexandre Blais
This has been one of the most requested feature for over two years and was even planned in the old roadmap at some point. Since the (sad) drop of NOSQL support, this feature should be quicker to produce. Any way we could finally see this planned and delivered? Would help a bunch of our clients using Strapi daily and greatly appreciated.
N
Nico Hofmair
You might also be interested if you handle multiple instances (branch based test environments, staging, production) to easily transfer data between those.