Importing / exporting content

[jmikrut]

We are planning to build an import / export function that can help export to Excel, CSV, etc.

This will include upload import / export as well.

[matthijs166]

In Wordpress we used wp-all-import/export plugin a lot. Love the way that plugin is build.

[willviles]

This would be great. Could this functionality be built with RBAC at collection level for both imports and exports?

[matthijs166]

Here is a breakdown of features I really like about the export and import plugin:
Multiple export types

...

Filter options to exclude results in the export

...

Mapping/selecting fields



...

Reusability of running exports/imports later again. Setting up a nice export/import can take some time.

...

Setup for cron and having a URL for a feed. (handy if other software import the feed in an interval)

...

Import from URL

...

Record matching & field selection what to overwrite

...

Custom code for data normalization and transformations

...

Those are my top features, probly to much for the first version 😓
This feature would be very awesome to sync Dev/staging with production without exporting user data.

[JanettaH]

What is the status of this functionality?

[NicoCaldo]

Is there a plan for "import from Wordpress". I think if we were able to migrate a complete Wordpress blog this project would skyrocket.

[Metax7]

Does anyone know how to export data from WordPress to Payload?

[katiasmet-93]

I imported data from prismic. I exported it to a json file. Then created a small app to do a post fetch to the payload API. You could do something similar with Wordpress.

[danielkoller]

Any info concerning the export function?

I would like to give my team the possibility to export form entries as a csv.

Thanks!

[kalon-robson]

I've reopened this project that I started a while back

• This version only migrates between payload instances¹ ², which is really handy when we want to diagnose an issue on an existing website so we migrate the prod content to our localhost.
• The next version, I want to add mapping CSV columns to payload fields.
• Then it would be handy to selectively export information by reusing the payload filters (on the collections pages) and selectively picking what fields we want.

I'll prepare the plugin to public and share it here if anyone wants to help to develop this with me.

¹ Ideally the collections are identical, from my testing payload is pretty smart with ignoring extra bits of data when creating records
² There is no collision detection and is intended to be used to import into blank instances

[tempo22]

I've reopened this project that I started a while back

• This version only migrates between payload instances¹ ², which is really handy when we want to diagnose an issue on an existing website so we migrate the prod content to our localhost.
• The next version, I want to add mapping CSV columns to payload fields.
• Then it would be handy to selectively export information by reusing the payload filters (on the collections pages) and selectively picking what fields we want.

I'll prepare the plugin to public and share it here if anyone wants to help to develop this with me.

¹ Ideally the collections are identical, from my testing payload is pretty smart with ignoring extra bits of data when creating records ² There is no collision detection and is intended to be used to import into blank instances

Did you had the chance to prepare the public plugin ?

[kalon-robson]

Hi @tempo22, I'm in a bit of a pickle with the new upcoming 3.0 release.

This version uses express routes heavily to achieve it's goals and I'm not sure if I should finish it like it is and then do a migration to 3.0 using the next routes.

I'm guessing it would still be handy to maintain this in 2.0 as the adoption of 3.0 will take time. What do you think?

Anyhow thank you for bumping this to my attention. I will notify you with the repo soon.

[akhrarovsaid]

As it stands, the only way to get true import/export is to build it yourself in-house with requirements from your specific project. I've yet to use a plugin that blew me away. It's definitely a much needed feature with several use-cases. I've been considering turning my own solution into a Payload plugin which features not only the ability to export/import from any specified collection, but also to choose what fields to export and how to reduce complicated fields such as Media/Upload and nested fields.

This is being used live right now for one of my clients and it works exceptionally well. However, it works well specifically because it's delegated to a job via a queue. This allows my customers the freedom of exporting/importing tens of thousands of entries without forcing the user to sit there and wait for it all to complete. Ideally, this wouldn't even happen on the same instance, but a dedicated server just for imports and exports.

I think before Imports/Exports really happen, what we really need is for the Jobs/Queues feature to ship. This would be an absolute game changer. In the meantime, any solution will just leave much to be desired.

[akhrarovsaid]

@mumincelal I'll do you one better: since this seems to have attracted a lot of interest, I'll author a plugin for this the moment I find the time. First iteration without job queues to account for those users who enjoy deploying to serverless, and then I'll add an opt-in jobs variant behind a config option is what I'm thinking now that job queues have shipped.

[crazytweeks]

Looking forward for this implementation for payload 3.

[BrianJM]

@akhrarovsaid Did you release this?

[marwinhormiz]

Any updates on this?

[roniekoma]

any update?

[AdvithShetty]

Hi, Any Update on this feature? is there any ETA or alternative to export collections untill its released?

[devj3ns]

It looks like an import/export plugin is currently in development: #10795

[AdvithShetty]

Yes i did see that one but, Any idea on the ETA?

[DracoBlue]

was published with 3.27.0 https://github.com/payloadcms/payload/releases/tag/v3.27.0

[lorenzrabs]

Hey, great work so far!

My two main USPs for this feature are:

• Exporting all website content to send it to a translation agency and then importing the completed translation back.
• Exporting all content (essentially like a database dump) to import it onto another domain—so that only the media files need to be transferred.

Would these functions be possible in future releases?

[matthijs166]

Just tried it and this feature is awesome! Can't wait on the import functionality of this package

[JW148]

Hi, is this plugin available as an NPM package yet? As mentioned above it is included in the 3.27.0 release, but I can't seem to find it anywhere.

[DracoBlue]

It is called

@payloadcms/plugin-import-export

[JW148]

Awesome, thanks! Must have been a typo on my end

[notflip]

It seems like there's no documentation for this yet? Or rather it's a 404: https://payloadcms.com/docs/plugins/import-export

[matthijs166]

We played a bit around with the plugin and it is awesome!

The features we are missing are mapping relations to a single values.
For example, exporting the collection with registrations and outputting the name (instead of the object ID).
Would also be awesome to map multiple fields, such as a name and an email.

Docs about the plugin would also help a lot.

Just an idea:
Sometimes we also need XML feeds for Google shopping and the sitemap.
An option for XML formats would also be nice, and maybe even with the option to predefine the structure with export templates.
(shipping the sitemap by default with the plugin)

We try to contribute to the plugin, If we got some extra time on our hands!

[notflip]

Would you mind pasting a gist of the code you're using? Not having documentation is a big issue at the moment.

[2coo]

I tried it but it shows error and It doesn't show any data in preview

err: {
      "type": "APIError",
      "message": "Collection with slug  not found",
      "stack":
          APIError: Collection with slug  not found
          at createExport

my plugins config.

importExportPlugin({
    collections: [
      "news"
    ],
    overrideExportCollection: (collection) => {
      console.log("collection", collection);
      collection.admin.group = "System"
      return collection
    },
    disableJobsQueue: true,
  }),

[DracoBlue]

Try without the overrideCollection part.