Published: 1 June 2026
Audience
This article is intended for:
- Administrators responsible for importing and managing customer data in PSOhub
- Users preparing contact data for bulk import
Objective
This article describes every field in the PSOhub contact import template. Use it to prepare your Excel file correctly before uploading, and to understand how each field is validated on import.
Prerequisites
You must have Admin or Controller access in PSOhub
Download the Template
Before you can prepare your import file, you need the official PSOhub template. The template contains the correct column structure that PSOhub expects on import — using any other file format or column order will cause the import to fail.
👉 Download the PSOhub contacts import template
⚠️ Important: Always use the template downloaded from PSOhub. Do not rename, remove, or reorder any columns. If you need a fresh copy, download the template again rather than modifying an existing file.
Prepare Your File
Before uploading your file, set up the import contact template correctly:
Fill in one row per contact. The RecordCount column is for your reference only and is not imported into PSOhub. Assign a number to each row.
Keep the following rules in mind as you fill in your file:
Email is the unique identifier. PSOhub matches incoming records to existing contacts by email address. If a match is found, the existing contact is updated rather than duplicated.
Company matching is exact. If the company name in your file does not match an existing company in PSOhub character for character, the contact will be created with a new company.
💡 Tip: Create the company record in PSOhub before importing your file. This ensures the contact is linked to the correct company automatically on import.
Date format must be consistent. Enter all dates in the same format throughout your file. PSOhub reads the date format as it appears in Excel, so inconsistent formatting across rows may cause some dates to import incorrectly.
Understanding the Import Fields
The table below describes every column in the PSOhub contact import template, including the expected format, accepted values, and any validation rules that apply on import.
| Field | Description | Type / Value | Notes |
|---|---|---|---|
| RecordCount | A row number for your reference. | Integer (1, 2, 3…) | Required. Not imported into PSOhub. Used for your own reference only. Each contact must have a unique ID. |
| Salutation | The contact's title or honorific. | Free text — e.g. Mr, Ms, Dr | Optional. Appears as entered in PSOhub. |
| First Name | The contact's first name. | Text | Required. Cannot be left blank. |
| Last Name | The contact's last name. | Text | Required. Cannot be left blank. |
| The contact's email address. | Valid email format — e.g. name@company.com | Required. Used by PSOhub to detect existing records. If a match is found, the existing contact is updated rather than duplicated. Must be unique per row. | |
| Job Title | The contact's job title or role. | Free text — e.g. Project Manager, CEO | Optional. |
| Company | The name of the company this contact is associated with. | Text | Optional. Must match an existing company name in PSOhub exactly for the link to be applied. |
| PhoneNumber | The contact's phone number. | Numbers only | Optional. Do not include spaces, dashes, or special characters. |
| DateOfBirth | The contact's date of birth. | Date | Optional. Use a consistent date format throughout your file. PSOhub reads the format as it appears in Excel. |
| IsPrivateCustomer | Indicates whether the contact is a private individual rather than a business contact. | true or false (lowercase) |
Required. For business contacts (associated with a company) this should be false |
FAQs and Troubleshooting
What happens if I leave the Email field blank?
PSOhub will not be able to check for an existing contact and may create a duplicate record. Always include a valid email address for every row.
My contact was imported but is not linked to a company. Why?
The company name in your file must match an existing company record in PSOhub exactly. Check for spelling differences, extra spaces, or punctuation mismatches, and ensure the company exists in PSOhub before re-importing.
The import failed after I uploaded my file. What should I check?
Confirm that the column headers in your file match the original template exactly. Adding, removing, or renaming columns will cause the import to fail. Re-download the template and copy your data into a fresh copy if needed.
Can I import contacts in a language other than English?
Contact names and job titles support free text, so non-English characters should import correctly. Validate this in PSOhub before importing a large file.