---
title: "Migrating Schemas Across Many Neon Projects Using DrizzleORM"
url: https://daily.dev/posts/migrating-schemas-across-many-neon-projects-using-drizzleorm-pu1azjpvf
source_url: https://neon.com/blog/migrating-schemas
type: article
source: "Neon"
published: 2026-07-09T06:57:49.506Z
updated: 2026-07-09T07:00:37.002Z
tags: ["github-actions"]
reading_time: 8
upvotes: 0
comments: 0
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrating Schemas Across Many Neon Projects Using DrizzleORM

**[Neon](https://daily.dev/sources/neontech)** · 8 min read · 0 upvotes · 0 comments

## Summary

A walkthrough of managing schema migrations across multiple Neon Postgres databases in a database-per-tenant architecture. The approach uses three custom scripts: a create script to provision new Neon projects via the Neon API, a generate script that auto-creates DrizzleORM config files, generates migration files, stores connection strings as GitHub secrets, and updates the GitHub Actions workflow, and a migrate script triggered on PR merge that applies the same schema to all tenant databases. The solution handles both onboarding new tenants and rolling out schema changes to all existing databases simultaneously.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://neon.com/blog/migrating-schemas>

## Similar posts on daily.dev

- [Integrating Postgres and Auth the Easy Way: Daisy’s Neon Setup](https://daily.dev/posts/integrating-postgres-and-auth-the-easy-way-daisy-s-neon-setup-2kwtolnxo) · Neon · 0 upvotes · 0 comments

---

Tags: [#github-actions](https://daily.dev/tags/github-actions)

[View this post on daily.dev](https://daily.dev/posts/migrating-schemas-across-many-neon-projects-using-drizzleorm-pu1azjpvf)
