The Migration

You kick off a project or endeavor that creates a fair amount of data per day. There happens to be a tool purposely designed to handle the kind of data you generate. Such a tool would make your life so much easier. It would make it auditable for your customers. Secure. Manageable.

Tool is proprietary and commercial. You are at an early stage; you can’t afford it.

You go on creating loads of data every day as your venture matures. Because you lack the tool, your data grows unstructured as you get by with a collection of cheap substitutes: an inelegant troupe of spreadsheets and files of obscure formats.

You dream of the day you will be able to put all your data into that perfect, glossy tool.

A day that most likely will never come.

The earlier data migration can happen, the—significantly—easier to handle; this is, before data gets too spread, divergent and messy.

But the earlier you are, the less likely you are of having the wherewithal to acquire the tool and secure a better data administration, so your information keeps on growing in a disorganized style.

At a given time, you have saved enough to buy the goddamn thing, but your data is already an unmanageable, unholy hairball and the migration process becomes a project in itself.

You don’t feel like adding this to your plate. There are more important things at the moment. There will always be more important things.

Migration never happens. Your data becomes like a Canada goose who decides not to fly south but stay waddling and shitting indefinitely around your local park.