Drift detected after prisma migration dev and wants to reset the database?

Trying to to migrate from Prisma 1 to Prisma 2 and all seems to work, i.e. I can query my database fine. Except when running npx prisma migrate dev which seems to think my schema is out of date and says We need to reset the PostgreSQL database

Is there a way I can tell Prisma that the schema in my database is the one I want to keep?

The flow I have done to migrate is as follows:

1. Using pg_dump to pull down prisma 1 database
2. Use pg_restore to upload copy of prisma 1 database to a new database
3. Using npx prisma-upgrade to generate SQL commands to run on new database
4. Running prisma introspect which shows successful (a few warnings These id fields were enriched with @default(cuid()) information taken from the previous Prisma schema. but shouldn’t be a blocker?)
5. Run npx prisma generate and can succesfully generate my client which I can use to query data and all seems to work fine
6. Run prisma migrate dev which is what doesn’t work Drift detected: Your database schema is not in sync with your migration history & We need to reset the PostgreSQL database

I don’t want to reset my database as I’ll lose all my data.

Is it possible to delete these migrations from somewhere so it thinks my database schema is up to date or will that cause issues downt the track?

[stretch0]

@janpio haven’t been able to get the migration dev working yet but thinking the db push and pull is actually what we were after. We will be doing the actual migration next week so should (just been doing test runs for now) so can report back when we have more info.

[Gamote]

@janpio sure thing. Here is the new issue: #8124