JSON to MongoDB

This tool takes a JSON object or a JSON array of objects and generates MongoDB shell commands you can run immediately. For a single JSON object, it produces a db.collection.insertOne({...}) call. For a JSON array, it produces a db.collection.insertMany([...]) call containing every element of the array as a separate document. The collection name in the generated command defaults to a sensible name derived from your JSON structure, and you can override it in the collection name field before generating. This is useful when you want the output to target a specific collection in your MongoDB deployment without manually editing the generated command. The BSON type conversion covers the cases that cause silent data corruption when ignored. String values matching the ISO 8601 date format — patterns like "2019-03-12" or "2024-07-15T14:30:00Z" — are wrapped in new Date() in the output, producing a BSON Date type in storage that supports full date range queries and date aggregation pipeline stages like $dateToString, $year, $month, and $dayOfMonth. Plain strings do not support any of these operations. String values matching the 24-character hexadecimal ObjectId pattern are wrapped in ObjectId() in the output. This maintains type consistency with MongoDB's native _id fields and ensures that queries using ObjectId comparison work correctly on those fields. Nested documents and arrays are included as-is in the output. MongoDB's document model natively supports arbitrary nesting depth and mixed arrays, so there is no special handling required — your nested profile object and your tags array both land correctly in the output document structure. The generated command uses mongosh syntax by default, which is the current MongoDB shell introduced in MongoDB 5.x and the replacement for the legacy mongo shell. A legacy mode option produces output compatible with the older mongo shell syntax for developers working with MongoDB 4.x or earlier deployments that have not yet migrated to mongosh. The entire operation runs in your browser. No JSON data is transmitted to any server. You can paste real API payloads, production database documents, or sensitive records without any data leaving your machine.

MongoDB's core promise is that it stores documents that look like the JSON your application already works with. That promise is largely true — but there is a gap between raw JSON and the insert commands MongoDB actually needs, and that gap causes problems in practice. The most common problem is dates. Virtually every API that returns records with timestamps returns them as ISO 8601 strings. "createdAt": "2023-09-15T10:22:00Z" looks like a date, feels like a date, and in most application code behaves like a date after you parse it with your ORM or driver. But if you insert it as a raw string into MongoDB, it is stored as text. A query like db.users.find({createdAt: {$gte: new Date("2023-01-01")}}) will return zero results even for documents that clearly have 2023 dates, because MongoDB is doing a string comparison, not a date comparison, and BSON dates and BSON strings are never equal regardless of their content. I have seen this mistake in production codebases more than once. The developer tested with a driver that automatically converted date strings to BSON Dates — and then a manual seed script inserted the same data as raw strings, silently corrupting the entire date range query logic. The second common problem is seeding and migration work. When you are building a new service that consumes a third-party API, you want to capture a sample of the API response and seed your local or staging MongoDB with realistic data. Writing the insertMany command from scratch means manually copying the JSON, formatting it as a MongoDB shell command, handling the collection name, and ensuring BSON types are correct. For a ten-field document with thirty records, that is fifteen minutes of mechanical work that introduces escaping errors and type mistakes. This tool compresses it to thirty seconds. Data migration work has the same pattern. Moving documents from one MongoDB collection to another, or migrating data from a REST API into MongoDB for the first time, involves taking JSON payloads and constructing insertion commands. Having a tool that produces correct, ready-to-run shell commands removes an entire class of manual error. The mongosh vs legacy shell distinction matters more than it sounds for teams with mixed MongoDB versions. MongoDB deprecated the legacy mongo shell in MongoDB 5.0 and removed it entirely in 6.0. Teams still running 4.x deployments — common in enterprise environments with conservative upgrade cycles — need legacy syntax. Having both options in one tool means you do not need to remember which syntax your target environment requires.