Migration Minute...

Data Migration is special !

Data Migration is special and even a bit odd at times. If you have been part of the SAP project world, you probably agree. I have been doing SAP projects for 20+ years, and been involved in data migrations for some 12 years. The special position of data migration still amazes me sometimes. Data migration remains a dark horse within the SAP project landscape. Here is why I think this is:

1. It's considered complex. Many key users, project managers and consultants avoid the topic because it is conceptually hard to master. Data migration is on one hand a highly technical task involving LSMW, iDoc and ABAP. On the other hand, it requires building effective relationships with a demanding and sometimes vacillating business. Add a lot of elbow grease, long hours and a certain level of "artistry" into the mix. In terms of literature, there are only a few books available. There are a handful relevant SAP courses but no nice certification to brag about on LinkedIn. Let's say it's a niche area.
2. It's difficult to estimate. Data migration estimates are always off. Too low of course, and this can make project management "dislike" data migration. Data migration will usually take longer, cost more and uncover more problems than initially thought. Resources are always under pressure ("too expensive"). The data guys always seem to be under intense scrutiny, while other teams are lavishly funded. Life's not fair!
3. It's difficult to plan. Data migration can only start after the main functional design is on the paper, if it ever gets to that stage. You need to build a structured approach, which is often lacking at first. The initial Mock load results are required before important functional issues are solved and processes have been properly tested. Expect your migration to experience changes and bugs until the day before go live. That can be frustrating.
4. The burden of data validation. Loading data is one thing, but checking if it is correct and complete another. Data Rules, that specify the logic to distinguish between "dirty" and "clean" data, are almost never defined in an organization. Reporting capabilities to automate this task can shorten the post validation, but take time to develop and test. Often the work to sift through thousands of data records in Excel falls to the business key users. Some actually like this activity. For the other 99,999% of humanity, staring at Excel to find anomalies is just not a favorite activity.

Perhaps you have your own reason why you think data migration is "special". Some say the personalities involved are a factor as well. Is there a typical "data migration person"? Maybe someday, data migration will be just another standard task, who knows. Until then, let us try to enjoy it!