Import & export
Administration ▸ Import & export is one page with three tabs: Export (take your data out), Import (bring it in from another tool), and History (who moved what, and when). Owners and admins only, because both directions move every record at once. The old /import and /export links still work and land on the right tab.
No lock-in. Export covers 61 kinds of record, up from twelve, and adds the ones a customer actually needs on the way out: your calls, call transcripts, voicemail, chat, meeting and screen recordings, text campaigns, payroll runs and payslips, projects, tasks, portfolios, ideas, risks, timesheets, clients, deals, contacts, leads, the customer and supplier master, proposals, contracts, forms and their submissions, invoices AND their line items, estimates, credit notes, payments, receipts, bills, vendors, products, expense claims, the chart of accounts, journal entries and lines, the ledger, bank accounts, assets, liabilities, domains, recurring expenses, subscriptions, the people roster, teams, attendance, leave, jobs, applications, interviews, offers, support tickets, automations, document and message templates, your custom fields, your companies, your status taxonomy and your appointments. Export everything gives you the lot as one .zip with a manifest and a README. Each record type comes out in full up to 200,000 rows; past that the card says so and we will get you the rest.
- 1
Export one thing
Open the Export tab, filter the list if you like, then press Export CSV on the card. Every row comes out, not the first thousand: the page reads the whole table in pages, in a stable order so no row is missed or repeated at a page boundary, and tells you how many rows it wrote. Files are UTF-8 with a byte-order mark and CRLF line endings, which is what Excel, Google Sheets, Numbers and LibreOffice all read without being told anything.
- 2
Export everything
One button, one .zip, one file per module grouped into folders, plus MANIFEST.csv listing every file and its row count and README.txt explaining the format. If one module cannot be read the archive still builds and says so in the manifest rather than failing. The file is written to your disk as it is read rather than assembled in the browser first, so the size of your workspace is not a limit. In Chrome and Edge you are asked where to save it before anything starts and it goes straight there. Safari and Firefox cannot write straight to disk, so there the archive is held in the browser until it is finished and we stop with an explanation if it passes 400MB, rather than letting the tab run out of memory. If an export fails part way, the incomplete file is discarded instead of being left on your disk looking finished.
- 3
Import from another tool
Open the Import tab, pick where your data lives today (GoHighLevel, HubSpot, Pipedrive, ClickUp, Asana, monday, Trello, Jira, QuickBooks, Xero) and follow the export instructions shown. Then choose what you are importing, upload the CSV, check the column mapping, and import. Commas, semicolons, tabs and pipes are all recognised.
- 4
Check the mapping before you import
The page matches columns for you and shows you what it matched, including the number format (1,234.56 or 1.234,56) and the date order (D/M/Y or M/D/Y) it read from the whole column. Change any of them. Where a source column splits a person into First name and Last name, the field takes a second column and joins them.
- 5
Answer the values we do not recognise
If your file uses stage or status names this workspace does not have (“Discovery”, “Contract Sent”), you are asked what each one means before anything is written. The Import button stays disabled until every one is answered: skipping a value does not leave the field empty, it lets the column default apply, and that is exactly the silent substitution this step exists to prevent.
- 6
See what was refused
Rows the database will not accept are counted, explained in plain language, and downloadable as a CSV with the reason on each row, so you can fix them and re-import just those. An import that keeps failing stops itself rather than grinding through every row.
- 7
Check the History tab
Exports and imports are recorded with who ran it, what moved, and how many rows, in the same audit trail as the rest of the workspace. The recording is best effort and never blocks the work: if the trail cannot be written the file still downloads and the import still runs. Imports also show the filename, how many were refused, and how many were skipped as already present.
Two safety notes. A spreadsheet treats a cell beginning with = + - or @ as a formula, so a value typed into one of your public forms could otherwise run as code the moment you opened the export. Those values carry a leading apostrophe, which spreadsheets hide and strip; the data underneath is unchanged, and negative numbers are left alone so your accounts still add up. And exports are recorded: taking the customer list is an event with a name against it, which it was not before.
What imports today: projects, tasks, clients, deals, contacts, companies, leads, products, vendors, the chart of accounts, ideas and teams. Everything else exports but does not yet import; the cards say which is which, so the page never promises a round trip it cannot complete. Products and the chart of accounts used to be sent one row at a time, which made a few thousand accounts take the better part of an hour. They are now sent in batches of 500 and five thousand lines finishes in seconds. A bad line still fails on its own and still tells you which line it was, so speed costs you nothing in the report you get back.