How to use Prisma migrations to add new models on an existing Laravel-managed MySQL database without data loss #28943

Pavan-Kumar-KN · 2025-12-19T06:29:27Z

Pavan-Kumar-KN
Dec 19, 2025

What I have done so far

The database already exists and contains data.
I created a baseline migration in Prisma that represents the current schema:
```
prisma/migrations/0_init/migration.sql
```
I marked the baseline migration as applied.

npx prisma migrate resolve --applied 0_init

I updated schema.prisma and added new models (new tables only, no changes to existing Laravel tables).
When I run:

 npx prisma migrate dev --create-only --name <migration_file_name>

Prisma warns that:

The database will be reset, or
Data loss may occur

This is not acceptable because the database is shared and already in use.

What I want

Prisma should treat the existing schema as baseline
Prisma migrations should be used only for new tables / new models
No destructive changes
No database reset

A clean, safe workflow going forward

My Questions:

What is the correct Prisma workflow for adding new models to an already existing Laravel-managed database?
How should the baseline migration be created and applied so Prisma does not attempt a reset?
After baselining, should prisma migrate dev be used for new models, or is migrate deploy the correct command?
What is the recommended long-term migration strategy when Laravel and Prisma share the same database but Prisma is responsible for new tables?

Any official guidance or best practices for this scenario would be very helpful.

nurul3101 · 2025-12-19T10:28:31Z

nurul3101
Dec 19, 2025
Maintainer

Hey @Pavan-Kumar-KN!

After you have applied have marked the baseline migration as applied via this command: npx prisma migrate resolve --applied 0_init

What happens if you run npx prisma migrate dev command after you add the new models. Is there any specific reason you need to add --create-only flag?

0 replies

Pavan-Kumar-KN · 2025-12-19T12:17:30Z

Pavan-Kumar-KN
Dec 19, 2025
Author

Hi @nurul3101,
Our backend is currently built on Laravel, using MySQL (RDS), and all database migrations have been handled by Laravel so far. We’re now migrating the system feature by feature and introducing a NestJS + Prisma stack alongside it.

The issue I’m facing is that when I run prisma migrate dev, Prisma suggests resetting the database or running migrate reset, and also throws relation / foreign key errors—even though the current schema and database state are already in sync.

Since this is a shared database with existing data, resetting the DB is not an option. I’m trying to understand the correct and safe workflow to introduce Prisma migrations without affecting the existing Laravel-managed schema.

although i can push the new models using push command or deploy command but the migration file we have to maintain right
I think you got the issue now !!

0 replies

nurul3101 · 2025-12-23T11:14:45Z

nurul3101
Dec 23, 2025
Maintainer

Hey @Pavan-Kumar-KN, thanks for the additional context!

I understand the issue now. When you run prisma migrate dev after baselining, Prisma might be detecting drift between your baseline migration and the actual database state, which triggers the reset warning.

Here's what I'd recommend:

After marking the baseline as applied, ensure your schema.prisma exactly matches the current database state (including all Laravel tables). You can use prisma db pull to verify this.
Then add only your new models to schema.prisma (the ones Prisma will manage).
Run prisma migrate dev --name add_new_models without the --create-only flag. This should generate a migration file with only the new tables, since the baseline is already marked as applied.
The relation/foreign key errors you're seeing suggest there might be a mismatch between what's in your baseline migration and what's actually in the database.

Regarding migration files: Yes, you should maintain them! Using prisma db push skips the migration history entirely, which isn't ideal for production workflows. Once your baseline is properly set up, prisma migrate dev should work cleanly for new additions.

Let me know if you still see the reset warnings after ensuring your baseline matches the DB state exactly!

1 reply

Pavan-Kumar-KN Dec 24, 2025
Author

Hi @nurul3101 I have tried as you said but in the last stage getting this issue

Loaded Prisma config from prisma.config.ts.

Prisma schema loaded from prisma\schema.prisma.
Datasource "db": MySQL database "searchy" at "localhost:3306"

Drift detected: Your database schema is not in sync with your migration history.

The following is a summary of the differences between the expected database schema given your migrations files, and the actual schema of the database.

It should be understood as the set of changes to get from the expected schema to the actual schema.

[+] Added tables
  - TestUser

[*] Changed the `five_minute_journals` table
  [*] Altered column `user_type` (default changed from `Some(Value(String("AppModelsUser")))` to `Some(Value(String("App\\Models\\User")))`)

[*] Changed the `goals` table
  [*] Altered column `user_type` (default changed from `Some(Value(String("AppModelsUser")))` to `Some(Value(String("App\\Models\\User")))`)

[*] Changed the `notes` table
  [*] Altered column `user_type` (default changed from `Some(Value(String("AppModelsUser")))` to `Some(Value(String("App\\Models\\User")))`)

[*] Changed the `todos` table
  [*] Altered column `user_type` (default changed from `Some(Value(String("AppModelsUser")))` to `Some(Value(String("App\\Models\\User")))`)

We need to reset the MySQL database "searchy" at "localhost:3306"

You may use prisma migrate reset to drop the development database.
All data will be lost.

Note: I’ve now taken a SQL dump from the live database and am running it inside a Docker container.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

How to use Prisma migrations to add new models on an existing Laravel-managed MySQL database without data loss #28943

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 3 comments 1 reply

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

How to use Prisma migrations to add new models on an existing Laravel-managed MySQL database without data loss #28943

Uh oh!

Uh oh!

Pavan-Kumar-KN Dec 19, 2025

Replies: 3 comments · 1 reply

Uh oh!

nurul3101 Dec 19, 2025 Maintainer

Uh oh!

Uh oh!

Pavan-Kumar-KN Dec 19, 2025 Author

Uh oh!

nurul3101 Dec 23, 2025 Maintainer

Uh oh!

Pavan-Kumar-KN Dec 24, 2025 Author

Pavan-Kumar-KN
Dec 19, 2025

Replies: 3 comments 1 reply

nurul3101
Dec 19, 2025
Maintainer

Pavan-Kumar-KN
Dec 19, 2025
Author

nurul3101
Dec 23, 2025
Maintainer

Pavan-Kumar-KN Dec 24, 2025
Author