Portfolio

Legacy indicator port to MT5

Buffers rewritten for the MT5 model, the original formula kept exact, colour rendering rebuilt and alerts moved to the new notification system.

MT4 / MT5 Existing EA owner Mohammadreza Fathi Owner of a proprietary indicator

Project specifications

Project specifications

Market
GBPUSD
TF
M15
Platform
MT4 / MT5
Client type
Existing EA owner
Delivery window
6 weeks
Stack
MQL4 and MQL5, M15 data, a comparison report
Strategy
Buffer and render rewrite for MT5
Modules
Coloured buffers + alerts
Testing
Numeric output compared across builds

Who this was for

Mohammadreza Fathi

Role
Owner of a proprietary indicator
City
Shiraz
Project reference
TBT-1407-24
Trade flow

The client's idea

Mohammadreza Fathi works GBPUSD on M15; the opening brief was: An indicator I wrote ten years ago must draw and calculate the same on MT5.

Initial challenge

The MT4 build leaned on limited buffers and legacy functions; a naive port would break colours and alerts.

Solution

Buffers rewritten for the MT5 model, the original formula kept exact, colour rendering rebuilt and alerts moved to the new notification system.

Why this design

The original formula was preserved line by line so the client's numbers do not shift. It matches how GBPUSD is actually traded and can be tested against the data already available.

Safeguards and risk control

The old build is not removed from the live account until the MT5 results match it.

Our next-step proposal

The next step is reviewing behaviour under missing data and server reconnects.

Portfolio

Measured results

These are the figures the test produced — not a promise about future performance.

  • 100 % Parity with the previous build
  • 5 Defects fixed
  • 0 Regressions caught
  • 4,800 Bars in the test set

Portfolio

How the delivery ran

Every project moves through these five phases, with the window for each agreed in the specification.

  1. Discovery and problem framing

    Completed

    Listing this project's MT4/MT5 differences: orders, positions and account accounting.

    Day 1–3

  2. Written specification

    Completed

    A migration map per file and an equivalent behaviour for concepts MT5 does not have.

    Day 4–9

  3. Implementation

    Completed

    Rewriting the order layer and mapping the magic numbers without touching the strategy.

    Day 10–23

  4. Testing and validation

    Completed

    Running the same data on both builds and comparing trade by trade.

    Day 24–33

  5. Handover and support

    Completed

    Handover of the MT5 build with a difference report and the MT4 build kept intact.

    Day 34–37