tags: domino, exchange, migration, notes, outlook
Enjoy Peter Presnell's insight gathered over a number of migration projects. Replacing an advanced messaging, application development, and web server platform like Domino is far from trivial. And the author has seen how it often goes down. If you care about quality of your environment, take note of this experience. Thanks to Peter for sharing.
Anyone considering a migration project would be wise to very carefully estimate both the full scope and budget of the effort, as well as the ability to continue support for existing usage patterns. Map how your users are actually leveraging the platform they have today. Don't assume you know.
Years ago, one of my first projects for IBM was to run beta tests for departmental cutsheet network printers. I'll never forget a particular customer: Great and very cooperative IT staff, but when they pointed me to their 'main' print queue, I found limited traffic. To make a long story short, they didn't realize many employees had switched their print jobs to alternate queues on alternate server clusters. Keeping up with all areas of usage is no small task. Know your users, especially when planning change projects, whether migrations, expansions, or other.