惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Vercel News
Vercel News
Y
Y Combinator Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
The GitHub Blog
The GitHub Blog
N
Netflix TechBlog - Medium
MyScale Blog
MyScale Blog
F
Fortinet All Blogs
Microsoft Azure Blog
Microsoft Azure Blog
H
Help Net Security
C
Check Point Blog
博客园 - 聂微东
云风的 BLOG
云风的 BLOG
M
MIT News - Artificial intelligence
U
Unit 42
WordPress大学
WordPress大学
B
Blog
Last Week in AI
Last Week in AI
人人都是产品经理
人人都是产品经理
T
Tailwind CSS Blog
D
DataBreaches.Net
G
Google Developers Blog
T
The Blog of Author Tim Ferriss
Hugging Face - Blog
Hugging Face - Blog
IT之家
IT之家

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Moving from Migrate Mongo to Mongo Migrate Kit (mmk) With...
Santosh Gupta · 2026-06-25 · via DEV Community
Cover image for Moving from Migrate Mongo to Mongo Migrate Kit (mmk) Without Re Running Old Migrations

Santosh Gupta

If you're using migrate-mongo and considering a switch, the biggest concern usually isn't features.

It's this:

"Will I have to re-run old migrations or risk production data?"

The short answer is no.

I built mongo-migrate-kit with migration adoption as a first class feature because switching migration tools shouldn't feel risky.

The Problem

Most teams already have months or years of migration history.

Re-running old migrations is dangerous.

Editing migration records manually is even worse.

What you really want is a way to tell the new tool:

"These migrations already ran. Start tracking them and leave everything else alone."

That's exactly what mongo-migrate-kit does.

Import Existing migrate-mongo History

First, install the package:

npm install mongo-migrate-kit mongodb

Preview the import:

npx mmk import --dry-run

This reads your existing migrate-mongo changelog and shows what will be imported.

Nothing is written to the database.

Once you're happy with the output:

npx mmk import

The migration history is copied into mongo-migrate-kit's tracking collection.

Your original migrate-mongo changelog remains untouched.

What Happens Next?

After importing:

npx mmk status

Previously applied migrations appear as applied.

Any migration files that haven't run yet remain pending.

When you run:

npx mmk up

Only pending migrations execute.

Old migrations are never re-run.

Why I Built This

I originally created mongo-migrate-kit after running into rollback issues during a deployment.

While using migrate-mongo, I found myself wanting more control over migration safety and deployment workflows.

That led to features such as:

  • Rollback specific migrations or batches
  • Dry-run support
  • SHA-256 checksum validation
  • Distributed migration locking
  • Redo support
  • TypeScript support
  • Safe migration adoption from migrate-mongo

Documentation

Getting started takes only a few minutes:

Deep dive on migration guide from migrate mongo:
https://mongo-migrate-kit.vercel.app/guide/migrate-mongo

npm:
https://www.npmjs.com/package/mongo-migrate-kit

GitHub:
https://github.com/santosh327/mongo-migrate-kit

Final Thoughts

Migration tools should make deployments safer, not add anxiety.

If you're looking for a migrate-mongo alternative or need a MongoDB migration tool for Node.js that can adopt existing migration history safely, give mongo-migrate-kit a try.