Help Center
DocsMoving from ServiceTitan
Import your customer list from ServiceTitan.
- 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.
The files a real export gives you
- Customer list saved out of a search. Becomes your companies.
- 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.
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. |
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.
- A customer keeps its name, how to reach it, its addresses and its labels. Agreements, price books and the paperwork attached to the customer do not come across.
- Notes and activity history do not come across. Calls, messages and the running commentary on a customer stay where they are.
- We read the customer list and nothing else. Equipment, jobs, estimates and money owed have no route out of here that we can read, so plan on rebuilding those rather than moving them.
- Photos, signed forms and attachments do not come across. Every file stays on the record you exported it from, so keep that account open until you have downloaded what you need.
- Your download does not carry the files themselves. Bring them over in a second step: send us a zip of the files and a list saying which record each one belongs to.
- Filter your customers to the ones you want, then save the result out of the search. That saved list is what we read.
- Most of what this one can send out goes to a ledger rather than to you, so the customer list is the part worth taking.
- Cancelling here is a conversation with your account contact and there is no step in it that hands you your data. Save the customer list before you start that conversation.
- A photo library of tens of thousands of pictures is bigger than one move. Bring the files attached to your live jobs first, keep the rest where they are, and ask us if you need the whole archive.
- 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.