Notion API importer, with Databases to Bases conversion bounty - $5,000

[kepano]

Currently Importer supports converting Notion's HTML exports to Markdown via #14.

Unfortunately Notion's file-based export options don't include necessary data to recreate Databases.

This new importer would use the Notion API to download files progressively, and convert Databases to Bases as .base files using the YAML syntax.

Closes #415

Bounty

See the Contribution guidelines for how to claim this bounty.

Bounty: $5,000 USD
Timeframe: 30 days

⚠️ Please only apply if you have taken time to explore the Importer codebase, as well as the Notion API. Provide detail about how you would approach solving it within the constraints of this Obsidian plugin.

Requirements

• Uses Notion API (integration token) incorporating changes from new data source object introduced 2025-09.
• Converts Databases to Bases, using the Bases syntax in a way that preserves the dynamic data. Formulas should be converted from Notion functions to Obsidian functions.
• Properly converts files to Obsidian-flavored Markdown, including tables, to-do lists, etc
• Support for images and attachments. Embed links converted to Markdown format !()[image.png] and placed in the user's defined attachment location (Settings → File & links)
• Provide working test cases, ideally a reproducible data import that can be used on Notion. Alternatively a test account you can share with us via DM.
• Review the contribution guidelines regarding code standards and limiting dependencies.

Other considerations:

• Keep Importer UI as simple as possible, mirror the current Notion (.zip) but adding the Notion integration token field.
• Handle Notion's rate limits

Databases to Bases

Some exploration is required before implementation because Databases and Bases work a bit differently. Notion's Databases start out as empty, whereas a Base starts out with all of the user's files, then narrows down using filters.

• Determine an approach for importing databases and files
• Determine what database features can be imported: views, columns, groups, summaries, formulas, etc.
• Determine what can't be imported, and what fallbacks might be appropriate, for example calendar views, kanban, etc.

[Klaudioz]

Hi, I’d like to claim this bounty to build a Notion-API importer (pages + media) with Databases → Bases conversion.

Short background: I was the top Replit bounty hunter in 2023 (Mainly chatbot, but Including a Notion automation + OpenAI work), I’ve contributed to several OSS projects (https://github.com/klaudioz), and I hold an Obsidian Insider Catalyst license as an early user. Also this is my LinkedIn https://www.linkedin.com/in/canalesclaudio/ and resume: cv.claud.dev

I’ll deliver a Notion integration (token auth, pagination), robust Notion → Obsidian-flavored Markdown conversion (blocks, tables, code, to-dos, callouts), and attachments downloaded into the vault’s attachment folder with correct ![]() embeds. Databases will import as individual notes with YAML frontmatter and a sample Base view mapping; I’ll document limitations (formulas/rollups).

my Plan: open a WIP PR branch within 3 days, incremental PRs for review, full implementation and tests inside the 30-day bounty window. It would be an honor to contribute to this amazing project. I'm a long time Obsidian user having thousand of notes, including all the bounties I've worked.

[kepano]

@Klaudioz Have you explored the Notion API? Can you be a bit more specific about how you would approach handling the differences in how Databases vs Bases work since one is additive and the other is subtractive?

[Klaudioz]

@Klaudioz Have you explored the Notion API? Can you be a bit more specific about how you would approach handling the differences in how Databases vs Bases work since one is additive and the other is subtractive?

yeah, I understand what you meant. I'm an avid Obsidian user and I've used Notion in the past. I'd treat Notion databases as the source of truth, importing each row as a Markdown note with metadata to allow safe, incremental sync. I'd map the properties to the note metadata, convert page content to Obsidian-style Markdown, download attachments into the vault, and create Bases (subtractive views) that mirror the Notion filters.

This is my Contra profile also @kepano https://contra.com/klaudioz

[dsynkd]

I would like to apply for this bounty as well.

Why I would be a good fit: am familiar with Obsidian plugin development, have multiple forks and PRs (obsidian-spaced-repetition, obsidian-front-matter-title). Have previously worked with Notion API as well.

Rough draft for an approach: detect Notion databases, maybe using the selector table.collection-content. Add an additional field for taking the integration token. Use the API to download the pages in the table and put them in a specific folder, mapping properties to metadata. Set the Base filter to display all notes in that folder, with relevant properties.

Only thing is I am currently busy with some interviews, I can start in about 2 weeks, but if time is of the essence others might be a better fit...

[kareemamrr]

Hey @kepano ! I'd love to take on this bounty.

Background: I've been digging deep into both the Obsidian Importer source and Notion's API docs. Spent a good amount of time understanding how FormatImporter works, the mobile constraints (especially that tricky "no Node.js imports" requirement), and all the performance guidelines you've outlined. Also got familiar with the new .base syntax.

So about that Database vs Base problem...

Notion databases work like containers - you throw pages into them. Obsidian Bases work the opposite way - they're more like smart filters that sift through everything in your vault. Here's how I'd bridge that gap:

My plan is to import each database page as a regular markdown file with all the database properties stuffed into the YAML frontmatter. Every imported page gets tagged with an ID so we can track which database it came from.

Then I create .base files that basically recreate the database view by filtering for those imported files

Timeline wise:

• Week 1: Get the basic importer working, set up Notion API calls with proper rate limiting, nail down the block → markdown conversion
• Week 2: Property mapping, downloading attachments, getting that YAML frontmatter just right
• Week 3: The bases generation part, figuring out view mappings, formula conversions where possible
• Week 4: Testing with real databases, making sure mobile doesn't break, writing docs

[kepano]

Bounty increased to $5,000. We'll select an applicant in the next 1-2 days. Thanks!

[greywolf42069]

Greetings,

I am GreyWolf, an ambitious full stack engineer. I'd love to take on this challenge as it would give me the opportunity to display my versatility in structuring and executing development of a dynamic array of different system structures.

You can see an example of the depth of my skills from this repository where I formed a signing library from one network to another and added a vast array of additional unit tests and edge cases to ensure that the package was able to not just meet the basic needs of the network change but also meet all the needs involved in the task.

I sincerely would appreciate the opportunity to demonstrate my capabilities and also secure a bounty to fund my further work and research in the FOSS field.

https://github.com/greywolf42069/swarm-transactions

[omarish]

Hi there. I’m open to giving this a try.

I wrote a service to render my personal website (https://omarish.com) via the Notion API and went so far as to write a Notion to React transpiler. I’m at the gym right now but can give the specifics a close look as soon as I’m back at my desk. I want this to exist because I need it myself.

Qualifications: I maintain several python open source packages, am the CEO of https://3.is, and previously led asset integration at Coinbase.