Update existing Notion rows from a CSV. Without the duplicates.
Notion's CSV import adds rows. It doesn't update them, so importing the same file twice gives you two of everything. Notion Safe Update matches on a column you choose, shows you every field that would change, and writes only what you approve.
Nothing to install · We never see your Notion password · Price is being tested
This is what you'd see before anything is written
A worked example on sample data. Switch between the groups to see how each record would be treated.
In the planned product you would approve or exclude groups and individual records here, then apply. Nothing is written to Notion until you press apply.
The planned workflow
Four steps. None of this is operational yet — it describes what we intend to build.
Connect a database
Authorise access through Notion's own permission screen and pick one database. You choose what the integration can reach.
Upload your CSV
Map columns to properties and choose the column that uniquely identifies a record — a client ID, SKU or email.
Review every change
See each record sorted into update, create, unchanged or needs-review, with the old and new value for every field that differs.
Approve and apply
Only approved changes are written. Afterwards you get a report of what was done and a CSV snapshot of the supported fields as they were beforehand.
Why this is awkward today
Notion's import appends, it doesn't match
"Merge with CSV" adds every row in the file to the database. It doesn't look for an existing record with the same identifier, so re-importing an updated export leaves you with the old row and the new one side by side.
So the work lands on you
The usual alternatives are reconciling by hand in the table view, rebuilding the database from scratch each time, or using a command-line tool that needs a browser cookie and a terminal. All of them work. None is pleasant.
We're describing Notion's documented import behaviour, not criticising the product. This is a narrow gap, which is why we think a narrow tool fits it.
It isn't built yet. That's the point of this page.
We're checking whether enough people want this before writing it. If you'd use it, leave an email and you'll hear once — when it launches, or if we decide not to build it.
The waitlist opens shortly — the form is not accepting addresses yet.
By submitting you agree that we store your address to send that one message. No newsletter, no sharing. Withdraw any time — see the privacy notice.
Separately — and this is the question we actually need answered:
This records an anonymous signal only. It isn't a purchase, an order or a commitment, and nothing is charged.
Proposed pricing
We're testing this price. It is not a final commercial offer.
One update means one controlled CSV-to-database operation: one file, one database, one preview, one apply. Usage limits would be published before launch.
- Preview of every create, update, skip and conflict
- Field-level before and after for each change
- Matching on a column you choose
- Report of what was applied
- CSV snapshot of supported fields, taken before the write
No payment is possible yet.
Questions
Can I use it now?
No. Nothing on this page is operational. The demo above runs on invented data and is not connected to Notion. We're measuring interest before building.
Would it overwrite my existing data?
It would write only the changes you approve in the preview, to the fields you've mapped. Fields you don't map would be left alone. Any tool that writes to your database can change data, so the preview exists to make sure nothing happens that you haven't seen first.
Would it support all Notion property types?
No, and we won't claim otherwise. Formulas and rollups are calculated by Notion and cannot be written at all. Relations, which point at pages in other databases, are substantially harder than plain text or numbers and may not be supported at launch. The supported list would be published before anyone pays.
Could I undo the changes?
Not automatically, and we'd rather say so than promise a rollback we can't guarantee. What's planned is a CSV snapshot of the supported fields as they were immediately before the write, so you hold your own record of the previous values. Notion's own page history is separate from this and remains available to you.
Is there a subscription?
No. The plan is to charge per update. If you run one update a year, you'd pay once.
Would I have to share my Notion password?
No. Access would go through Notion's standard authorisation screen, where you grant a named integration access to the pages you select, and you can revoke it from Notion at any time. We would never ask for your password.
Who is behind this?
SignalFoundry, a small German digital-products business. The imprint and privacy notice are linked in the footer.