Skip to content

Import branches and branch contacts

Both imports require an existing client and run in the background after the dialog closes. Each successful row is saved independently; a later failure does not roll back earlier rows.

Import branches

  1. Open Import Branches and select the import action.
  2. Download BranchImportTemplate.csv and keep its first header row.
  3. Choose the target region.
  4. Upload the CSV and select Submit.

The importer requires Branch Name. It reads address, city, state, ZIP, contact name, contact phone, contact email, and branch number from the remaining columns. Use state abbreviations and the supplied template.

When processing ends, BranchImportLog.txt is emailed to the signed-in user's profile email.

Import branch contacts

  1. Open Import Branch Contacts and select the import action.
  2. Download BranchContactImportTemplate.csv and keep its first header row.
  3. Choose the target branch.
  4. Upload the CSV and select Submit.

Each row requires first name, last name, title, and at least an office or mobile phone. The remaining fields are extension and email. All imported contacts attach to the selected branch.

When processing ends, BranchContactImportLog.txt is emailed to the signed-in user's profile email.

Reconcile an import

Review the full log even when new rows appear. Empty lines made only of commas are ignored; other malformed rows are logged. Because imports are not atomic, compare every source row against the resulting hierarchy before retrying. Reimport only failed rows after checking for duplicates.

Update your profile email before starting if the destination shown in the dialog is incorrect.