FAQ
Every project brings its share of questions. Our Frequently Asked Questions page is here to make finding answers quick and easy. Whether you’re curious about our migration process, technologies, or the way we work with clients, this section gathers the information you need in one place. If your question isn’t listed here, we’re always just a message away and ready to help.
Business
How long will my migration project take? How much will it cost?
The time and cost for a migration project depend on several factors, including the size of your application, the number of programs and database tables, the level of complexity, and any custom features or integrations. Most projects range from a few months for smaller systems to 12–18 months for large, enterprise-level applications. Costs vary accordingly, but our Pre-Assessment process can help us get a rough estimate. of the time and cost your project will take
What is the Pre-Assessment Phase?
Our no-cost Pre-Assessment phase gives clients an initial idea of project scope and effort. By providing us with the total number of programs, total lines of code, and total database tables in your system, we can prepare a low-to-high rough order-of-magnitude estimate for the migration. This helps you understand potential timelines and costs before committing to the next phase. Feel free to reach out to us at info@coremigration.com or our Contact Us to learn more
What is the Detailed Assessment Phase?
This Detailed Assessment phase is the part of the project where we receive your source code and analyze it to provide an exact time and cost estimate. During this phase of the project, we use our established software and team of skilled modernization experts to collect and analyze every line of source code that makes up business application(s) to be assessed including dictionaries, databases, data entry / inquiry screens, menu screens, reports, batch processes, scheduled jobs, external programs, third party components batch command files.
The end result of this is a Detailed Assessment and a Statement Of Work and accompanying PowerPoint presentation that details our findings including the results of our analysis, the time and costs to modernize the business application to Java or .NET environment accessing the migrated data store.
Feel free to reach out to us at info@coremigration.com or our Contact Us to learn more.
What is the CORE Directed Migration Option?
The CORE team handles the entire migration process, from design receovery, forward engineering, unit testing and functional testing based on test cases provided by the client. This ensures a smooth and efficient transition. We manage everything, with ongoing collaboration to keep you informed. Learn More.
What is the SELF-Directed Migration Option?
For those clients who have the team and want to take the lead, we provide support through planning and training to help your team manage the migration process. We generate the raw code from the CORE engine and your take it through to Unit, Functional, System and Impolementation with support from the CORE team. Learn More.
What is a Code Drop?
A code drop at Core refers to the process of dividing a business application into functional areas, such as customer, order, inventory, or finance, and migrating these sections one at a time. This approach allows us to deliver the new system incrementally, enabling early testing, faster feedback, and smoother adoption while ensuring each area is fully functional before moving to the next.
Business Rules Extraction
What is Business Rules Extraction?
Business rules are the embodiment of your organization’s policies, practices, and operational guidelines, developed and refined over time. These rules ensure your business runs smoothly and consistently
Our Business Rules Extraction service uses the same advanced Design Recovery tools we apply in legacy migration projects, but instead of generating new application code, we produce clear documentation, spreadsheets, and UML diagrams. This gives you a detailed, organized view of the business rules embedded in your application, helping you understand how the system works today and providing a solid foundation for modernization, redevelopment, or process improvement initiatives. Read More
What is a Business Rule?
A business rule is a statement that defines or constrains how a business operates. It can describe a policy, calculation, process step, or decision that must be followed to ensure consistency and compliance. Business rules can be as simple as “a customer must have a valid email address before placing an order” or as complex as “interest is calculated daily but only applied to the account at month-end.”
In legacy systems, business rules are often buried deep within application code, making them hard to identify or update. Extracting these rules is a key step in modernization, as it allows them to be documented, validated, and applied accurately in the new system.
Data Conversion
What is Data Conversion?
What kind of data can we extract?
We can extract information from virtually any source. This includes IMAGE databases, RDB databases, Interbase, indexed file systems, C-ISAM, ISAM, flat files, sequential files, PowerHouse subfiles, Excel spreadsheets, and a wide range of relational databases such as Oracle, SQL Server, and DB2. Over the years, we’ve handled data in countless formats — from well-documented modern systems to decades-old proprietary structures.
If it stores data, chances are we’ve already migrated it. Our process ensures that your data is extracted accurately, validated for consistency, and made ready for use in your new environment.
What databases does CORE Support for my Legacy Migration Project?
Legacy Migration
What is Design Recovery?
The Design Preservation Toolkit contains all the tools that directly interact with the legacy source code. These tools perform several individual tasks that enable it to read each legacy source file, perform appropriate syntax checking, decompose the source modules into smaller fragments known as “tokens”, and prepare these tokens to be accepted by the API Loader. These tools are built on tried and tested programming language grammar files, as well as high-speed C# CORE librairies and functions designed to perform the critical task of decomposing the legacy source code into the CORE Repository.
What is Forward Engineering?
The CORE Forward Engineering (FE) toolkit is an integrated application development environment that uses the information in the CORE repository to perform an assortment of tasks, including re- documentation, application and data definition navigation, impact analysis as well as forward engineering to various target environments including Java and Microsoft .NET. The target application development environments and technologies currently generated by the tool include Java and Microsoft .NET. The target database environments include Oracle, SQL Server, DB2, MySQL (from Image, RMS, C-ISAM, Rdb, etc). Read More.
What is the CORE Repository?
The CORE Repository is an object-oriented relational database and library of Application Programming Interfaces (API) that validate incoming data and ensure the recovered application is consistently represented and stored in the form of objects, methods and business rules that make up the underlying application. Read More.
Application Development
How does CORE use Java in the migration project?
Built on years of experience, our Java solutions plays a central role in both our legacy modernization efforts and our custom application development. We’ve delivered successful Java-based solutions that span a wide range of business needs—from online data inquiry and transaction capture to high-performance ETL, complex reporting, and robust batch processing. Read More.
How does CORE use .NET in the Migration Project?
Microsoft .NET development plays a central role in both our legacy modernization efforts and greenfield application builds. Whether we’re reimagining 30-year-old systems or building fresh solutions from the ground up, .NET technologies give us the flexibility and performance to deliver stable, scalable software across a wide range of industries. Read More.
Database Layer
What is a DAO Layer and why is it important?
The DAO (Data Access Object) layer is a key part of our modernization approach. Each table in your application is assigned its own class and DAO interface, which all programs use for data access. This centralizes all Create, Read, Update, and Delete (CRUD) operations in one place, making it easier and faster to add, remove, or modify columns without having to update every program individually. Read More.
What is Oracle and what versions does CORE Support?
The first migration project undertaken by Core was to migrate an Interbase database hosted on a VAX/VMS to Oracle. Core has migrated to Legacy Data structures to Oracle for many of our clients. Oracle is used in a wide variety of applications, mostly in settings where data matters—and where losing data or experiencing downtime could be a major issue. Read More.
What is SQL Server and what Versions does CORE Support?
SQL Server is used pretty much anywhere a business needs to store structured data and access it reliably. Because SQL Server is so flexible, it is used across industries—finance, healthcare, retail, manufacturing, education, you name it. Read More.
What is DB2 and what Versions does CORE Support?
DB2 is a relational database management system (RDBMS) developed by IBM. It’s been around for decades—first released in the early 1980s and it’s used by organizations that need to store, manage, and retrieve large volumes of structured data reliably and efficiently. In simpler terms, DB2 helps businesses organize their data, customer records, sales transactions, financial logs, product inventory and make sure that data is available, secure, and consistent at all times. Read More.
Front End Development and Tools Used at CORE
What is React and how does CORE use it on Legacy Migration Projects?
The main idea behind React is component-based development. Rather than writing an entire web page as one large block of code, developers build small, reusable components (such as buttons, forms, or menus) that can be assembled into complete user interfaces. This modular approach improves development speed, code organization, and maintenance. Read More.
What is Angular and how does CORE use it on Legacy Migration Projects?
Angular is a front-end web development framework built using TypeScript, a superset of JavaScript. It was created and is maintained by Google and was first released in 2016 as a complete rewrite of the earlier AngularJS framework. Angular is often used for developing large-scale, complex applications because of its structure, scalability, and built-in features. Read More.
What is Bootstrap and how does CORE use it on Legacy Migration Projects?
Bootstrap is a front-end framework that helps developers and designers build websites and web applications quickly and consistently. It was originally created by developers at Twitter back in 2011, and it is now one of the most widely used tools for web design in the world. Read More.
What is WPF and how does CORE use it on Legacy Migration Projects?
WPF, (Windows Presentation Foundation) is a user interface framework by Microsoft to create applications based on Windows desktop. It is the constituent of the “.NET” and enables a developer to construct a user interface that is rich, interactive and modern and a combination of XAML (to give layout and design) and C# similar to provide backend logic. Read More.
Business Logic Development and Tools used at CORE
What is Dapper and how does CORE use it on Legacy Migration Projects?
Dapper is a light and high performance micro-ORM (Object Relation Mapper) in the .NET technology. Created by the folks at Stack Overflow it sought to provide an easy to use, lightweight access to data in .NET projects without the overhead of a fully featured ORM such as Entity Framework. Read More.
What is My Batis and how does CORE use it on Legacy Migration Projects?
MyBatis is a lightweight open-source Object-Relational Mapping (ORM) Java component that enables the developer to work less easily with relational databases in a more flexible manner. MyBatis itself is simply a Java-to-SQL mapping tool and is ideally suited to any applications that need to manage data persistence without the complexity or overhead of a heavyweight ORM engine like Hibernate. Read More.
What happens to the Business Logic in my application and where does it go on the Legacy Migration project?
In a legacy migration project, the business logic from your application is moved to a dedicated layer between the user interface (UI) and the DAO/database layer. This separation ensures cleaner design, easier maintenance, and better scalability. In our solution, business logic is implemented in C# for .NET projects, or in Java using frameworks such as Spring Boot or Spring Batch for Java projects. This approach preserves your application’s functionality while making it easier to enhance and maintain in the future.
What is Spring Batch and how does CORE use it on Legacy Migration Projects?
Spring Batch is a Java-based framework designed to help developers build and run batch processing jobs especially when those jobs need to handle large volumes of data in a reliable and repeatable way. Spring Batch part of the larger Spring ecosystem which means it fits nicely alongside other Spring tools like Spring Boot, Spring Data, and Spring Security. Read More.
What is Spring Boot and how does CORE use it on Legacy Migration Projects?
Spring Boot is a Java-based framework used to build web applications, APIs, and microservices—quickly and with minimal setup. Spring Boot built on top of the Spring Framework, which has been around for years and is known for being powerful, but sometimes complicated. Spring Boot came along to solve a simple problem: make Spring easier to use. Read More.
What is Red Hat SSO and how does CORE use it on Legacy Migration Projects?
Red Hat Single Sign-On (SSO) is an identity and access management solution that enables easier and more practical application logins by the user. It enables the users to provide a single sign-in, and then access numerous services without having to re-authenticate themselves. Read More.
What is C# and how does CORE use it on Legacy Migration Projects?
Chances are that if you have wandered even a little in the world of programming, you have heard of C# (read C-sharp). As the product of Microsoft in the beginning of the 2000s, C# was created to be modern, easy-to-use, and potent. It is the Microsoft response to Java, bringing together the form and performance of the ancient programming languages such as C++ and clarity and sheer simplicity required of the current software production. Read More.
Quality Assurance
What Quality Assurance does CORE perform on Legacy Migration projects?
At Core, Quality Assurance (QA) isn’t an afterthought, it’s part of how we build. Over the years, we have handled some of the most complex application migrations in North America, and along the way, our approach to QA has evolved into something we are proud to offer on its own. The same deep, hands-on testing methodologies that safeguards our modernization projects powers standalone service to companies that need expert oversight and reliable outcomes. Read More.
What is End-to-End Testing and Automation and how does CORE use it on Legacy Migration Projects?
End-to-End (E2E) testing is a way of software testing which tests that an entire app flow operates correctly in a beginning-to-end manner. It replicates actual user actions to ensure that each component of the system interacts in a right manner. This should take into account the frontend, the backend, and databases, APIs and any third-party facilities and services. Read More.
What is Test Script Development and how does CORE use it on Legacy Migration Projects?
Test script development entails development of detailed instructions that will give a testing software or a tester clear guidelines on how to verify the operation of a section of an application works properly. These scripts determine the inputs, the anticipated results and the process required to execute the test. Read More.
What is A/B Testing and how does CORE use it on Legacy Migration Projects?
A/B testing is a way to compare two versions of something to see which one works better. For example, you might test two different headlines on a webpage to see which one gets more clicks or leads. You show Version A (the current one) to half of your audience and Version B (the new version) to the other half. Then, you measure which one performs better based on your goal like sign-ups, sales, or time spent on the page. Read More.
What is DevOps and how does CORE use it on Legacy Migration Projects?
Microsoft DevOps is a combination of two elements; namely Development and Operations. It is not a particular tool or language but an approach therefore and a culture structured to have software development and IT operation teams converge. DevOps is aimed at faster and more reliable construction, testing, releasing, and improving of software. Read More.
What is Playwright and how does CORE use it on Legacy Migration Projects?
Playwright is a modern tool that helps developers and testers automate web browsers. Playwright was created by Microsoft and released in 2020 and while that is relatively recent, it has quickly become a favorite among teams working on websites and web applications. Read More.
What is JUnit and how does CORE use it on Legacy Migration Projects?
JUnit is a Java unit testing framework which supports developers to write and execute the unit tests. A unit test is a small program that determines whether a given part of program is functioning as intended. JUnit is used to write these tests, make them organized and automatically verify the outcomes during development. Read More.
What is NUnit and how does CORE use it on Legacy Migration Projects?
NUnit is a unit test framework that supports the .NET applications. It enables programmers to create and execute tests to check that their code is executing properly. NUnit is one of the most popular testing frameworks within the .NET community and it is instrumental in ensuring that code quality is high, and bugs are found early, and allows test-driven development. Read More.
What is Git and how does CORE use it on Legacy Migration Projects?
Git is a distributed revision control system that was designed to trace amendments to source code as well as coordinate collective work. It enables programmers to store versions of their code, test without pain and align with colleagues easily. Developed by Linus Torvalds in 2005, Git has come to be the industry de facto version control system in software development. It is popular with sites such as GitHub, GitLab, and Bitbucket, and it allows working both individually and in groups. Read More.
What are CI/CD Pilelines and how does CORE use it on Legacy Migration Projects?
Continuous Integration pipeline (CI pipeline) is simply a set of tasks that is automated to run every time someone commits a new piece of code to a shared repo. To ascertain the integration of the code into the current project, the pipeline checks, builds, tests and validates the code automatically. Continuous Delivery pipeline (CD) , is a sequence of programmed processes, which carry software in an accomplishment and environment-checked produce build to a staging or production environment. It is the successor of Continuous Integration (CI) and it prioritizes issuing new features or updates as quickly, reliably and safely as possible. Read More.
What is Azure SQL Database and how does CORE use it on Legacy Migration Projects?
Azure SQL Database is a fully managed relational database service, built on SQL Server, in the cloud. It allows the usage of scalable, secure and high performance database capabilities with no requirement to manage physical equipment or manage software installation. You can treat it as one of the usual SQL Server databases, but without any less of the cloud advantages. Read More.
What is Docker and how does CORE use it on Legacy Migration Projects?
Docker is a platform through which software applications are built, packaged and executed in containers. A container is a lightweight standalone package that contains all necessities to execute a segment of software, namely the code, the runtime, the libraries and system tools, to ensure that software functions in any environment in the same manner. Read More.
Project Management
What is the Agile Methodology and how does CORE Use it on Legacy Migration Projects?
Agile is an adaptive and user cooperative software development approach. It aims at providing customer value by releasing value in very small increments at frequent frequencies instead of infrequent large releases. Agile is iteration, feedback and continuous improvement. Read More.
What is the Scrum and how does CORE Use it on Legacy Migration Projects?
Scrum enables the teams to divide large work into small manageable chunks and report progress on a regular basis. It focuses on openness, auditing and transformation. Read More.
What is the Waterfall Methodology and how does CORE Use it on Legacy Migration Projects?
The Waterfall methodology is an old-fashioned linear software development system. A project, in this model, is divided into different phases that once they are accomplished, we follow the next phase in a definite order. One stage has to be completed completely before another stage commences. Read More.
What is SDLC the and how does CORE Use it on Legacy Migration Projects?
SDLC, or System Development Life Cycle, is a structured process for delivering high-quality software through defined stages such as analysis, design, build, testing, and deployment. At Core, we use a hybrid SDLC approach for legacy migration projects, applying its proven structure while hyper-accelerating the analysis, design, and build phases using our automation tools. This allows us to preserve the rigor and quality of SDLC while dramatically reducing the time it takes to migrate and modernize your application. Read More.
