You don’t know what you don’t know. You know?

StethoscopeOne of the most often asked questions about Lotus Quickr in its golden years has been “what do I have?” — meaning, on the server and in the places. This is the case with any self-service platform and has been especially pertinent with Quickr, as IBM has unintentionally made some of its migration requirements quite difficult to get your head around. A basic for-instance: the requirement that all workflows be complete before starting to migrate a place. Super, makes sense. Except that there’s no way to tell this in the product, no “outstanding workflow” view, and no simple way of determining for which places, rooms, and forms workflow is even turned on!

There are a myriad of other “requirements” and a list of things that do and don’t migrate to take into account — if only you could quantify and identify them. If you have 100 places, you likely have 500 or more databases including rooms. So in 500 databases, can you easily identify where you have lists? Active calendars? Tasks? HTML forms? None of these items migrate, so you probably at least want to know where they are in order to interface with the managers of these places to determine how active and important they are. At best, you’d want to produce a list of them, identify which are active within a certain time period, and through the application of a few algorithms be able to classify a Quickr place as a good, moderate, or bad candidate for migration — and then do the same for your archiving strategy.

HTML forms are my next best example. If you have done any customization in the 14 years you’ve been able to, you may have some of these powerful things lying around. They don’t migrate to CCM…or do they? In fact, it’s not impossible. Programmatically, you can convert the content in an HTML form to a simple form, then it can be migrated (assuming there’s attachments involved). The migration of simple forms to CCM is hoky, but it can be done…with some volume limits.

Having spent years making Quickr efficient, lean and mean for large deployments, I have access to SNAPPS tools that slightly modified can tell us just these things. Depending on volume, in fairly rapid fashion I can tell you how ready you are for a CCM migration, how much work there is to do, and estimate the percentage of your Quickr content that will be preserved. It’s part magic tools, part intuition, and part experience, like any in depth analysis.

I mention all this because I’m currently in different stages of this kind of analysis with four Quickr clients, all of whom just don’t quite know what they have. That’s the common factor, and the result of years using a powerful, self-serve, customizable platform like Quickr. In fact for two clients, I’m even running demonstration projects to migrate a single place to CCM in order to show them the results, but in a safe lab environment using LDAP mapping to a lab directory. I’ll be doing a lot of those next year as more companies are figuring out what they want to do with Quickr. And, I intend to post some of the results here as I go. For now, it’s the larger environments that are starting to get concerned with what I’ve predicted as an April 2016 end of support.

But don’t worry, with enough money you can keep that going too… 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *