How to map json fields to database column names
- Step 1Export your database column names — Run SELECT column_name FROM information_schema.columns WHERE table_name = 'your_table' to get the exact column names. These are the target names in your mapping.
- Step 2Map source JSON keys to column names — Create pairs: camelCase API name →’ snake_case column name. Map every field that will be inserted: firstName →’ first_name, userId →’ user_id, createdAt →’ created_at.
- Step 3Apply the rename to the full record batch — Paste the JSON array of records and apply the mapping. Every record is renamed simultaneously, producing a consistently named batch.
- Step 4Feed into your ORM bulk-create — Pass the renamed JSON array directly to your ORM: await prisma.users.createMany({ data: renamedRecords }). The field names now match the Prisma schema column names exactly.
Frequently asked questions
How do I handle the id field — should I rename it or exclude it for auto-increment columns?+
Exclude the source id field if your database column is auto-increment (SERIAL or AUTO_INCREMENT). Use the JSON Key Filter to remove the id field from the records before the bulk insert, so the database generates new IDs. Only include id if you are explicitly seeding a table with specific known IDs.
Can I rename keys and cast types in the same step?+
This tool handles renaming only. For type casting — converting string numbers to integers, ISO date strings to Date objects, or 'true'/'false' strings to booleans — apply a transformation function after renaming. In JavaScript, use a map over the renamed array to cast specific fields.
Is the data transmitted to JAD Apps?+
No. All renaming runs entirely in your browser. JSON records with customer and business data are never transmitted to JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.