Classification Migration 

Classification Migration is a component that is used to migrate files and emails classified with other classification tools to Seclore Digital Asset Classification (DAC). Currently, migration from only Boldon James classification is supported.  

By configuring this component, all the existing Boldon James classified files will be classified with the mapped Seclore Classification label. When users open the file, they’ll see Seclore DAC visual markings.  

Further, to migrate existing emails that are currently classified with Boldon James, the Global Security Admins (GSA) will need to take the following steps:  

• Configure this component. 

• Create a content policy that includes the Boldon James header/footer. 

• Map the content policy to a Seclore DAC label. 

Once these steps are completed, users who reply to or forward existing emails classified with Boldon James will see a suggestion to classify the email using the Seclore DAC label specified in the content policy.  

For more information on how to create a content policy and how it works see this article.  

To ensure seamless migration, it is important to:

1. Uninstall Boldon James from end user's machines.

2. Upgrade to the latest Seclore Desktop Client and upload the following additional patches in the Policy Server:

• Classification Migration 1.0.0.0
• Customization Patches

3. Configure Classification Migration in the  Policy Server.

 

Now, let’s see how to configure this component.

Go to the Component Configuration section in the Policy Server portal. 

Click Add Component.

 

 

Let's go through component details along with each parameter and its value.

 

Component details

 

• Component Name: Third party Classification Migration
• Component ID: Seclore.ClassificationMigration 

Note: The ID is case sensitive. The component's name is customizable by the organization, but its ID must remain unchanged.

 

Click Add Parameter to add the following parameters.

 

Existing Classification Agent

This parameter defines the source Classification Agent for migration. As of now, only Boldon James is supported, therefore, this is the only value that can be configured. 

This is a mandatory parameter for the migration to work.  

 

• Parameter Name: ExistingClassificationAgent
• Parameter Type: String
• Parameter Value: Boldon_James

 

Total Users in Organization

The parameter indicates the approximate user count within your organization. This is a mandatory parameter.

 

• Parameter Name: TotalUsersInOrganization
• Parameter Type: String
• Parameter Value: Enter a valid number.

 

Label Mappings

This parameter enables mapping of current classification labels to Seclore Classification labels using their label IDs. 

This is a mandatory parameter.

 

• Parameter Name: LabelMappings
• Parameter Type: String
• Parameter Value: {“Boldon_James_LabelID1”:”Seclore_DAC_LabelID1”, “Boldon_James_LabelID2”:”Seclore_DAC_LabelID2”} 

Note: The input must be a valid JSON. You can map multiple labels by separating them with commas.

 

Max Retrial Count

This parameter defines the maximum number of migration attempts for a file in case of failure instances, such as the file being in use, etc. (failure instances where migration can be attempted again).

This is an optional parameter.

 

• Parameter Name: MaxRetrialCount
• Parameter Type: String
• Parameter Value: Enter a valid number.
  (When this parameter is not configured, it assumes a default value of 3 . However, if it is set, it must be a valid number for the migration to work properly.)

 

Click Save when you're done. The changes may take up to 24 hours to be applied.

 

After configuring the component, files and emails classified with Boldon James will be migrated to Seclore DAC.

This implies that the Boldon James metadata and visual markings will be replaced by Seclore DAC's metadata and visual markings for the files and emails. 

• Old Office formats (doc, xls, ppt) will have only metadata migrated, excluding visual markings.
• For PDF files, Boldon James metadata, header/footer will be migrated, but the watermark won't be migrated.

Administrators can verify the migration by downloading the Classification activities report from the Policy Server. For more information on how to view Classification activities see this article.