 a particular region or set of customers (optional) Identifying Key Data Components. First, all data sources for each target application, i.e. the applications into which data will be migrated, must be identified. This is done on a region by region or customer segment by customer segment basis, depending on the IICs diversity in these areas, and the nature of its data and how it's organized. Data sources may be legacy systems, electronic files or paper. Second, the IIC must identify all data fields and data structures required for the target applications. Data analysis of both the source and target data fields and structures is necessary to identify gaps, overlaps and areas where certain systems cannot accommodate the data they are supposed to, or where more than one system houses or requires the same data. Some target data may only be available if derived from other data using legacy business processes. This might be the case where the data being moved is not as detailed or broken into as many levels of hierarchy as the target application expects. Also, some data may have default values that need to be captured. Some organizations find that using a "staging database" is helpful to structure the data migration. Legacy data would need to be extracted and normalized within this interim staging environment, prior to loading into the target applications. Data Cleansing and Mapping. Each data element level between source and target systems needs to be mapped, while considering the business context. In other words, the old data must be reorganized into categories and hierarchies that the target application can understand and that make sense from a business perspective. This process is almost like moving into a new house and making sure everything is packed in the proper order to be "dropped in." In some cases, business processes must be reviewed to identify any data transformation needed between source and target systems. Data Chapter 7 - Supporting the Life of an OSS Integrated Platform discrepancies such as unmapped 