Data export/import v4 -> v5 not creating draft record counterpart.

[douwepausma]

Bug report

Required System information

• Node.js version: v20.10.0
• NPM version: 10.2.3
• Strapi version: 5.7.0
• Database: Postgres
• Operating system: OS: darwin-arm64 Sequoia 15.1
• Is your project Javascript or Typescript: Typescript

Describe the bug

I am exporting data from a v4 Strapi instance and importing it into to a v5 Strapi instance. And all the records are in my database as they should, but are not visible in Strapi. I discoverd that this is caused by the fact that there are no draft versions of the records available in the database (probably because in Strapi v4 it is one and the same record).

Steps to reproduce the behavior

1. Follow the export documentation on a v4 instance
2. Follow the import documentation on a v5 instance

Expected behavior

Would it be an idea to auto create a draft version (containing the data from the published version including relations) when the imported record has an published_at value?

Additonal notes

I am upgrading Strapi manually hence why I am porting the data manually.

[strapi-bot]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/published-entries-not-visible-after-migration-from-strapi-4-25-17-to-5-5/49243/2

[derrickmehaffy]

We probably need to check the publishedAt information from exports coming from v4 and if it's null/undefined create the draft in Strapi 5.

To be determined if using exports from Strapi 4 in Strapi 5 are supported or not by the product team. (cc @maccomaccomaccomacco

[douwepausma]

We probably need to check the publishedAt information from exports coming from v4 and if it's null/undefined create the draft in Strapi 5.

Just to be clear, imported drafts are already handled correctly. It's when a published record (publishedAt is not null) is imported, a draft counterpart (without publishedAt) needs to be created in order for it to be displayed in Strapi, which currently is not the case.

[douwepausma]

For those running into the same issue. Here's a work around:

Steps

1. Import your export. npm run strapi import -- -f ../v4-export.tar.gz
2. Paste the createDraftCounterparts() function in your bootstrap() function in your src/index.ts/js see the example below
3. Set the desired content types.
4. npm run develop ONLY ONCE
5. Remove the code from the bootstrap() function or just comment out the execution part.
6. npm run develop again and check the results

// src/index.ts
import type { Core } from '@strapi/strapi';

export default {
  async bootstrap({ strapi }: { strapi: Core.Strapi }) {
    const createDraftCounterparts = async (contentType) => {
      const entries = await strapi.documents(contentType).findMany({
        fields: ['documentId', 'publishedAt'],
        status: 'published'
      });
      
      entries.map(async (entry) => {
        // Turn entry into draft
        await strapi.query(contentType).update({
          where: {
            documentId: entry.documentId
          },
          data: {
            publishedAt: null
          }
        })
        
        // Published draft
        const newPublished = await strapi.documents(contentType).publish({
          documentId: entry.documentId,
          fields: ['documentId', 'publishedAt', 'id'],
        });
        
        // Update publishedAt to original value
        await strapi.query(contentType).update({
          where: {
            id: newPublished.entries.find(e => e.publishedAt).id
          },
          data: {
            publishedAt: entry.publishedAt
          }
        })
      });
    }

    [
       // Make sure to define your contentTypes here
       'api::page.page',
       'api::article.article'
    ].map(async (contentType) => {
        await createDraftCounterparts(contentType);
    });
  },
};