Great field operations start with clear guidance

What this guide covers

Use Import Center to bring contacts, jobs, quotes, invoices, payments, and pricebook data into JobsiteOn from CSV exports.

You can open it directly from Settings -> Integrations -> Import Center. The Installed integrations page also links back into the same workflow, so provider migrations stay discoverable beside the connected-service controls.

The current workflow supports:

• platform selection from /settings/imports/new
• CSV upload by drag-and-drop or file picker
• automatic file parsing and entity detection
• header-count review and raw data preview
• recommended field mapping with manual overrides
• validation, preview, and final commit

Before you begin

• Start from Settings -> Integrations -> Import Center, or open /settings/imports directly in the correct workspace.
• Use sandbox first when testing a new import process.
• Gather the full export set when possible so linked records resolve cleanly.
• For Tradebase, upload contacts together with jobs, quotes, and invoices for the best match rate.

Tradebase CSV checklist

For Tradebase (yourtradebase.com), the upload screen is tuned for these CSV exports from docs/import-module/CSV Files for Data Transfer:

• Customers Data from *.csv -> Contacts
• Jobs Data from *.csv -> Jobs
• Invoices Data from *.csv -> Invoices
• Quotes Data from *.csv -> Quotes

The quotes export uses a multi-row format. JobsiteOn groups proposal rows automatically so the preview and mapping steps operate on quote records instead of raw line-item rows.

Step 1: Create the import run

Open /settings/imports/new, choose the source platform, and create the run.

• Use Tradebase when you are importing the standard Tradebase exports listed above.
• Use Unknown / Custom CSV when the file is not from a supported source or needs manual mapping.

After the run is created, JobsiteOn sends you to the upload step.

Step 2: Upload and parse files

Open /settings/imports/[runId]/upload and drag files into the drop zone or select them from disk.

After upload, each file is parsed automatically and shows:

• filename and row count
• detected header row count
• delimiter, encoding, and quote character
• suggested entity type with confidence
• entity type override if you want to force a different import target

Use the entity selector when a file is detected incorrectly. The Tradebase upload checklist also marks which expected files are already present in the run.

Step 3: Review recognition and preview data

Open /settings/imports/[runId]/recognize to review what JobsiteOn detected.

On this screen you can:

• adjust the detected header-row count
• review a raw preview of the uploaded CSV rows
• confirm or override the entity type
• inspect the recommended field matches and confidence levels

This is the first place to check when headers look shifted or the preview does not line up with the CSV columns you expect.

Step 4: Confirm field mapping

Open /settings/imports/[runId]/mapping to map CSV columns to JobsiteOn fields.

JobsiteOn recommends mappings automatically and keeps the mapping editable. Use this screen to:

• change the JobsiteOn target field for any CSV column
• ignore columns you do not want to import
• confirm required fields before validation

For supported Tradebase CSVs, JobsiteOn also applies import transforms automatically for common patterns such as:

• full names split into first and last name
• inline addresses split into street, city, state, and postal code
• phone numbers normalized from Contact Details
• status normalization
• date and currency parsing
• multi-email cells reduced to the primary email for matching and storage

Step 5: Validate and preview the import

Open /settings/imports/[runId]/validate to run validation, then /settings/imports/[runId]/preview to review staged results.

Validation checks imported records for missing required data, invalid values, and platform-specific parsing warnings.

Preview shows what JobsiteOn will do for each row:

• create a new record
• update an existing record
• skip an unchanged record

Review preview carefully before committing, especially when importing live data.

Step 6: Commit and review the summary

Open /settings/imports/[runId]/commit when the preview looks correct.

After commit, review /settings/imports/[runId]/summary for:

• total processed records
• created, updated, skipped, and conflict counts
• any remaining warnings from validation or staging

Troubleshooting

The CSV preview looks wrong after upload

Go back to /settings/imports/[runId]/recognize and adjust the detected header-row count. Then confirm the entity type and preview table before continuing.

The wrong JobsiteOn fields were suggested

Use /settings/imports/[runId]/mapping to override the recommended mapping. Supported platform packs provide a starting point, but custom CSVs may need manual cleanup.

Linked jobs, quotes, or invoices are not matching the expected contact

Upload the contacts CSV in the same run and verify the email, customer name, or company values are present. JobsiteOn uses those imported contact records during staging to resolve related jobs, quotes, and invoices.

A Tradebase quote file looks too large in raw row count

That is expected. Tradebase quote exports contain proposal rows plus line-item rows. JobsiteOn groups those rows during parsing so the import operates on quotes, not every raw line item as a separate record.

Validation checklist

• The correct platform was selected for the run.
• All expected CSV files were uploaded.
• The preview shows the correct header row count and entity type.
• Required field mappings are complete before validation.
• Preview results match the records you expect to create or update.
• The summary page reflects the final import outcome after commit.

Related Articles

• Create and Manage Contacts
• Create and Manage Properties