What Happened to the Flatfile Importer? The Obvious Rebrand, Explained

If you searched for the Flatfile importer recently, you may have noticed something surprising: the company behind it is no longer called Flatfile. In 2026, Flatfile rebranded to Obvious and repositioned itself as AI data preparation and migration software, with a new AI agent (also named Obvious) that migrates data, analyzes it, builds reports, and generates presentations. That is a much bigger story than a logo change. If your SaaS product embeds the Flatfile importer, or you were evaluating it for customer-facing CSV import, the rebrand raises real questions about where the product is headed. Here is what changed, what it means for embedded import buyers, and how to think about your options.

Start with the facts as Flatfile presents them. The homepage now leads with "AI-powered data migration" for enterprises. The product navigation centers on Workbooks (a spreadsheet-like collaborative interface), AI Mapping, Configuration, Collaboration, and Transform. The solutions pages target service teams and system integrators, with dedicated editions for NetSuite and Workday partners. The pricing page describes project-volume-based billing with no published dollar figures, and the site notes that older versions of the classic importer are no longer supported.

None of this is inherently bad. It is a coherent strategy aimed at enterprise data migration projects, the kind run by implementation teams and consultancies. But it is a different job than the one many SaaS teams originally hired Flatfile to do: give my customers a fast, reliable, embedded way to upload a spreadsheet into my product. Those two jobs pull a roadmap in different directions, and the rebrand signals which direction won. We saw this coming when we compared the platforms in Dromo vs. Flatfile vs. OneSchema, and the divergence has only widened since.

Credit where due: Flatfile pioneered a lot of this category, and the pivot makes commercial sense from their side. Enterprise migration projects command large contracts, services partners like system integrators bring repeatable deal flow, and an AI agent that spans extraction, transformation, reporting, and presentations is a bigger story to tell investors than a file upload widget. The move tracks a broader 2026 pattern where AI is reshaping the data import stack and vendors are choosing which layer of it to own. The strategic question was never whether the pivot is smart for Flatfile. It is whether it is good for you.

When a vendor repositions, embedded customers feel it in three places. First, roadmap attention. Features for collaborative enterprise data projects (multi-step approvals, shared workbooks, presentation generation) do not necessarily improve the widget your users see inside your app. The embedded import experience, from column mapping to validation to error correction, needs constant investment to stay sharp, and importer-first vendors are the ones making that investment. Second, pricing predictability. Project-volume billing makes sense for migration consultancies that run discrete projects. It maps awkwardly onto a SaaS product where thousands of customers each upload files continuously, which is why we have long argued for scrutinizing data import pricing models before you commit. Third, support and deprecation risk. Every pivot eventually rationalizes the product line, and legacy embedded SDK versions are usually the first to lose support.

To be clear, Flatfile still maintains developer documentation, an API, and a plugin ecosystem, and existing customers are not being cut off. The question is not whether the importer works today. It is whether an embedded CSV importer remains the company's core product tomorrow, and what happens to your onboarding funnel if it does not. Your customers do not care about your vendor's strategy; they care that a broken import experience costs them time, and it costs you revenue.

If you are a current customer heading into a renewal, or an evaluator deciding whether to sign, put these on the table. What is the committed roadmap for the embedded importer specifically, not the platform as a whole? What are the support timelines for the SDK version you are on? Can you get pricing in writing that scales with your actual usage pattern rather than project volume? How do compliance guarantees (SOC 2, HIPAA, GDPR) apply to the embedded product as the platform evolves? These join the standard diligence we outline in ten questions for your data importer and the five security and privacy questions every vendor should answer without hesitation. A vendor with a clear importer roadmap will answer all of these easily. Hesitation is data.

It is also worth quantifying what the importer is actually worth to you before the conversation. If your onboarding depends on customers successfully uploading data, the importer sits directly on your activation and revenue path. Estimate the support tickets a degraded import experience would generate, the onboarding time it would add, and the churn it would create. Teams that have done this math, the same math from our breakdown of the hidden costs of poor data import processes, tend to negotiate very differently, because they know a mediocre importer is not a line-item problem. It is a funnel problem.

Staying put is a legitimate option, especially if you are deep into a contract and the embedded product meets your needs today. But if the rebrand has you rethinking, the good news is that the embedded import category is stronger than ever. Our roundup of the best Flatfile alternatives in 2026 covers the field in depth, and our guide to the best CSV importers for SaaS ranks the leading options by use case. The short version: importer-first vendors now offer AI-powered column matching, automated validation, in-place error correction, and fully self-service import flows as standard, with compliance built in rather than bolted on.

Dromo's position here is simple: data file importing is not a stepping stone to a different business, it is the business. The embeddable importer drops into React, Angular, or Vue, a headless API covers automated pipelines, and private mode means customer files never touch Dromo's servers. Pricing is published on the site: $599 per month for Professional with usage-based scaling, no sales call required to see a number. That is the profile of a vendor whose roadmap and your import experience point the same way, something worth checking against any evaluation framework you use.

Switching importers sounds like a project, but it is dramatically smaller than the original build ever was. Schemas, validation rules, and mapping logic translate cleanly between modern importers, and the embedded integration is typically a few hundred lines, not a subsystem. We maintain a step-by-step guide to migrating from Flatfile to Dromo, and the real-world benchmark comes from WayCool, which completed its migration in under an hour and cut costs in the process. UpKeep made a similar move and pushed its import success rate to 99 percent.

The Flatfile rebrand is a reminder that in infrastructure, you are not just buying features, you are buying a roadmap. When the vendor's future and your use case line up, everything compounds in your favor. When they diverge, you inherit the gap. If embedded CSV import matters to your product, pick a vendor for whom it is the whole product. See the difference for yourself with a free Dromo sandbox account, or talk to our team about a side-by-side migration plan. For the deeper comparison, our Flatfile vs. Dromo breakdown and the build vs. buy math are the places to start.