The CSV import was never the hard part

The migration pilot was useful for one thing: it made the bigger problem much clearer.

Getting one CSV into a database turned out to be the easy part. The actual problem is giving customers a way to bring their existing data into a SaaS product without turning every import into another support or engineering job.

I'm building ImportFlow as an embedded customer importer for Supabase SaaS. Customers bring CSV or spreadsheet data into the product, work through mapping and bad data there, and get a clear result instead of handing the file back and forth with the team.

I'm still building the first usable release, but I've opened early access while I do it. I want the first version shaped by teams that already deal with customer imports, not by a feature list I guessed at on my own.

If your customers bring data from another tool, I'd like to hear how you handle it today and what you wish the importer could take off your team's plate.

Early access: https://importflow.dev/#alpha