The following mapping example aims to populate a target system equipment register as described in Table A5.1 within an ERP application.

You can see the fields that need to be populated (mandatory) from a target system viewpoint. This is, however, only the technical view of ‘mandatory’. Although the target system might allow you to create records with some fields unpopulated, the business processes mandate the completion of many other fields. You would also like to provide as rich a dataset as possible, so in the course of your analysis you have found source data for as many fields as possible. Looking at Table A5.1 field by field:

  • Equipment ID – This is a system-generated unique key, so you do not have to provide any ...

Get Practical Data Migration now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.