Help Center

Docs

Moving from Housecall Pro

Import customers, jobs and estimates from Housecall Pro.

What comes across

The record types we can build from your Housecall Pro export.

  • 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.
  • Quotes. Your quotes. Each row becomes one quote in your workspace.
  • Projects. The pieces of work you run for a customer. Each row becomes one project against the company it names.

The files a real export gives you

  • Customer list. Becomes your companies.
  • Jobs. Becomes your projects.
  • Estimates. Becomes your quotes.

Getting your files out

Three steps, then bring everything back here at once.

  1. Sign in to your old system.
  2. Go to Settings, then Export, and choose every record type it offers.
  3. 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.

The order we bring things in

We will bring these in this order so the links hold.

  1. Companies. Companies come before contacts, because a contact is attached to one.
  2. People. Contacts come after companies and before everything that names a person.
  3. Quotes. A quote points at a company and at products, so both come first.
  4. Projects. A project is attached to a company, so companies come first.

The columns we read

What each one is called here, the headings we recognise for it, and an example.

Companies

The companies or accounts list out of the system you are leaving.

FieldDescription
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 addressWrite it as domain. Example: acme.example. Helps us spot the same company arriving twice under two spellings.
Main phone numberWrite it as phone. We also read phone number, main phone. Example: +1 415 555 0142.
Main email addressWrite it as email. We also read email address. Example: hello@acme.example.
What they are to youWrite 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 areWrite it as status. We also read account status. Example: active.
IndustryWrite it as industry. Example: Manufacturing.
CityWrite it as city. Example: Oakland.
CountryWrite it as country. Example: United States.
Who owns itWrite 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.

FieldDescription
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 nameWrite 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 addressWrite it as email. We also read email address, work email. Example: dana@acme.example.
Phone numberWrite it as phone. We also read phone number. Example: +1 415 555 0188.
Job titleWrite it as title. We also read job title, position. Example: Operations Lead.
Where they are in your funnelWrite it as lifecycle_stage. We also read lifecycle stage. Example: customer. We keep your own words where your workspace already uses them.
Profile linkWrite it as linkedin_url. We also read linkedin. Example: https://www.example.com/in/dana.
Who owns itWrite it as assigned_to. We also read owner. Example: dana@yourcompany.example.

Quotes

The quotes list out of the system you are leaving.

FieldDescription
Source Record IDWrite it as source_record_id. We also read _source_record_id.
Assigned ToWrite it as assigned_to.
CompanyWrite it as company.
Company IDWrite it as company_id.
Contact EmailWrite it as contact_email.
Contact IDWrite it as contact_id.
CurrencyWrite it as currency.
DescriptionWrite it as description.
Discount TypeWrite it as discount_type.
Discount ValueWrite it as discount_value.
Expiry DateWrite it as expiry_date.
Internal NotesWrite it as internal_notes.
IntroductionWrite it as introduction.
Is OptionalWrite it as is_optional.
Is SelectedWrite it as is_selected.
Issue DateWrite it as issue_date.
Line Discount TypeWrite it as line_discount_type.
Line Discount ValueWrite it as line_discount_value.
NameWrite it as name.
NotesWrite it as notes.
OpportunityWrite it as opportunity.
Opportunity IDWrite it as opportunity_id.
Product IDWrite it as product_id.
QuantityWrite it as quantity.
Quote Number*Write it as quote_number.
Record IDWrite it as record_id.
Section NameWrite it as section_name.
SKUWrite it as sku.
Source Record IDWrite it as source_record_id.
StatusWrite it as status.
Tax CodeWrite it as tax_code.
Tax RateWrite it as tax_rate.
Terms And ConditionsWrite it as terms_and_conditions.
Title*Write it as title.
Unit LabelWrite it as unit_label.
Unit PriceWrite it as unit_price.

Projects

The project, job or engagement export.

FieldDescription
Project name*Write it as name. We also read project name. Example: Acme line upgrade.
Where it is up toWrite it as stage. Example: in_progress. A word we do not recognise stops the row.
Start dateWrite it as start_date. We also read start date. Example: 2025-04-01.
Target finishWrite it as target_end_date. We also read target end date. Example: 2025-07-31.
BudgetWrite it as budget_amount. We also read budget. Example: 48000.

Words we recognise

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.

What is not coming across.

  • 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.
  • 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.
  • A file of jobs holds one row per visit and repeats the customer on every row of theirs. We collapse those rows onto the customer they name, so one company comes out for each distinct customer and one job for each row.
  • Line items, checklists, time on site and the crew who attended do not come across. A job arrives with its name, its customer, its dates and its money.
  • An estimate keeps its name, its customer, its dates, its money and its lines. Which option the customer accepted, the signature on it and the pictures attached to it do not come across.
  • The way out here is three separate files rather than one: the customer list, the jobs and the estimates. Wait until you have all three and drop them in together, because the jobs and the estimates only find their customer once the customer list is in.
  • Each of the three is sent to you by email rather than downloaded on the spot, so give it a few minutes before you go looking.
  • If a report will not run across your whole history, ask for it a year at a time and drop the pieces in together.
  • Turn on every column the report offers before you save it. A report saved with the columns it starts with brings across about half of what you have.
  • 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.

What a move can hold

The same limits apply whichever system you are coming from.

  • 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.