Flatfile Is Now Obvious: What Changes for Importer Users

Updated October 8, 2026. On December 5, 2025 the company behind Flatfile announced that it is now called Obvious, and that Obvious is also the name of its new product, a general AI agent sold per seat. Flatfile, the data importer, keeps its name and is described by the company as being in active, long term support, with no deprecation, no pricing change and no change to contracts. Ten months later the signals are mixed: the Flatfile docs changelog has had no entry since July 23, 2025, the product news page stops at August 15, 2025, and the last release of the @flatfile/react package was on November 7, 2025. This post lists what is confirmed, what is not, and what a team that depends on the importer should do about it.

Key Takeaways

Only the company changed its name. Flatfile the product still exists, is still sold, and the vendor says contracts, SLAs and renewals are unchanged.
Obvious is a separate product with its own architecture and its own pricing, aimed at a different buyer. That is where the company's public roadmap activity is.
No end of life date exists. Anyone who tells you the Flatfile importer is deprecated is ahead of the facts.
If your team uses Flatfile for recurring client files over SFTP or email, that was never what the importer did. That workload has a cleaner home.

What actually happened

December 5, 2025: the company announces on its LinkedIn page that Flatfile is rebranding to Obvious. The post says that Flatfile is not changing and that the company is now Obvious, with a new product also called Obvious.
The Flatfile knowledge base publishes an article titled About the Flatfile Rebrand. Its first lines: Flatfile the company is now Obvious. Flatfile the product remains unchanged. Your implementation, contract, and support continue exactly as they are today.
By March 2026 flatfile.com carries a banner on every page: Flatfile is now Obvious, with a link to the new product. The banner is still live today.
Obvious is sold per seat, with public Standard and Pro tiers and an Enterprise tier, and ships changelog entries through October 2026. Flatfile customers were offered early access first.
Flatfile itself is now presented as data preparation and migration software for service teams and system integrators. Its pricing page describes project volume based pricing with no published figures.

What the vendor says, in its own words

The support article answers the questions customers asked, and the answers are unambiguous. Is Flatfile being deprecated or sunset? No. Flatfile remains our core product and continues to be fully supported. We are not deprecating features or changing pricing. On contracts: same terms, same pricing, same renewal schedule. On support: same team, same SLAs, same channels. On whether Obvious replaces Flatfile: no, Flatfile remains the purpose built solution for data migration projects. On the relationship between the two: Obvious is a separate product with its own architecture.

Take those statements at face value. A written commitment to long term support is worth more than a rumor, and nothing published since contradicts it.

What the vendor has not said

No end of support date, no last supported SDK version and no migration guide away from Flatfile has been published. That is normal for a product in long term support. What is also normal, and worth watching, is where the engineering goes. These are the public signals as of today.

Docs changelog: last entry July 23, 2025.
What's new page: last entry August 12, 2025.
News page: last item August 15, 2025.
npm: @flatfile/react last published November 7, 2025; @flatfile/api August 28, 2025; none of the packages is marked deprecated.
Legacy Portal v2 and v3 documentation was marked deprecated on January 31, 2025, before the rebrand, and is kept for backward compatibility with upgrade guides to the current platform.
GitHub: the Flatfile organization still receives commits in 2026, alongside new repositories for Obvious.

Read together: the importer is maintained, not advanced. For a component that sits in your product's onboarding flow, maintained can be enough for years. It can also mean that the next browser change, framework major version or security finding waits longer than it used to.

What it means for your team

You use the embedded importer for one time uploads inside your app

No urgent action. Keep the contract, keep the SDK pinned, and put three things on a calendar: a quarterly check of the signals above, a copy of your Flatfile configuration (blueprints, record hooks, transformations) exported into your own repository so the mapping logic does not live only in a vendor console, and a named fallback. One fallback that costs nothing to keep ready is the FileFeed Embeddable Importer, a free React component with mapping and validation in the browser. It is not a feature by feature clone of Flatfile and does not try to be, but it covers the upload, map, fix and submit flow that most products actually use.

You use Flatfile for files that clients send on a schedule

This is the case to act on, and the rebrand is only the prompt. An in app importer assumes a person is present to drag a file, review the mapping and click submit. Recurring client files arrive at 2 am on an SFTP server or as an email attachment, with nobody in the loop, and the same client sends the same shape of file every week. Teams that used an importer for this wrote scripts around it: a poller, a mapping store, a replay mechanism, alerting. That is a product, and it is the one FileFeed sells: a client gets an SFTP folder or an email address, the mapping is approved once per client, every later file is validated row by row and delivered as signed JSON to your webhook. $700 per month, flat, for up to 20 client connections.

You are choosing an importer today

Ask every vendor the question the rebrand raises: which product gets the engineering budget next year, and how will I know? Then ask the question that matters more for B2B products: how many of my clients will upload a file by hand, and how many will export a file from their HR, payroll, inventory or carrier system and expect it to flow in on its own? If the second number is larger, the importer is the smaller half of the decision. Our Flatfile comparison covers the full picture with dates and prices.

If you decide to move: a checklist

1. Export the schema. Write down every target field, type, required flag and uniqueness rule your Flatfile blueprint enforces. This is the asset; the vendor is replaceable, the schema is not.
2. Export the rules. Record hooks and transformations become validation rules and transforms in the new tool. Most are trim, case, date and email normalization, plus a handful of cross field checks.
3. Collect ten real client files. Not samples, the ugly ones: the Excel with a header on row 3, the semicolon CSV, the export with dates in two formats. A replacement that cannot map those is not a replacement.
4. Separate the two workloads. Manual uploads inside the app go to an embedded importer. Scheduled client files go to a feed with SFTP or email intake, run history and replay.
5. Run both in parallel for one client. Compare the JSON your backend receives from each path for a few weeks before switching the rest.
6. Keep the old contract until the last client is moved. Long term support means there is no deadline pushing you; use that.

Step 3 is the one you can do right now. Drop one real client file into the browser and see the mapping, the rows that fail and the clean JSON, without an account.

The problem

What this post does not claim: that Flatfile is being shut down, that its pricing changed, or that customers were told anything beyond the public article and the announcement. None of that is confirmed, and we will update this page if the facts change.

Frequently asked questions

Is Flatfile shutting down?

No. The company, now called Obvious, states that Flatfile remains its core product in active, long term support, with no deprecation, no pricing change and unchanged contracts. No end of life date has been published.

What is the difference between Flatfile and Obvious?

Flatfile is the data importer and migration product. Obvious is the new company name and a separate AI agent product with its own architecture and per seat pricing. Flatfile customers were offered early access to Obvious, but it does not replace Flatfile.

Do I need to do anything if I use the Flatfile importer?

Not immediately. Keep your SDK version pinned, keep a copy of your blueprint and hooks in your own repository, and check the public release signals every quarter. Have a fallback importer identified so a decision never has to be made under pressure.

Can FileFeed replace Flatfile?

For recurring client files over SFTP or email, yes, and that is the workload FileFeed is built for. For one time uploads inside your app, FileFeed offers a free embeddable importer that covers upload, mapping, validation and submit, without claiming feature parity with Flatfile's platform.

How do I test a replacement with my own files?

Open filefeed.io/try, pick or paste your target schema, and drop a real client export. You see the column mapping, the rows that fail validation and the resulting JSON in the browser, with no account.

Flatfile is now Obvious: what changes for teams using the importer