Import Your Existing Data
Bring your contacts, properties, and pricebook items into JobsiteOn using CSV imports so you do not start from scratch.
Bring your contacts, properties, and pricebook items into JobsiteOn using CSV imports so you do not start from scratch.
This guide explains how to import your existing business data into JobsiteOn using CSV files. You will learn how to prepare your data, map columns to JobsiteOn fields, review imports before they commit, and handle common errors. JobsiteOn supports importing contacts, properties, and pricebook items.
When importing phone contacts in the iPhone or Android app, starting in Sandbox shows Switch to Live. Choose it to keep your selected contacts and continue to the duplicate review in Live. Contacts are added only after you confirm the import. This switch alone does not take the workspace live for everyone.
Screenshot: Import Data page showing three import options as cards: "Import Contacts", "Import Properties", and "Import Pricebook Items" with a description and "Start Import" button on each
If you are moving from another field-service system, start with the migration assistant cards in Settings > Imports. JobsiteOn includes guided options for Tradebase, ServiceTitan, Jobber, Housecall Pro, FieldEdge, ServiceFusion, and Synchroteam. Choose Generic CSV when your source system is not listed or when you already have spreadsheet exports.
Each source card explains the current support level and points you to the right CSV template or assisted migration path before you upload data. You can also open See all platforms to pick from the full catalog of recognized sources. JobsiteOn recognizes the export formats of about a hundred field-service, CRM, accounting, payments, and calendar tools.
During recognition and mapping, the JobsiteOn AI Foreman can lend a hand: when the automatic engine is not confident about what a file contains, it suggests the record type, and after you save a mapping it can fill in any leftover columns the engine could not match. Everything the AI Foreman suggests stays fully reviewable. It never overrides a choice you made, and you can turn it off for an import run.
Before preparing your file, download the CSV template for the data type you want to import. The template includes all supported column headers with example rows.
Tip: Always use the template as your starting point. It ensures your column headers match exactly what JobsiteOn expects, which prevents mapping errors during import.
The contacts template includes these columns:
| Column | Required | Description |
|---|---|---|
| first_name | Yes | Contact's first name |
| last_name | Yes | Contact's last name |
| No | Email address | |
| phone | No | Primary phone number |
| company | No | Company or business name |
| type | No | "customer", "vendor", or "lead" |
| notes | No | Free-text notes |
Note: Duplicate detection runs on email address. If a contact with the same email already exists, the import skips that row and reports it as a duplicate.
A row with an email but no name and no company is still imported: its name is made from the address, so dean.a.pendleton@field-9f0f1d.example becomes Dean A Pendleton.
The properties template includes:
| Column | Required | Description |
|---|---|---|
| address | Yes | Street address |
| city | Yes | City name |
| state | Yes | State abbreviation |
| zip | Yes | ZIP or postal code |
| contact_email | No | Links the property to an existing contact |
| property_type | No | "residential" or "commercial" |
| notes | No | Free-text notes about the property |
Tip: If you include
contact_email, JobsiteOn links the property to the matching contact automatically. Make sure the email matches a contact that already exists or is included in a contacts import you run first.
The pricebook template includes:
| Column | Required | Description |
|---|---|---|
| name | Yes | Item name (e.g., "Drain Cleaning") |
| description | No | Detailed description |
| type | Yes | "service" or "material" |
| unit_price | Yes | Price per unit in dollars |
| unit | No | Unit of measure (e.g., "each", "hour", "sqft") |
| taxable | No | "true" or "false" |
Screenshot: Column mapping screen showing CSV headers on the left ("First Name", "Last Name", "Email") mapped to JobsiteOn fields on the right with glenn checkmarks for matched columns and a yellow warning for one unmapped column
Animation: A user dragging a CSV file onto the upload area, the file parsing, and the column mapping screen appearing with auto-matched fields
After mapping, JobsiteOn shows a preview of the first 10 rows so you can verify the data looks correct.
Screenshot: Import preview table showing 10 rows of contact data with glenn checkmarks on 8 rows, a yellow warning icon on 1 row, and a red error icon on 1 row with an error message "Missing required field: last_name"
When a customer in your file has more than one email address, the preview also lists the people found in those emails. Each person becomes a contact of their own, named from the address and linked to the customer, while shared inboxes stay on the customer. See Contacts Made From Imported Emails.
Review the preview carefully. When satisfied, click Confirm Import.
After the import completes, JobsiteOn shows a summary:
Note: You can download a CSV of failed rows, fix the errors, and re-import just those rows. This saves you from re-uploading your entire file.
If your data is interconnected, import in this order:
If your assisted migration includes file links, sign in to JobsiteOn before opening them. Workspace files require access to that workspace. Private files remain available only to their owner or uploader. A saved link cannot open a deleted file or a file you no longer have permission to view.
Open the saved JobsiteOn link again if a temporary download address has expired. The link checks your access and creates a fresh download address each time.
If preparation fails, review the files and try again. If some records were already saved, retry the same import to continue from its last saved batch. Avoid starting a second copy of the import. If it keeps failing, give support the import ID and the time it stopped.
JobsiteOn keeps the line breaks in imported descriptions, notes and terms. Detail pages show each line of a description on its own line, and quote and invoice PDFs keep the line breaks inside each line description. Lines that start with a bullet or a list number print as a list, and text that starts with a number, such as "50% deposit", prints in full. If a description still shows as one paragraph, the source export joined its lines: edit the description and add the line breaks back.
Make sure your file is saved as UTF-8 encoded CSV. Some spreadsheet apps default to other encodings. In Excel, use Save As and select "CSV UTF-8" as the format.
Check that your CSV uses the exact column headers from the template. Headers are case-sensitive. "First Name" does not match "first_name". Use the downloaded template headers exactly.
Check the import summary for skipped duplicates. If all records were flagged as duplicates, your data may already exist in JobsiteOn. Verify by searching for a few records in the Contacts or Properties module.
Did this answer your question?