Help Center
DocsMoving from Dubsado
Bring clients, their contacts and their projects across from Dubsado. Its clients, projects and contacts exports are three separate files and we join them back into one set of records.
- Companies. The businesses you sell to, buy from or work alongside. Each row becomes one company, and every contact, deal and invoice you bring later links back to it by name.
- People. The individual people you talk to. Each row becomes one contact, attached to the company named on the same row.
- Deals. The deals in and out of your pipeline. Each row becomes one deal on the company it names, sitting at the stage you give it.
The files a real export gives you
- Clients export. Becomes your companies.
- Projects export. Becomes your deals.
- Contacts export. Becomes your people.
- 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.
- Companies. Companies come before contacts, because a contact is attached to one.
- People. Contacts come after companies and before everything that names a person.
- Deals. A deal needs its company and its stage, so both come first.
Companies
The companies or accounts list out of the system you are leaving.
| Field | Description |
|---|---|
| Company name* | Write it as company. We also read company name, account name, organization. Example: Acme Manufacturing. The name we match everything else against, so keep it spelled the way your team says it. |
| Web address | Write it as domain. Example: acme.example. Helps us spot the same company arriving twice under two spellings. |
| Main phone number | Write it as phone. We also read phone number, main phone. Example: +1 415 555 0142. |
| Main email address | Write it as email. We also read email address. Example: hello@acme.example. |
| What they are to you | Write it as type. We also read company type, account type. Example: customer. A word we do not recognise stops the row, so the accepted words are listed with this record type. |
| How active they are | Write it as status. We also read account status. Example: active. |
| Industry | Write it as industry. Example: Manufacturing. |
| City | Write it as city. Example: Oakland. |
| Country | Write it as country. Example: United States. |
| Who owns it | Write it as assigned_to. We also read owner, account owner. Example: dana@yourcompany.example. Use the work email of somebody already in your workspace, or leave it blank. |
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. |
Deals
The deals, opportunities or pipeline export.
| Field | Description |
|---|---|
| Deal name* | Write it as name. We also read deal name, opportunity name. Example: Acme line upgrade. |
| Company name* | Write it as company. We also read company name, account name. Example: Acme Manufacturing. A deal needs a company. Bring the companies file first. |
| Stage | Write it as stage. We also read deal stage. Example: proposal. We keep your own stage names where your workspace already has them. |
| Value | Write it as amount. We also read value, deal value. Example: 48000. |
| Currency | Write it as currency. Example: USD. Give this whenever your deals are not all in one currency. |
| Expected close | Write it as expected_close_date. We also read close date, expected close date. Example: 2025-09-30. A date we cannot read stops the row rather than landing as a blank. |
| 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.
Deals: stage
discovery, prospecting, research, qualification, qualified, qualifying, proposal, proposal price quote, quote, negotiation, negotiation review, contract, contract sent, closed won, won, closed lost, lost, appointmentscheduled, qualifiedtobuy, presentationscheduled, decisionmakerboughtin, contractsent, closedwon, closedlost, lead in, contact made, needs defined, proposal made, negotiations started, perception analysis, id. decision makers, value proposition, needs analysis.
A stage word we do not know lands the deal in Discovery, and we say so on the row.
People: lifecycle stage
subscriber, lead, mql, marketing qualified lead, marketingqualifiedlead, sql, sales qualified lead, salesqualifiedlead, opportunity, customer, evangelist.
- Your own words for where a client stands do not line up with ours, so we leave that column out rather than turn it into the wrong word. Set them once after the move.
- Form and questionnaire answers live in their own structure outside the standard export, so they are not in the file at all and cannot come across.
- Canned emails, workflow steps and scheduled reminders stay behind.
- Client portal logins, and anything a client typed into a portal form, stay behind.
- Contract signature status comes out as a word on the project row and we have nowhere to put it, so it is not brought across. Keep the file if you need it for your records.
- How much of a project has already been paid stays with whichever product holds the money.
- An invoice amount column is not a billing history. The export carries an amount on the project row and no invoice, payment or refund of its own, so nothing lands in your billing records.
- Bring invoices across from your accounting product instead, and we will match them to the clients and projects these files create.
- Calendar appointments are an export of their own and are not part of the clients, projects or contacts files.
- You need three exports, not one. Clients, projects and contacts each come out as their own file. Bring all three and we will join them back into one client with its people and its work.
- The export runs from a desktop browser only, so start it on a computer rather than on a phone.
- Only the account owner, or someone the owner has given permission to export, can run it. If the option is missing, that is why.
- Everything comes out as a comma separated file. There is no spreadsheet option.
- 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.