Our organization (ITD/NSD, 6,000+ people globally) is going to be outsourced to AT&T late this year or Q1 2008. We are looking for a way to migrate our request tool (currently in Domino) to a different language and platform. This tool will still be used to engage us by IBM for IBM projects once we are re-badged as AT&T employees. I am not sure what OS will be using at AT&T with new machines. The other option to re-writing/migrating is to use existing tool with access priveleges modified to allow continued use as-is. No idea how this would work in a non-Lotus environment. I’m pretty sure AT&T uses MS products exclusively. Does anyone know what our options might be?
Thanks in advance for any help…
Subject: Converting Domino Code to another language
You really don’t seem have enough information to know your options yet.
Find out what platforms the IT organization that will be supporting you prefers. (Even within the MS world, if that’s really all they have, there are still multiple technology choices.)
Then hire one or more consultants who are fluent in both Lotus and the target technologies, and get some estimates. Double the estimates. Then compare that cost to what it will cost in order to either get your new IT organization to support your pre-existing working Domino-based application.
And if anyone tries to convince you they have tools that can do the job cheap and easy, don’t believe it. Make them prove it.
-rich
Subject: Converting Domino Code to another language
Domino can authenticate against an LDAP store, so it should be possible to get it working with Active Directory. Build a web interface for the users and access that via your intranet.
You’d still need a Dom server and a client or two to admin it, but it shouldn’t be THAT hard to make work.
You’ll have to steel yourself for all the anti-Notes feelings from all the MS people. Every time anything goes wrong, you know who will hear it. 
Otherwise, moving it to another platform like .NET is pretty much a complete rewrite. Its really different outside of Notes. Planning a normalized relational database, caching and sessions, datagrids and all that stuff.