Magic software upgrade Frequently Asked Questions

General

We do not need the code of your Magic Software application. we just need the Application details (i.e. size, programs, tables, etc.) and the conversion type required. You can use the contact form on this website as well.

No. When your Magic software application is submitted to us for conversion, a recommended best practice is to reduce development as much as possible, until the conversion is completed and accepted. However, if any changes are required after conversion begins, they will be incorporated as a Delta conversion at the end of the process. Another method we support is fixing all the problems in the automatic tools and re-covert again without code freeze at all.

In our experience, we’ve found that on average 30% of the programs in a Magic Software application are unused. We factor this into our pricing, and in any case, inactive programs will be converted, but not tested.

Yes. If there are several Magic Software applications that need to be converted, you can combine them altogether into one project. Also, if you need more than one type of conversion (i.e. Database+Version) we can incorporate everything into the same project and save duplication of efforts during the testing phase.

We have a lengthy track record of success (over 20 years & 5,800 successful Magic Software conversions for hundreds of satisfied clients) and we’re confident your conversion project will be successful as well. In fact, we’re so confident of your success that we won’t charge you until the end of the conversion, and we provide a warranty following your project’s completion (See next FAQ).

Magic Upgrade

Yes. We do not need your Magic Software application’s data in order to perform the conversion. However, data will be helpful during the testing phase, but this phase can be conducted entirely on-premise at your site.

The GUI of the converted application will be similar to the old application. However, during the conversion process, we will implement a particular design for the tables and screens. There is also an option to combine face-lifting with the design component model during the conversion process.

Yes. We upgrade your Magic application / uniPaaS application to a fully event-oriented application in Xpa. No RM-Compatible handler will be left in your application, nor will one be required. Our proprietary automated tools ensure that the result Xpa code of decomposition will be correct and bug-free.

In our extensive experience, we’ve discovered that there are numerous problems which the free tools cannot deal with. That’s one of the reasons we developed our tools. To ensure that an application converted to Magic Xpa would not only convert properly, but would also be able to take full advantage of the new capabilities Xpa offers.