Skip to main content

Running a PVM Policy Import End to End

Overview​

This guide explains how to complete a PVM policy import from start to finish, from uploading the source file to verifying the imported data in ViSN.

Before You Start​

  1. Ensure the source file is available:
    • pvmFleetFile.csv
  2. Ensure the import schedulers have already been created.
  3. For scheduler setup steps, see Creating PVM Policy Import Schedulers.
  4. Ensure sub-customers exist in ViSN if the file uses location (Purchase Location Code).

Step 1: Upload the File​

  1. Open the correct storage bucket for the target environment.
  2. Navigate to imports/fileDrop/.
  3. Upload pvmFleetFile.csv.
  4. Confirm that the file is present before continuing.

PVM file loaded in bucket

Step 2: Run the Fleet File Import​

  1. Open Cloud Scheduler.
  2. Find the pvm_policy_fleet_file_import job.
  3. Run the scheduler.
  4. Wait for the job to finish.
  5. Confirm that the job completed successfully before continuing.

Run PVM fleet file import scheduler

PVM fleet file import log

PVM fleet file Firestore import log

Step 3: Log in to ViSN​

  1. Log in to ViSN as the customer.
  2. Open the correct customer account or lease context.

Step 4: Open the Policies Page​

  1. Navigate to the Policies page in ViSN.
  2. Open the policy list for the relevant lease or customer.

Step 5: Confirm the Imported Vehicle Is Visible​

  1. Search for one of the vehicles included in the import file.
  2. Confirm that the vehicle is listed on the Policies page.
  3. If the vehicle is not visible, recheck the import status and logs before continuing.

Imported vehicle visible in ViSN

Step 6: Open the Policy Details​

  1. Click View for the imported vehicle.
  2. Open the policy details page.
  3. Confirm that the page loads correctly for the selected vehicle.

Policy details page vehicle section

Step 7: Verify the Imported Policy Data​

  1. Confirm that the vehicle details are correct.
  2. Confirm that the expected policy records are present.
  3. If the source file contained multiple policies for the same vehicle, confirm that they appear under the same vehicle record.
  4. Confirm that the policy holder details are correct where applicable.

Policy details page policy section

Policy details page policy holder and policies section

Status: Pending Approval
Category: Protected
Authored By: Aditya on Jul 16, 2026