Help Center
DocsMoving from HoneyBook
Bring your contacts across from HoneyBook. Its own published column list is the one it accepts for taking contacts IN, so treat the columns we read as our best expectation and check the preview.
- People. The individual people you talk to. Each row becomes one contact, attached to the company named on the same row.
The files a real export gives you
- Contacts import template. Becomes your people.
- Contacts export. Becomes your people. We have not seen a real copy of this file, so we read it by name rather than by its column list.
- Sign in to your old system.
- Go to Settings, then Export, and choose every record type it offers.
- You will get one or more files. Come back here and drop all of them in at once.
Nothing is written until you say so. You will see what we made of every file, decide anything we cannot decide on our own, and read a plain summary of what pressing the button does before it does it.
- People. Contacts come after companies and before everything that names a person.
People
The contacts or people export from the system you are leaving.
| Field | Description |
|---|---|
| First name* | Write it as first_name. We also read first name, given name. Example: Dana. A single full name column works too. We split it for you. |
| Last name | Write it as last_name. We also read last name, surname. Example: Whitfield. |
| Company name* | Write it as company. We also read company name, account name. Example: Acme Manufacturing. A contact needs a company. Bring the companies file first and these link themselves. |
| Email address | Write it as email. We also read email address, work email. Example: dana@acme.example. |
| Phone number | Write it as phone. We also read phone number. Example: +1 415 555 0188. |
| Job title | Write it as title. We also read job title, position. Example: Operations Lead. |
| Where they are in your funnel | Write it as lifecycle_stage. We also read lifecycle stage. Example: customer. We keep your own words where your workspace already uses them. |
| Profile link | Write it as linkedin_url. We also read linkedin. Example: https://www.example.com/in/dana. |
| Who owns it | Write it as assigned_to. We also read owner. Example: dana@yourcompany.example. |
Type any of these and we will know what you mean. Anything else comes across as it is written.
People: lifecycle stage
subscriber, lead, mql, marketing qualified lead, marketingqualifiedlead, sql, sales qualified lead, salesqualifiedlead, opportunity, customer, evangelist.
- Because the export path is not documented we cannot promise which columns arrive. Check the preview against your own file before you start.
- Projects and where they stand are not in a contacts file. Bring them across by hand, or from whichever product holds the money.
- Invoices, payments and signed contracts are not in a contacts file, so nothing lands in your billing records.
- Contacts only. There is no supported way to push an account across from another product in either direction, so a file is the whole route.
- The 500 row cap, the 2 MB size cap and the required email address are their own rules for taking a file IN. We do not cap your file that way and we will read a list their own importer would refuse.
- Its export path is not documented, so the columns we read are what we expect rather than what we have seen. Check the preview against your own file, and send us a real one so we can correct it.
- Columns we do not recognise are left out rather than guessed at. Nothing is written under a name we invented.
- Photos and files come over on their own. One move brings over 2 GB and 500 files.
- One file can hold up to 10,000 rows.
- One file can be up to 10 megabytes.
- You can undo a move for 30 days after it finishes.
- You can undo a single file import for 24 hours after it finishes.
Coming from something else? The list of systems we read has a page for each one, and a file from a system with no page of its own still comes across: we read the headings and you confirm every one of them before anything is written.