Preparing to Import Your User Data

ManyThis customersarticle wishprovides toOPS-COM portadministrators overwith the requirements and best practices for importing existing user data when they purchaseinto the OperationsCommander system. DataProper importsdata canpreparation beis complicatedessential but they start withfor a clearsuccessful understandingmigration ofand whatensures all user profiles, vehicles, and permits are correctly associated within OperationsCommander.

Data Preparation Strategy

Before initiating an import, ensure your data is neededclean and clean data. A Data Import may have been included with your systemstrategy purchaseis orclearly it may incur additional costs.  You can also make use of our Data Importer (BETA).  Contact your Account Executive or email support@ops-com.comcom to find out.defined.

Preparing your User Data

Clean Data

After exportingExport your data from your currentlegacy system,system youand mustperform cleana thethorough data.cleanup:

This

includes
• removing

  Remove duplicate entries,entries.

  correcting
typos,
• and

  Correct ensuringtypographical consistenterrors.

  data

• Standardize formatting (e.g., date formats, capitalization)capitalization, and phone numbers).  

Data Strategy

You must decide onDefine your User Management strategy:strategy before starting the import process:

• What will

  Unique youID: use forSelect a User Unique ID?ID Will it be(e.g., email address, username, or student/staff number? number). InThis orderID is mandatory for you to stack data in the system, you must start by importing your users and populating a unique ID. This will then allow you to bring in morestacking data and tagassociating itfuture records (like vehicles or permits) to the correct users.user. Ensure this ID is never duplicated.

• Whatever  you

  SSO: chooseIf foryour Uniqueorganization IDutilizes mustSingle notSign-On be(SSO), duplicated.determine your required login source.

• Will your

  Mandatory usersFields: beIdentify settingwhich upuser forprofile SSO?details Ifare sorequired.

  you
need
• to

  System determineConfiguration: Ensure the loginfollowing sourceareas forare this.

configured
• Whatin details will you consider mandatory for a user profile?

Your OPSCOM system must be setup and some configuration doneOperationsCommander before importing your data. The following must be configured:importing:

• User Types

• Lots

• Vehicle types, colorscolors, and makes

• Login sources

• User profile settings for mandatory fields.fields

Data Mapping

AnyTo fieldensure thatsuccessful isimports, allowedyour toCSV befile importedheaders intomust OPSCOMmatch isthe outlinedsystem's expected attributes.

1. Review the Request Object Attributes section in the API documentation to identify the RequestPossible Object AttributesNames sectionand Limits for eachevery API document.  For example iffield you areintend pushingto inimport.

   Users,
you
2. would

   Ensure reviewyour 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 Requestspecified Objectcharacter Attributeslimits.

   sectionf
for

4. Follow the User Create/Update API to find out what the name is for each column header you wish to import (Possible Names) and if there are any limits to what that field accepts in OPSCOM (Limits). Below is an example.  If you are importing users, the columnsteps in the CSVUsing filethe mustDatabase beImporter labeled(Beta) unique_idguide andto itbegin mustthe notupload haveprocess.

   more
than 50 alphnumeric characters including any dashes.

Unique ID

String

50-character alphanumeric including dashes.

unique_id

(Required) An unique identification number of the user.

Build out your CSV file with the column headers that match the data you are bringing into OPSCOM and follow the steps in the Data Importer documentation to begin importing. 

Building on yourYour Data

Once you have imported your users, you should now have ainitial user recordimport withis a Unique ID thatcomplete, you can nowbegin addadding vehiclerelated ordata.

permits

to.
• You will reference

  Use the Unique ID forestablished during the user inimport eachto newassociate CSVsubsequent filerecords you(such createas so that the vehicleVehicles or permit gets associatedPermits) to the correct user profile in thefuture system.CSV uploads.

Post-Import Actions

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

• Verification: Perform a spot-check of the imported data to ensure it's correct. You should check a fewvarious user profiles and vehicle records to confirm that theall information has been importedmigrated accurately.

• Error Log Review: YouMonitor will get anyour email withfor athe post-import error log. This willdocument explainis whichcritical for identifying and troubleshooting any records that failed andto why. This is a critical step for troubleshooting and fixing issues.import.

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.

---

Best Practices and Considerations

• Data Integrity: Prioritize the accuracy of your Unique ID, as this is the foundation for all future data associations in the system.

• 
  Consultation: Reach out to the support team if you are unsure about mapping specific fields or encounter unexpected errors during your initial import tests.