Dromo for your stack, your system, and your industry

Every Dromo importer runs on the same engine: AI column matching, validation as the file loads, bulk fixes, and clean JSON out. What changes from one product to the next is the code it sits in, the system the data is headed for, and the files your customers have. Pick the page closest to yours for setup steps, the fields that break most often, and a working schema you can copy.

By framework

Install guides, the props that matter, and the pitfalls specific to each framework. Every package renders the same importer.

By system

The record types each kind of system imports, the columns that arrive broken, and the validators and hooks that catch them.

By industry

The files each industry actually sends, the compliance questions buyers ask, and how recurring partner files are automated.

One schema, two ways in

Each page above uses the embedded importer, where a user uploads a file inside your product and fixes problems as they go. Recurring files with nobody present, like nightly partner exports or a bulk migration, run through the Headless API on the Enterprise plan. A schema saved in Schema Studio works in both, so the rules your customers see when they upload are the same rules applied to their automated feeds.

Not sure where to start?

Start with the framework page for your frontend, then the system or industry page for your data. The sandbox account is free and needs no credit card, so you can test the importer on your own customers' files before you talk to anyone. For the full picture of how Dromo works, what it costs, and how it compares, see why Dromo.