ArcticPulse

Data imports in ArcticPulse

How CSV validation, field mapping, confirmation and error reporting fit together.

Before importing

ArcticPulse is a private product in development. You can import data only if you have access to the correct organisation and property.

Use a CSV file that follows the template or fields in the version you can access. Remove unnecessary personal data and keep a secure copy of the source data.

The import flow

  1. Choose the correct organisation, property and import type.
  2. Upload the CSV file in the private ArcticPulse area.
  3. Review validation for columns, data types, dates and required values.
  4. Map source columns to the correct ArcticPulse fields if prompted.
  5. Read the summary and error report before confirming the import.
  6. Confirm only when the scope, mapping and result are correct.

When an import fails

Correct the source file or field mapping and run validation again. Do not repeat a confirmed import without checking whether that would create duplicates.

If the error message is not enough, create an ArcticPulse support ticket with the property and import reference, time and error code. Do not attach the full dataset unless support specifically requests it through secure upload.

Related articles