Migrating data from IBM InfoSphere Information Server to IBM Cloud Pak for Data (Watson Knowledge Catalog)

If you use IBM® InfoSphere® Information Server and want to start using IBM Cloud Pak® for Data, you can migrate your data.

Product versions supported for migration
Asset types that you can migrate
Data that you can’t migrate

Product versions supported for migration

You can export data from IBM InfoSphere Information Server versions 11.7.1.x and import this data to IBM Cloud Pak for Data.

Migrating analysis database, automated discovery results, and data rule and rule set run history is supported only from Db2® databases.

Prerequisite: You must have the Watson™ Knowledge Catalog service installed with Cloud Pak for Data.

Asset types that you can migrate

Asset types

The following table contains information about which asset types you can migrate and where you can find them in the Cloud Pak for Data user interface.

Table 1. Asset types migrated to Cloud Pak for Data
Asset type in Information Server	Location in Cloud Pak for Data
Terms	Governance > Business terms
Categories	Governance > Categories
Information governance rules	Governance > Rules
Information governance policies	Governance > Policies
Data classes	Governance > Data classes
Labels	Governance > Classifications
Bundle assets (open IGC assets)	Catalogs > Information assets
Common metadata assets: Implemented data resources (databases, data files) Business intelligence (BI) assets Physical data model assets Logical data model assets Data connections Contract libraries
Extension mapping documents and extended data sources
InfoSphere DataStage® and QualityStage® assets
InfoSphere Streams assets
Metrics
Workspaces	Governance > Data quality
Data sets
Data rules
Data rule definitions
Rule sets
Rule set definitions
Quality rules
Analysis results: column analysis, data quality analysis, data rule history, rule set history, overlap analysis, relationship analysis, cross-domain analysis, multiple column primary key analysis
Automation rules	Governance > Automation rules
Import areas	Catalogs > Metadata import
Data connections
Staging area assets

Only published versions of glossary assets are migrated (terms, categories, information governance rules, and information governance policies). In the target catalog, they are also imported as the published artifacts. If you want to migrate the content of the draft glossary, you must publish these assets before migration.

Important: When you migrate glossary assets and then remove any of them in the Cloud Pak for Data user interface, you cannot migrate them again. Glossary assets include terms, categories, policies, rules, data classes, and labels.

Glossary asset properties

The following tables contain a comparison of properties between glossary assets in Information Governance Catalog (IGC) and governance artifacts in Cloud Pak for Data.

Table 2. Term properties
Term in Information Governance Catalog	Business term in Cloud Pak for Data
Name	Name
Parent Category	Primary category
Short Description	Description
Long Description	Description
Status (Candidate, Accepted, Standard, Deprecated)	(Deprecated)
Referencing Categories	Secondary categories
Labels	Tags, Classifications (see note 1)
Stewards	Stewards
Governed by Rules	Related content
Abbreviation	Abbreviation
Additional Abbreviation	Abbreviation
Example	Description (see note 2)
Usage	Description (see note 3)
Is Modifier	(Deprecated)
Type	(Deprecated)
Is a Type Of	Is a type of
Has Types	Has a type of
Is Of	Is a part of
Has A	Has a part of
Synonyms	Synonyms
Preferred Synonym	Synonyms
Related Terms	Other related business terms
Replaces	(Deprecated)
Replaced By	(Deprecated)
Assigned Terms	Other related business terms
Assigned to Terms	Other related business terms
Assigned Assets	Secondary category when it’s a category in IGC Related artifacts when it’s a data class in IGC Not migrated when it’s an information asset in IGC
Notes®	(Not migrated)
Collections	(Deprecated)
History	(Not migrated)
Custom attribute values of type Text, Predefined Values, Date, Number	Details
Custom attribute values of type relationship	(Not migrated)

Notes:

When a classification with the same name as a label already exists in the target catalog, the classification replaces the label and assets are associated with a classification. In other cases, the label is converted into a tag.
The example content is prefixed with ‘Example’ in the description.
The usage content is prefixed with ‘Usage’ in the description.

Table 3. Category properties
Category in Information Governance Catalog	Category in Cloud Pak for Data
Name	Name
Short Description	Description
Long Description	Description
Parent category	Parent category
Labels	(Not migrated)
Stewards	(Not migrated)
Assigned to Terms	(Not migrated)
Subcategories	Subcategories
Contains Business Terms	(Not migrated)
References Business Terms	(Not migrated)
Collections	(Deprecated)
Notes	(Not migrated)
Custom attribute values of types Text, Predefined Values, Date, Number	(Not migrated)
Custom attribute values of type Relationship	(Not migrated)

Table 4. Rule properties
Information governance rule in Information Governance Catalog	Rule in Cloud Pak for Data
Name	Name
(New)	Primary category
Short Description	Description
Long Description	Description
Referencing Policies	(Not migrated)
Labels	Tags, Classifications (see note 1)
Stewards	Stewards
Related Rules	Related Rules
Implemented By Assets	(Not migrated)
Governs Assets	Related artifacts when it’s a term
Collections	(Deprecated)
Notes	(Not migrated)
Custom attribute values of types Text, Predefined Values, Date, Number	Details
Custom attribute values of type relationship	(Not migrated)

Table 5. Policy properties
Information governance policy in Information Governance Catalog	Policy in Cloud Pak for Data
Name	Name
(New)	Primary category
Parent Policy	Parent Policy
Short Description	Description
Long Description	Description
Labels	Tags, Classifications (see note 1)
Stewards	Stewards
Subpolicies	Subpolicies
Information Governance Rules	Rules
Collections	(Deprecated)
Notes	(Not migrated)
Custom attribute values of types Text, Predefined Values, Date, Number	Details
Custom attribute values of type relationship	(Not migrated)

Table 6. Data class properties
Data class in Information Governance Catalog	Data class in Cloud Pak for Data
Name	Name
(New)	Primary category
Short Description	Description
Long Description	Description
Example	Example
Labels	Tags, Classifications (see note 1)
Stewards	Stewards
Enabled	Enabled
Data Type	Matching method
Minimum Data Length	Minimum length of data value
Maximum Data Length	Maximum length of data value
Provider	Provider
Priority	Priority
Scope	Scope of code
Threshold	Threshold
Assigned to Terms	Related artifacts
Implements Rules	Related content
Governed by Rules	Related content
Collections	(Deprecated)
Notes	(Not migrated)
Custom attribute values of types Text, Predefined Values, Date, Number	Details
Custom attribute values of type relationship	(Not migrated)

Other data that you can migrate

Analysis databases
Automated discovery results
Quick scan results
Data rules and rule sets run history

Data that you can’t migrate

The following list details which data you can’t migrate. In some cases, you can recreate the data manually.

Users and their roles. You must recreate users manually in Cloud Pak for Data. Not all associations between assets and users are migrated. For more information, see Create users in the target Cloud Pak for Data system.
User groups. They are not supported in Cloud Pak for Data.
Draft glossary assets from Information Governance Catalog. To migrate such assets, you must publish them before migration.
Analysis results: primary key analysis, foreign key analysis, natural key analysis. You must run the analyses again.
Quality score. You must run the analysis again.
Suggested term assignments. You must run the analysis again.
Analysis database settings. You must configure the database settings manually.
Analysis settings. You must configure analysis settings manually.
Data source names (DNS). You must recreate them manually.
Unstructured data sources (IBM StoredIQ® assets).
Data Science assets (IBM Data Science Experience Local assets).
Lineage configuration. You must configure the settings manually. You can migrate lineage templates and filters.
Data rule bindings which are literal values. You must create literal values manually in Cloud Pak for Data and bind them to data rule variables.
Data classes with an additional regular expression defined. In Cloud Pak for Data, only one regular expression is supported. For more information, see Data classes.