Legacy Modernization Software Migration Services

• Software Modernization Services
  • Lotus Notes to SharePoint 2010 Migration
  • Natural Adabas to JAVA/.NET Reengineering
  • VB to .Net Conversion
  • VisiCodeMiner Business DNA
  • Enterprise Reengineering
  • Cognos to Microsoft BI Migration
• Support & Maintenance Services
  • Remote DBA Services
  • BizTalk/SharePoint Integrated Solutions
  • SAP Solutions and Services
  • IT Outsourcing
  • Outsourcing Software Testing
  • Application Development
  • Application Maintenance
  • Business Intelligence Solutions
  • webMethods Development
  • Microsoft SharePoint Server 2010
  • Business Process Management
  • Microsoft BizTalk Server
  • IT Staffing
• Business Process Outsourcing
  • Title Services
  • Appraisal Services
  • Origination Services
  • Loan QA/QC Services
  • Curative Services
  • Underwriting Services
  • Commercial Mortgage
  • Flood Services
• Industry Solutions
  • Manufacturing & Retail
  • Mortgage & Banking

Legacy Modernization data migration tools and methodology used for the conversions of RPG, PowerBuilder, VB, Lotus Notes & Natural Adabase into J2EE/.NET, Java Client Server, Java Web Based, .NET, SharePoint & JAVA/.NET

Visionet has defined two extensive categories for migration projects based on modern trends in the industry: 

Technology Migration Offerings

Legacy applications (RPG, PowerBuilder, Visual Basic, Lotus Notes, Natural Adabase, C++/VC++, etc) to multi tier applications based on J2EE, dot Net, or SharePoint. 

Platform Migration Consulting

100+ large scale platform migrations and system re-writes. Applications running on old server platforms need to be ported to latest application server platforms. 

Legacy Application Conversion: Automated vs. Manual

• Automated tools are primarily targeted for client server to client server conversions. Web based architecture is significantly different and does not lend itself to automated conversion
• Automated conversion tools always have limitations that need to be fixed manually:

• UI elements in PB use PB Units for layout, whereas in Swing it is Pixels, so generated UIs need to be touched up
• UI element behavior is not the same between PB and Swing: setEnabled vs. setEditable
• Emulating too much PB means you lose opportunities for optimized Java code, use of interfaces in Java for constants is more efficient than a constants class, use of java.lang.String vs. java.lang.StringBuffer
• JVM memory management uses a garbage collecto,r so object reference clean up is important to ensure there are no memory leaks
• Swing does not have a masked edit control, so a third party component needs to be used.

• Because of these issues, a detailed test plan of the converted app needs to be developed to verify things that may not have been converted. This creates a big project risk on the quality and coverage of test cases.
• Java is a multi-platform community-based technology. As such, there are subtle, yet important differences between different JDK versions on the same platform and the same JDK versions on different platforms. Automated tools target specific JDK versions on specific platforms which may not be the same as in your environment

Value Proposition

• 10+ years supporting strategic and tactical solutions for the IT industry – Started as a AS/400 Y2K migration business
• Application Migration Excellence for migration / reengineering analysis
• Proven and well defined methodology in migration / reengineering
• 100+ large scale platform migrations and system re-writes
• A diverse team of 850 plus professionals
• Strong resource base with migration tools and knowledge process expertise
• Track record of building scalable, and reliable enterprise class solutions for Fortune 500 companies (On-site; On-Shore; Off-Shore)
• Metrics- Based approach in migration / reengineering
• Usage of prior migration experience and modern learning in migration/reengineering
• ISO 9001, SAS-70, CMMi Level 5 Certified Development / Process Centers