# Preparing to Import Your User Data

<p class="callout info">This article provides OPS-COM administrators with the requirements and best practices for importing existing user data into the system. Proper data preparation is essential for a successful migration and ensures all user profiles, vehicles, and permits are correctly associated within OperationsCommander.</p>

### Data Preparation Strategy

Before initiating an import, ensure your data is clean and your strategy is clearly defined.

#### Clean Data

Export your data from your legacy system and perform a thorough cleanup:

- **Remove duplicate entries**.
- **Correct typographical errors**.
- **Standardize formatting** (e.g., date formats, capitalization, and phone numbers).

#### Data Strategy

Define your **User Management** strategy before starting the import process:

- **Unique ID**: Select a **Unique ID** (e.g., email address, username, or student/staff number). This ID is mandatory for stacking data and associating future records (like vehicles or permits) to the correct user. Ensure this ID is never duplicated.
- **SSO**: If your organization utilizes **Single Sign-On (SSO)**, determine your required login source.
- **Mandatory Fields**: Identify which user profile details are required.
- **System Configuration**: Ensure the following areas are configured in OperationsCommander before importing:
    
    
    - **User Types**
    - **Lots**
    - **Vehicle types, colors, and makes**
    - **Login sources**
    - **User profile settings** for mandatory fields

### Data Mapping

To ensure successful imports, your CSV file headers must match the system's expected attributes.

1. Review the [Request Object Attributes](https://opscom.wiki/books/api-documentation/page/push-api-user-createupdate#bkmk-360) section in the API documentation to identify the **Possible Names** and **Limits** for every field you intend to import.
2. Ensure your CSV column headers align exactly with these attribute names.
3. Build your CSV file, ensuring that all **Required** fields, such as **unique\_id**, adhere to the specified character limits.
4. Follow the steps in the [Using the Database Importer (Beta)](https://opscom.wiki/books/setup-configuration-for-admins/page/using-the-database-importer-beta) guide to begin the upload process.

<table class="wrapped confluenceTable tablesorter tablesorter-default" id="bkmrk-unique-id-string-50-" role="grid" style="width: 100%;"><tbody aria-live="polite" aria-relevant="all"><tr role="row"><td class="confluenceTd" style="width: 9.17759%;">Unique ID</td><td class="confluenceTd" style="width: 8.46246%;">String</td><td class="confluenceTd" style="width: 31.466%;">50-character alphanumeric including dashes.</td><td class="confluenceTd" style="width: 12.2742%;">unique\_id</td><td class="confluenceTd" style="width: 38.6197%;">**(Required)** An unique identification number of the user.</td></tr></tbody></table>

### Building on Your Data

Once your initial user import is complete, you can begin adding related data.

- Use the **Unique ID** established during the user import to associate subsequent records (such as **Vehicles** or **Permits**) to the correct user profile in future CSV uploads.

### Post-Import Actions

After the import process concludes, perform the following steps to ensure data integrity:

- **Verification**: Perform a spot-check of various user profiles and vehicle records to confirm that all information migrated accurately.
- **Error Log Review**: Monitor your email for the post-import error log. This document is critical for identifying and troubleshooting any records that failed to import.

<p class="callout warning">Data imports can be complex and may incur additional costs. Please contact your **Account Executive** or email **support@ops-com.com** to confirm whether a data import is included in your system purchase or to learn more about the **Data Importer (BETA)** tool.</p>

---

### <span style="color: rgb(22, 145, 121);">Best Practices and Considerations</span>

- <span style="color: rgb(22, 145, 121);">**Data Integrity**: **Prioritize the accuracy of your Unique ID, as this is the foundation for all future data associations in the system.**</span>
- <span style="color: rgb(22, 145, 121);">**Consultation**: Reach out to the support team if you are unsure about mapping specific fields or encounter unexpected errors during your initial import tests.</span>