Docs

Importing your history

A decade of old work can walk in from a CSV — and imports are built to never eat an edit you made.

One tool for every route in

Settings → Data → “Bring your data in” takes a spreadsheet from anywhere that can make a CSV — Excel, Google Sheets, Numbers, Airtable, or a whole Notion export. Before anything lands, you check the column matching and how your statuses translate; rows already in toqe are left alone unless you say otherwise. If an import lands wrong, Ctrl+Z undoes it for the rest of the session.

What an import will never do

• Overwrite your local edits. A re-import updates the rows it created, but a row you’ve touched keeps your values.
• Touch your settings, invoices or time off. Those are yours; imports only carry projects, clients and expenses.
• Write anything back. The road runs one way, in. Nothing you do in toqe reaches Notion or the spreadsheet it came from.

Back-filling by hand

For a year or two of old work, History’s + past project row is often faster than a spreadsheet: it defaults to Paid, follows the client’s rate, and keeps the client and dates from row to row so a run of entries goes quickly. Back-filled rows keep their own dates — money that landed last March files under last March.

A document that already carries Notion database ids (from toqe’s early days) also shows a direct API pull here. It’s the same one-way import, just fetched instead of dropped.