article page | 1 | 2 | 3 |

different, but some of the factors that should be considered before embarking on an MDM initiative include:

1. Ensuring that the business takes priority
   Like any application migration project, it’s essential that business priorities take precedence and the business users drive the project. Only business users can decide which datasets should be consolidated or migrated first, which datasets do not need to be migrated, how to resolve data conflicts or variants, and so on. In addition, getting buy-in from business users means that new data management processes are more likely to be adhered to going forward.
2. Taking small steps
   This type of project is complex and you need to approach it as a series of inter-related projects, each with its own goals and deadlines, but each of which fits within the overall goals of an MDM strategy.
3. Developing the master data model
   What do you want your master data records to include? This step should include understanding the producers and consumers of master data, and mapping between current data sources and the master data model. At this step you will need to recognise inconsistencies and resolve how you are going to handle them. For example, which naming convention will you use consistently for your customers? (e.g. Mr John Smith, Mr J Smith, Mr J. Smith, John Smith, Smith J.)
4. Choosing an appropriate tool
   There are various tasks that you will need to perform in order to create a master data list. You will need to clean, normalize, and standardize your data, as well as de-duplicate it. It is helpful if you have a tool that gives you a high degree of dynamic control and visibility along with bi-directional synchronisation. These features will certainly make the process of creating master data lists easier.