Topics on this page

Data conversion configuration

Data conversion involves converting client data (like contacts, policies, claims, notes, properties, etc.) into a file that is compatible with the BriteCore schema. For each input file, there is a corresponding filter file that maps each column to a predefined column name.

The conversion process uses client input files, normally CSV files, and then generates a proprietary import file. The conversion process can either be run monthly or as a one-time bulk import.

There are several configuration files for the different data types (properties, contacts, etc) and there are preexisting classes and libraries that handle most of the import process, but a good amount of development work is normally needed to finish a new conversion.

Data conversion options

Below are the conversion options available:

Data conversion guidelines

BriteCore provides data conversion templates so you can get an idea of what the data required by the conversion process looks like.

In addition to the templates, keep these general guidelines in mind:

Desired file format

Ideally, data should be provided in CSV format, but XLS or other easily converted formats work as well. Format consistency is essential, as scripts will be written for any general format conversion that may be necessary.

Missing data points

If there is information you expect to convert that isn’t listed in the spec, include it in your file. Be sure to tell us specifically about those data points, or they may get overlooked.

Unavailable data points

If there is information listed that can’t be provided, contact us to discuss options.

Column naming/renaming and constant values

It isn’t required that your output file’s columns exactly match the specs listed for each section, but if they don’t, please provide a file that defines the relationship of your columns to our desired columns.

The format is simple:

Your Column Name|Our Desired Column Name #

Comments are supported.

Note: All columns that will be used in the conversion must be included in this file, even if no translation is required. This file, if present, provides both column filtering and renaming.

Additionally, if a column has a constant value, it can be completely defined in this mapping/filter file as follows:

|Column Name = Column Value

For example:

  • POLICY NUMBER|policyNumber
  • Orig Eff Date|inceptionDate
  • effectiveDate # This is the policy effective date
  • |policyStatus = Active

If these files are provided, please use the affected CSV file’s name postfixed with .filter as the file’s name. For example:

  • policies.csv –> policies.filter
  • properties.csv –> properties.filter

Policy/Policyholder information

The data in this section should define the most basic policy and policyholder information.

If possible, please provide this data in a single file. You can use any file name, but the file name must remain consistent through the process and should clearly indicate the file’s contents.

Possible content (* indicates required)

  • policyNumber* – The number with which the policy should be converted.
  • inceptionDate* – The original effective date of the policy.
  • effectiveDate* – The current policy effective date.
  • expirationDate* – The current policy expiration date.
  • termLength* – The length, in months, of the policy term; it can be calculated on our end from effective date and expiration date.
  • policyStatus * – An indicator of policy status, such as active versus cancelled.
  • lineOfBusiness* – An indicator of the Line of Business used to map to a specific BriteCore policy type. Depending on Lines setup, more information may be required to select the policy type.
  • nameX* (where X is 1, 2, 3, etc.) – Insured name(s). If all contacts are in a single field, you can provide the value as name1 and our code will attempt to parse out individual names.
  • dobX (where X is 1,2,3, etc.) – Insured’s date of birth. Must correlate with nameX.
  • ssnOrfidX (where X is 1,2,3, etc.) – Insured’s SSN or FID. Must correlate with nameX.
  • phoneX (where X is 1,2,3, etc.) – Insured phone numbers. All phones are added to all insureds.
  • phoneTypeX (where X is 1,2,3, etc.) – Phone number type (home, work). Must correlate with phoneX.
  • emailAddress – Primary insured’s email address.
  • addressLine1* – Insured address line 1.
  • addressLine2* – Insured address line 2.
  • addressCity* – Insured address city.
  • addressState* – Insured address state.
  • addressZip* – Insured address ZIP
  • agencyIndicator – A value indicating the agent associated with the policy. Only required for converting agent assignments.

Notes:

Dates are parsed with dateutil.parser.parse, so most formats are acceptable. If you can parse your format with this library, it’s acceptable.

At present, the conversion code assumes insureds share the same address as, to date, we haven’t received individualized information from any client. Updates can be made to support more individualized data points if they can be provided.

If address components aren’t available, you may provide a single address string in addressLine1 and the conversion process will attempt to parse the address. For the best results, you should still provide any components that you have available separately.

Property/risk information

The data in this section should define all basic information for the Property/Risk tab. If multiple locations exist, there should be multiple rows for each policy, and a location number indicator must be provided.

If possible, please provide this data in a single file, sorted by locationNumber. You can use any file name, but the file name must remain consistent through the process and should clearly indicate the file’s contents.

Possible content (* indicates required)

  • policyNumber* – The number with which the policy should be converted.
  • locationNumber – The risk/location number used for ordering; it can be omitted if only one location is possible.
  • line1* – Address line 1 of the risk.
  • line2 * – Address line 2 of the risk.
  • city* – Risk city.
  • state * – Risk state.
  • zip* – Risk ZIP.
  • county* – Risk county.
  • … other risk fields, such as Driver, Vehicle, Property, etc.

Notes:

The conversion process, like BriteCore, will look up city and state information based on ZIP code if necessary. However, since ZIP codes aren’t necessarily 1:1 correlated with counties, the correct county may not be selected if it isn’t provided. For best results, provide all data points.

If the address components are not available, you may provide a single address string in line1 and the conversion process will attempt to parse the address. For the best results, you should still provide any components that you have available separately.

Property/Risk builder information

The data in this section should define all information required to construct a BriteCore policy’s Builder screen. Due to the fact that Lines in BriteCore are custom to each site, it isn’t possible to give a specific set of information that is required.

If possible, please provide this data in a single file. You can use any file name, but the file name must remain consistent through the process and should clearly indicate the file’s contents.

Possible content (* indicates required)

  • policyNumber* – The number with which the policy should be converted
  • locationNumber* – The risk/location number–used for ordering

Other required content

Other required columns are completely dependent on your site’s Lines setup. As such, we can only provide a guideline on what to include. That guideline is:

  • Include any and all information necessary to determine coverage options and inputs for a BriteCore policy’s builder.
  • Likewise, the naming convention is up to you, but to avoid confusion, an ideal format is:
    • Item Name.Input Name

The data you provide in this file will be mapped to BriteCore via a YAML file, which defines the relationship of the file contents to the Lines setup of a given BriteCore site.

Policy-wide builder information

See Property/Risk builder information, but omit the locationNumber requirement.

Document conversion

Some clients have used Docfinity (or similar tools) to convert documents when they switched to BriteCore’s core system. BriteCore offers an FTP scanning process where a client can upload all the converted documents into their respective folders by policy number. We can store and index them automatically in the Attachments module.