In my experience with migrating data between two different standards, the worst part of the whole process is building crosswalks. Essentially the way that I’ve built crosswalks in the past is to write out how each destination feature class or table is going to get migrated on its own Excel sheet. The Excel sheets do a good job in telling the story of how the data is going to be migrated, but that’s about all they are good for. You still have to wire up an ETL tool based on what is in Excel, which for large migrations can be a fairly large task. If crosswalks need to be changed, they have to be updated in Excel and then again in the ETL tool. So there is a large duplication of effort just to be able to have a document that explains how the migration will happen. The larger the migration, the more Excel sheets you have, which then presents a whole new problem with maintaining all of the crosswalks and tools. I have a small example that I will use throughout this how-to to show the problem and the solution. It’s fully scalable, so it doesn’t matter if you are migrating one feature class or a thousand; this is a good way to handle crosswalks in the future.
If you are interested in learning more about attribute cross walking, ETL, data migration, SchemaMapper, or the Data Interoperability Extension then please continue on to the rest of my piece on building attribute and value crosswalks in Esri's Data Interoperability Extension.
You can click the read more link below or view the document as a PDF.