Welcome to Konigi, where legacy migrations are our specialty.

Over the past two decades, we have provided services to businesses, in diverse industries, including the resource for migration from legacy COBOL, FORTRAN and RPG II environments to Microsoft's architectures.

Over the past eight years we have been developing tools and processes to support this initiative and as a result, we have developed an environment which generates Microsoft VB.NET code from ANSI COBOL code. This automated environment allows developers to upload COBOL source code with relevant Copybooks and generate VB code. The processes preserves COBOL logic and functionality, enabling the inclusion of the code into a VB.Net project.

This environment will be continuously undergoing enhancements to comply with ANSI COBOL coding standards and is subject to "Unimplemented" notices for COBOL statements and functions which have not been implemented.

To support your efforts, this environment will enable the client to re-convert any previously converted COBOL code with no additional costs, enabling them to take advange of conversion enhancements as they are implemented.

As new changes and functions are developed, clients will be notified, via email, of the new enhancements, the impact and benefits of the new functionality, and an invitation to re-convert any prior converted COBOL code.

We invite you to view your COBOL code, converted to VB.NET, by signing up, uploading your COBOL code with copybooks. The format is a GIF image and is protected to prevent downloading or copying.
The primary breakdown for Lecagy Application Migration is in three parts, Data, Screens and Logic.

Data constitutes the most critical part of a migration and in most respects, it the simplest part. Using middleware products, businesses can migrate extensive amounts of Legacy data directly to anyone of a number of formats or database. The majority of middleware products have functionality to interact directly with Oracle, SQL Server, MySql, Pervasive SQL and others.

Two considerations for data migration should be examined, (1) to convert, as-is or (2) to enhance as part of the conversion process.
Our strategy is to provide cost effective and efficient tools, applications and methodologies to assist developers and businesses migrate their Legacy environment to .NET and other open architectures.

Our experiences over the past several decades give us an edge, unmatched in this industry. While many claim to be experts at code and data migrations, only a few have actually mastered this process.

Seach the Internet for "COBOL CONVERSION" and ".NET". You will find hundreds of consultants, but not one service that will convert your COBOL code, online, at a fixed price!
Our real-time, COBOL to Visual Basic (.NET) On-Line, conversion application, simplifies the migration of your ANSI COBOL to Microsoft's .NET architecture while retaining the logic and definitions of your environment while preserving your business investments.

This environment enables developers to rapidly migrate COBOL code and  Copybooks (Library's) directly to Microsoft VB.Net, eliminating conversion mistakes including formatting, typographical and syntactical errors, common with manually converted applications.

Interested in migrating your COBOL code to .NET? We have applications to build SQL Server databases directly from your RMS, DB2, ISAM, VSAM and other database and file formats. Our data conversion applications autogenerate stored procedures within SQL Server and simultaneously build VB modules with corresponding procedure calls, using datasets and datatables. Need to move hundreds of screens quickly and efficiently to ASPX.NET? We have products to satisfy  all your migration needs and more.

Contact us at Sales@Konigi.us, where your legacy conversion begins.
Legacy application migrations has recently become the forefront of business IT activity and is an option previously not available to most organizations. Yet, the high cost of Web-Based environments such as SAP, BAAN, PeopleSoft and Oracle have detered many corporate executive to re-assess their existing Legacy environment, resulting in various decisions including:
  • It works, don't change it
  • It is too expensive to migrate
  • No one has a product which meets our needs
  • Our business IT needs are too complex
  • Our IT environment was custom built for us
  • Cost of ownership for new systems is too expensive
  • We need to modify IT our environment, this is not an option
  • The new system must be flexible and customizable
  • Our data schema is critical

Where to turn!

The answer my be easier to consider than you think.

A few important decisions for business executives when considering a new software environment for their organization are:

  • Purchase cost
  • Cost of ownership (ongoing)
  • Technology costs
  • Flexibility
  • Data re-mapping

The most cost effective, efficient and self-supporting solution is to migrate to an Open Architecture, where:

  • Purchase (conversion) costs are low
  • Cost of ownership is low
  • Technology costs are manageableFlexibility is high
  • Flexibility is high
  • Data is transparent (no remapping, no restructuring)

Consider this!

If you have a legacy COBOL environment and have access to the Source Code and are looking for a solution which:

  • Protects your business investment
  • Retains your IT application logic
  • Is recognizable to your users (no retraining)
  • Is similar in format
  • Is easily maintainable
  • Is cost effective
  • Preserves your data schema

Migration
is the "best solution"!

A scenario:

A business has a COBOL environment with 200 data files or tables, each with 40 fields. Their application has 250 programs with a total of 2 million lines of "code logic" and there are 300 screens.

If your business has over 100 users, your initial investment for a new environmnet will cost between $300,000 and $500,000, and if your business is larger (250+ users), expect costs in excess of $1M.

Equipment will not be considered, as the business will need to invest in new servers, storage arrays and relevant technologies no matter which path you choose.

Add in costs for:
  • Data Conversions
  • Training (IT staff and users)
  • Data re-mapping
  • Consultants
  • Business process re-engineering
  • Integrating external feeds (EDI, CRM, etc)

Estimate 25% to 35% above the software cost, for training, conversions, data re-mapping, integrating external feeds and consultants (this can be very, very expensive)

Consider The Alternative:

Conversion of your COBOL applications to VB.NET, <$100,000 usd

Migrating your data from:

  • DEC (RMS, RDB, DBMS) <$20,000 usd
  • IBM (DB2, VSAM, ISAM) <$20,000 usd
  • UNIX <($20,000)

Conversion of Screens:

This is dependent on the proficiency of your developers. We have converted screens with 30 fields, in under 20 minutes. Estimate 6 months for three programmers, budgeted cost of $150,000. Cost of the Screen Builder, $5,000. The screen builder works with your COBOL source code, your copybooks and the target database, after migration. This environment automatically builds VB.Net (ASPX) code, reducing coding and development resources.

An estimate for conversion would be between $250,000 and $450,000.

The true cost savings are realized with the:

  • Cost of ownership
  • Support costs (marginal)
  • Training Costs (marginal)
  • Consultants (minimal)
  • Data re-mapping (none!)
  • Standardized Code Structures

With this scenario, the business owns all the source code, it pays no external support costs, has complete flexibility with enhancements, can support data warehousing and integration with external systems.

Savings realized:

Priceless!