Notion has no app output, so the job is moving the data and the workflow out.

What does Notion actually hand you when you ask for your content?

Files, from one menu, in one of three shapes. Notion's help article on exporting your content opens by offering PDF, CSV and HTML format, and the dropdown itself lists PDF, HTML, and Markdown and CSV. You click the dot dot dot icon at the top right of a page, open More, and choose Export. A page that is not a database comes out as a Markdown file. A full page database comes out as a CSV, with Markdown files for each subpage. Callout blocks are exported as HTML, because Markdown has no equivalent for them. If a PDF export fails, Notion falls back to exporting HTML instead.

Three limits in that article matter more than the formats. You cannot export a Form view of a database at all, and Notion suggests exporting the questions and responses from Table view instead. When you export a database you choose between the current view and the default view, because exporting all views at once is not supported. And including subpages as separate PDF files is a Business or Enterprise plan feature. The whole workspace export lives in Settings, under Workspace, then General, then Export all workspace content. It arrives as an emailed link that expires after 7 days and can take up to 30 hours to process, and you can only start it on desktop or on the web.

Then comes the sentence that decides what the export is for. Notion writes that you cannot instantly recreate your workspace by reuploading your exported workspace content. Read that before you plan a migration around a zip file. The export preserves what the views showed, as files. It does not carry the structure that made those views work. If the data has to live somewhere else, the API is the route, because there the schema is still an object you can read. Automation tools hit this from the other side, where the workflow is portable and the screen is not, and zapier to mobile app is that version of the problem.

Notion, API request limits, the source of the size and rate figures used below, read 22 October 2026

Can a Notion page already be an app on a phone?

It can be two things, and neither of them is yours. The first is a Notion Site. Notion's help article on publishing a Site says any page you build can be turned into one with a click, through Share and then the Publish tab. The free plan covers an unlimited number of published pages and one claimed notion.site domain. Paid plans raise that to five of those domains and add search engine optimisation fields, themes and a Google Analytics connection. A domain you already own is a separate add-on, charged at 10 US dollars a month, or 8 a month on annual billing, for up to 25 domains, read on 22 October 2026. The Site updates by itself as you edit the page, and Notion warns that indexing can take up to four weeks.

The second is the Notion app on the App Store and Google Play, which you read, edit and comment in. That is a host app holding your workspace, which is a model Apple names explicitly. Guideline 4.2.6 says apps created from a commercialized template or app generation service will be rejected unless submitted directly by the provider of the app's content, and then allows one alternative: a single binary that hosts all client content in an aggregated or picker model. Notion is that single binary. The consequence for you is that the icon, the notifications and the onboarding belong to Notion, and the layout does too. Notion's mobile help states that there are no columns on mobile and that any column structure you built on desktop collapses into one. A three column dashboard is not broken on a phone. The app only has one column to put it in.

That same mobile page lists six things the app will not do at all: select several blocks at once, import data, change your account information, delete or leave workspaces, edit workspace security settings, and edit plan or billing settings. Someone reading notes on a train will never meet any of them. Someone trying to run a shift rota from a phone meets most of them in the first week. So a Notion page does reach a phone, in two supported ways, and both of them keep Notion in the middle. If that is fine, stop here and publish a Site, because it costs an afternoon.

Apple, App Store Review Guidelines, guideline 4.2.6 and the picker model, last updated 16 October 2026, read 22 October 2026

What does the Notion API expose, and how fast will it read?

Almost everything you can see, and nothing you can install. The object model is worth getting right before you write any code, because it changed. Notion's guide on working with databases explains that a database holds data sources and views, that a data source carries the schema and is the parent of its pages, and that a page's property values fill the cells while its content blocks form the body. API version 2025-09-03 introduced that split for multi-source databases, and Notion's own upgrade guide says the change is not backwards compatible: most operations that used a database_id now want a data_source_id. Any Notion tutorial that still calls POST to query a database is describing the old shape.

Now the ceilings, all read on 22 October 2026. A paginated endpoint accepts a page_size with a maximum of 100, and pass it explicitly, because the introduction page contradicts itself about the default: its parameter table says 100, the sentence above that table says ten. Each connection gets a fixed budget of requests per 60 second window set by the workspace plan: 600 a minute on Business and Enterprise, which Notion calls an average of 10 per second, and 180 a minute on every other plan, an average of 3 per second. You can spend that evenly or in one burst. Querying a data source then has its own separate limit of about 3 requests per second per connection, and a further limit is shared across all of the workspace's connections, so you can be throttled while each connection sits inside its own budget. Going over returns HTTP 429 with a rate_limited code and a Retry-After header in whole seconds, and a 529 means Notion is overloaded and should be retried the same way.

The figure that actually breaks projects is 10,000. Notion's guide on querying large data sources says a single query returns at most 10,000 results, that the cap is per query rather than per data source, and that pagination stops once it is reached. The response comes back with has_more set to false and a request_status marked incomplete, with an incomplete_reason of query_result_limit_reached. Notion spells out the trap: a loop that follows next_cursor until has_more is false looks like it finished, while a 25,000 row database quietly returns 10,000 rows. The documented way through is to sort by created_time, walk the window, and start a new query from the last timestamp you saw, deduplicating the rows that sit on the boundary. Use created_time rather than last_edited_time, because an edit moves a row between windows.

A handful of smaller limits catch people out on the write side and in the app. A single payload maxes out at 1000 block elements and 500KB, and a rich text content string at 2000 characters. A relation in a page response returns up to 25 references, with has_more true when there are more, and a page write replaces the relation outright, so read the existing references before you add one. And a file url is a temporary signed link that expires after an hour, which means you cannot store it for offline use. Since 8 September 2026 the REST API also enforces the free workspace block limit: a free workspace with more than one member has 1,000 lifetime blocks, deleting blocks does not win any back, and after a three day grace period writes that create a block fail with a 403. Reading stays open throughout. Anyone coming from a spreadsheet backed tool will find this familiar, and appsheet to mobile app walks the same ground with Google's limits instead.

Notion, API request limits, rate limits and size limits, read 22 October 2026

What does a rebuild actually have to replace?

Less than people fear, as long as Notion stays where it is. Keep the workspace as the place your team edits, and treat the app as a second face on the same data. Your schema stays. Your rows stay. Your permissions stay. What you are building is the screens, a cached copy on the device so the app opens with no signal, and a refresh loop that respects the rate limits. The one decision worth making on day one is whether the app writes back. A read-only app is a weekend of work and almost no risk. A writing app has to handle two people editing a row at once, and Notion has no conflict resolution to lend you.

Four pieces need a decision rather than a port. Formulas and rollups are read-only through the API, so you either show the value Notion calculated and accept the lag, or you reimplement the arithmetic in the app. Buttons come back as empty objects, so anything a button did has to be rewritten as an action. File URLs expire after an hour, so anything that must work offline has to be downloaded rather than linked. And a multi column page has to be redrawn, because the Notion app itself does not render columns on a phone. Those four are the whole surprise. Everything else is a list, a detail screen and a form.

Newly is an AI app builder for this job. You describe the screens in plain English and it writes a real React Native and Expo project that you own, with two-way GitHub sync, so the code is never somewhere you cannot reach it. It uploads iOS builds to TestFlight, publishes to Google Play internal testing, and builds a standalone Android APK. It costs $25 a month and there is no free tier. The one thing it will not do is press submit on the App Store for you, and that is deliberate: guideline 4.2.6 rejects apps from an app generation service unless the provider of the content submits them, so the account and the submission are yours. The steps for that are in publish to app store.

A recommendation that costs us money, to finish. Do not rebuild a workspace that is working. If your team lives in Notion on laptops and checks it on a phone twice a day, the Notion app is the right answer, and a Site covers the people outside the workspace. Build when you need it on a home screen under your own name, when it has to work with no signal, or when a notification has to arrive without anybody opening an app. Those are the only jobs a Notion page cannot do, and none of them is about how good your database is.

Apple, App Store Review Guidelines, guidelines 4.2, 4.2.2 and 4.2.6, read 22 October 2026