INSIDE 2.5 Support End: Preparing a Software Migration

Updated October 14, 2026. On January 21, 2021, New Hope announced that support for INSIDE 2.5 and earlier versions would end on February 1, 2021. The recommended replacement at that time was INSIDE 3.0. This is a product lifecycle archive, not an instruction to install version 3.0 today.

What the 2021 notice covered

The announcement listed changes to the program core, fast and slow quote charts, Diff displays, open trades and history. It also stated that the updated New Hope FEED (Bank Stock) program required INSIDE 3.0 or later. That statement concerned the release described; it does not establish compatibility between any old feed and a current product.

The third-generation INSIDE announcement provides related historical context. An end-of-support date does not necessarily mean that an executable stops opening on that day. Equally, an old program starting successfully does not establish that its connections, licensing or settings remain supported.

Map the installed system before changing it

• Record the exact names and versions of the robot, feed and trading platform.

• Identify the broker server, account type and full instrument names.

• Record the operating system, server location and connection method.

• Preserve settings, logs and identifiers for outstanding orders.

• Identify the component that needs replacement and the dependencies that must change with it.

Replacing the robot alone, for example, does not resolve an incompatible data source. Updating a terminal without checking its connecting component can also leave a system only partly operational: prices appear, but order acknowledgements do not arrive. Check the complete route for both data and trading instructions.

Prepare a reversible change

Separate file preservation from trading-state checks. A settings backup is useful, but restoring it cannot rewind transactions on an account. Before migration, decide how each open position will be monitored and who controls the resumption of automated actions. Do not run two robot instances on one account without a documented operating arrangement.

For MetaTrader 5, the official folder documentation distinguishes installation files from user data. Copying a single executable therefore does not preserve the entire environment. For other applications, check their own instructions for settings and data locations.

Define acceptance checks for the replacement

1. Confirm the connection and receipt of fresh quotes.

2. Compare parameter units, symbols and volume limits.

3. Test order submission, response, cancellation and history in a test environment.

4. Check state recovery after a permitted restart.

5. Keep a results log and a list of unresolved questions.

The demo/live validation protocol explains how to compare environments. For present-day NH PRO, start with the setup preparation guide and use the New Hope enquiry form to confirm a suitable version and migration terms. The historical notice does not define a current upgrade price or licence duration.