Property Insurance
Import existing Insurance data
Purpose 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 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 |
Recommended migration order Recommended migration order
For most Insurance migrations:
- Clean and import sites.
- Create site groups for Insurance scope.
- Add site groups or individual sites to the Insurance board.
- Create the relevant Insurance period.
- Import values for that period.
- Import available COPE data.
- Configure responsibilities and import assignments.
- Import or create risk improvements and engineering report references.
- Review exports and analytics with stakeholders.
When to ask for assisted migration 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.
The best migrations start with site identity. Make sure each location has a stable site name or ID before importing values, COPE, responsibilities, or recommendations.