Account Migration Executor

Moving an open book from one account to another by hand - closing each position on the old account, then re-opening its equivalent on the new one - is exactly the kind of one-time, high-stakes task where a slip (closing the wrong ticket, mistyping a lot size, forgetting a position) is expensive and easy to make under time pressure. This EA runs on both terminals involved. On the SOURCE account (InpRole = SOURCE), it never closes a position just because it is open and matches a magic filter - every single ticket must be explicitly listed by number in InpConfirmedTickets, and even then nothing happens unless InpArmMigration is also set to TRUE. Left unarmed, it only prints a dry-run list of eligible ticket numbers so the trader can review and copy them into the confirmed list deliberately. For each ticket actually confirmed and armed, it closes the position, then writes a row to a shared manifest recording the symbol, direction, lots, and each stop's distance in POINTS (not a raw price, which means nothing on a different account) - and immediately appends a plain-language rollback note explaining that the original fill can no longer be replicated and what to manually re-open if the migration needs undoing. On the TARGET account (InpRole = TARGET), it reads that manifest and, for every row still pending, opens the equivalent position sized to THIS account's own live lot step/min/max (never the source account's lot size verbatim) with stops re-derived from the recorded point distance against this account's own current price. If the target-side open fails, the manifest is marked FAILED and a rollback note records plainly that the position now exists on NEITHER account and needs manual attention - the migration is never silently retried or auto-reversed. Notes and limitations - This is NOT atomic. Between a SOURCE close succeeding and the TARGET open completing, the position genuinely exists on neither account. This gap is inherent to migrating between two separate trade servers - there is no way to close and open in a single transaction across them - and it is exactly why every step is logged with a rollback note rather than assumed to always succeed. - "Rollback" is honest, not literal: a closed source position cannot be reopened at its original price and time. The rollback notes describe what to manually re-enter as a NEW trade, not a true undo. - Stops are migrated as a POINT distance from the source's own open price, re-applied against the target's own current price at open time - the resulting stop level is equivalent in distance, not in absolute price, and is still subject to the target broker's own stop-level/ freeze-level constraints. - Tracks at most 200 manifest rows in memory per run per side (a documented fixed-array cap, MAX_TRACKED_TICKETS in the source); migrate in batches within that limit. - On MQL5 netting accounts, TARGET refuses to open into a symbol that already carries a foreign-magic position rather than risk merging into it - see MQL4 VERSUS MQL5 DIFFERENCES. Clear or reassign that position first if this happens. - Assumes the source and target accounts trade the same symbol NAME. If the two brokers use different symbol naming, resolve that separately (see the Auto Learning Symbol Mapper project elsewhere in this catalogue) before running a migration - this EA does not remap symbol names itself. - Reimplements its own lot normalisation and shared-file append pattern inline rather than including another project's file, per this catalogue's no-cross-project-include rule.

Expert advisor · MT4 · v1.0 · Free

Tags: Risk & Lot Size · MT4 Expert Advisor · MQL4 Source Code

Expert advisors (EA) for MT4 & MT5 · PolyMaria