© Information Disciplines, Inc., Chicago—1 December 2009
NOTE: This document may be circulated or quoted from freely, as long as the copyright credit is included.
In the 1970s we began to talk of "data migration" to describe the process by which computer files would move from online storage to an archival or backup medium. The obvious analogy was to the seasonal migration of birds or the occasional migration of groups of people. It was, of course, the data files that were doing the migration.
The term was later extended to the conversion of files or whole computer applications. The accounting system might migrate to a new machine. Although that usage strained the analogy with birds and populations it was still understandable.
But then the terminology changed. We began to see the word used in a transitive sense:
"We have to migrate all our data before January 1."
Now it wasn't the data files that were doing the migration; it was the staff doing it to the data files. That new usage was in conflict with the dictionary definitions of the word. Here's what the Que Programmer's Dictionary1 said about it in 1993:
Migrate often connotes multiple individual actions over an extended or indefinite time period. Avoid using the term as a synonym for either convert or move.
Nevertheless, such misusages persist, to the point where Microsoft's Encarta College Dictionary2 has capitulated. After three conventional definitions it offers this:
While I usually respect the Encarta, I strongly disagree here on the grounds of both precision in writing and necessity. This usage fills no need. Why not just use the more descriptive terms move, transfer, transmit, convert, etc.?
Return to Business & culture articles
IDI Home Page
Last modified 1 December 2009