Property Insurance

Import existing Insurance data

Purpose

Most Insurance teams already have important data before they start using 21RISK. It may live in spreadsheets, broker templates, engineering report files, ERP systems, asset registers, or local site owner lists.

21RISK supports several import paths so you can move from existing data to a structured Insurance board without starting from scratch.

Import paths

Data Recommended path
Sites and hierarchy Bulk import sites
Site custom fields Create custom columns first, then use site import or site table editing
Insurance values Bulk import values
COPE area Bulk import COPE
Responsibilities Bulk import responsibilities
Risk improvements Use risk improvement creation workflows or assisted import where needed
Engineering reports Use Engineering Reports or assisted migration where needed

For most Insurance migrations:

  1. Clean and import sites.
  2. Create site groups for Insurance scope.
  3. Add site groups or individual sites to the Insurance board.
  4. Create the relevant Insurance period.
  5. Import values for that period.
  6. Import available COPE data.
  7. Configure responsibilities and import assignments.
  8. Import or create risk improvements and engineering report references.
  9. Review exports and analytics with stakeholders.

When to ask for assisted migration

Ask for assisted migration when your data has complex relationships, many custom fields, historical periods, engineering report mappings, or GRC integration requirements.

Assisted migration is often useful when:

  • Existing spreadsheets use inconsistent site names.
  • Historical periods need to be preserved.
  • Risk improvements need to be linked to engineering reports.
  • External IDs need to be mapped to GRC or broker systems.
  • COPE data needs custom mapping.
previous Engineering reports
next Automations