Help Center
DocsMoving from Salesforce
Import accounts, contacts, opportunities, activities, and tasks from Salesforce.
- 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.
- Activities. The calls, meetings, notes and emails already on the record. Each row becomes one item on the history of the company or contact it names, keeping its original date.
- Tasks. The to do items your team is carrying. Each row becomes one task, on a project where you name one.
- 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.
- Activities. History is attached to the company, contact or deal it belongs to, so those exist first.
- Tasks. A task can hang off a project, a deal or a ticket, so those 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. |
Activities
The activity, task history or timeline export. Several systems split this into one file per kind.
| Field | Description |
|---|---|
| What it was* | Write it as subject. We also read title. Example: Intro call. |
| Kind of item* | Write it as activity_type. We also read activity type. Example: call. Leave it blank and we record a note. A word we do not recognise stops the row. |
| The notes | Write it as content. We also read notes, body. Example: Walked through the current setup.. |
| When it happened | Write it as due_date. We also read date, activity date. Example: 2025-03-14. We keep the original date rather than stamping today. |
| Who did it | Write it as assigned_to. We also read owner. Example: dana@yourcompany.example. |
Tasks
The task, to do or activity export.
| Field | Description |
|---|---|
| What needs doing* | Write it as title. We also read subject. Example: Send the revised quote. |
| Where it stands | Write it as status. We also read task status. Example: todo. A word we do not recognise still lands the task, marked for you to look at. |
| How urgent it is | Write it as priority. Example: high. |
| Due date | Write it as due_date. We also read due date. Example: 2025-04-18. |
| Who it is for | Write it as assigned_to. We also read owner, assignee. Example: dana@yourcompany.example. |
| The detail | Write it as description. We also read notes. Example: Use the numbers from the second visit.. |
Type any of these and we will know what you mean. Anything else comes across as it is written.
Activities: type
call, email, meeting, note, task, follow up, followup, incoming email, outgoing email, logged call, logged email, logged meeting, logged note, phone call, send letter, send quote, lunch, deadline, mail, phone, event, in person, online meeting, video call, demo, presentation, sms, text, chat, letter.
Activities: priority
low, medium, high, urgent.
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.
Tasks: priority
low, lowest, medium, normal, mid, high, highest, urgent, critical, blocker.
Tasks: status
todo, to do, in progress, working, started, review, in review, awaiting review, done, completed, complete, closed, finished, not started, deferred, waiting on someone else, open.
- Past email and past calendar entries do not come across in a file. Connect Gmail or Outlook and we match them to people by address from the moment you connect.
- Report and dashboard definitions do not come across. Rebuild your top few in the built in analytics.
- Flows, Process Builder and Apex do not come across. Rebuild the logic as automations where it still applies.
- A custom field has to exist here before a Salesforce column can land in it, so make the ones you need first. A standalone custom object with its own web of links does not come across whole.
- 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.