A funded account change requires checking the whole automation route: broker connection, destination account, subscription assignment, running TradingView message, and copier selections. A successful login only confirms one part of that route. Before the next signal, verify where an order will go and how any existing position will be managed.
Table of Contents
- Key takeaways
- What can change when you receive a funded or replacement account?
- Which type of funded account change are you making?
- Step 1: record the old route and protect existing trades
- Step 2: verify the new broker account and environment
- Step 3: check the subscription after a funded account change
- Step 4: regenerate saved alerts with the new destination
- Step 5: update the running TradingView alert too
- Step 6: inspect copier masters, followers and allocation
- Step 7: prove where the next instruction goes
- Worked example: replace one follower under the same login
- What should you do if verification fails?
- Troubleshooting a funded account change
- Frequently asked questions
- Finish the account change with a verified route
Passing an evaluation, receiving a reset, or replacing an unavailable account can leave familiar settings pointing at an obsolete destination. The broker username might stay the same while the account ID changes. Your chart can look unchanged even though the next alert still carries yesterday’s account details.
This guide follows the PickMyTrade.io automation platform and its documented Saved Alerts and subscription workflows. Tradovate users on PickMyTrade.trade should use their own application’s account and billing instructions. The checklist is documentation-based; the examples below are hypothetical and do not describe a tested migration or a particular prop firm’s rules.
Key takeaways
- Identify the new account, broker connection, and environment separately.
- Check existing positions and orders before pausing or removing routes.
- Update saved configurations and the actual running TradingView alerts.
- Verify the .io subscription’s connection assignment and each copier destination.
- Resume only after the intended account, size, and protection are confirmed.
What can change when you receive a funded or replacement account?
An account replacement can change the destination without changing your broker login. It can also involve a different broker, server, environment, or credentials. Record exactly what the firm issued before editing your setup. Treat account labels as convenient descriptions and compare the actual identifiers used for execution.
| Part of the route | What to compare | Why it matters |
|---|---|---|
| PickMyTrade application | The .io or .trade registration where you configured automation | The account and plan must be checked in the relevant application |
| Broker connection | Broker, login, server and environment where applicable | The same broker name can appear on multiple connections |
| Trading account | Old and new account IDs or names used by the connector | A connection may expose more than one destination |
| Subscription | Paid plan and assigned connection in the documented .io flow | Payment and correct assignment are separate checks |
| TradingView alerts | Webhook URL, message, condition and status | An older active message can still use the previous destination |
| Copier routes | Master, followers, allocation and enabled state | A direct alert update does not establish copier correctness |
Ask the firm whether its funded stage permits your automation and copying arrangement. A permission that applied to an evaluation does not establish the rules for every later account. Check the current agreement for the specific account type, including trade allocation, maximum size, and any restrictions on copying between accounts.
Which type of funded account change are you making?
Identify what changed before rebuilding the setup. A replacement account under the same login can need a different account selection without needing a new connection. A new broker or environment needs a broader review. Use this decision table to choose the work, then complete the verification steps below.
| Situation | Main changes to review | What to confirm separately |
|---|---|---|
| New account, same broker login and environment | Destination selections in generated messages, running alerts and followers | New account visibility, limits and current plan assignment; do not assume reconnecting is required |
| New login or connection | Broker authorization, connection selection, generated configuration and subscription mapping | Old connection’s positions and orders before disconnection |
| Different broker or environment | Connector-specific setup, endpoint, field definitions, instrument mapping and sizing | A payload that worked on the previous broker may require regeneration |
| Replaced copier master | Master selection and the source of copied events | Existing follower exposure and whether another job still copies the old master |
| Replaced copier follower | Follower selection, allocation and risk settings | Old follower is excluded from the intended new job; new follower result is verified |
Step 1: record the old route and protect existing trades
Start with an inventory of everything that can submit an instruction to the old or new account. Include direct TradingView alerts, scripts that create messages, saved templates, copier jobs, and scheduled automation. Record the old account’s open positions and working orders before changing connections or disabling an alert.
- Write down the old and new account references and the broker connection for each.
- List all active entry and exit alerts, including separate buy, sell, close and partial-exit messages.
- Inspect existing positions, pending entries, stops and targets at the broker.
- Decide how existing exposure will be managed throughout the change.
- Stop unintended new entries while preserving a deliberate exit plan.
Pausing the wrong component can stop more than entries. PickMyTrade’s pause guide says incoming alerts remain visible while processing and execution are paused. Do not rely on alert-driven exits continuing through that pause. Separately confirm any broker-held protection already working for an open position.
Stopping alerts, disconnecting a connection, and closing a position are different actions. Confirm the resulting broker state instead of assuming one performs the others. If an entry has already been submitted or is in flight, changing a template will not prove that order was cancelled. Inspect both accounts during the handover.
Confirm pause scope before using it. In the documented .io interface, Pause Account is under Alerts. The guide does not establish a universal scope across every connection or independent copier, or whether events received while paused are discarded or replayed after resuming. Confirm those details for your workflow. Do not resume on an assumption about queued signals.
Step 2: verify the new broker account and environment
Check that the intended replacement account is visible and usable in the broker environment connected to PickMyTrade. A “funded” label does not by itself identify a Live server; firms can use different environments for different programs. Follow the firm’s actual connection instructions and the relevant broker setup guide.
If the login is unchanged, determine whether only the destination account selection needs updating. If credentials, broker, server, or environment changed, follow the selected connector’s setup guide. Record the old connection reference before replacing it so order-history checks remain possible.
For a hypothetical move from ACCOUNT-OLD to ACCOUNT-NEW under the same broker login, a password change does not fix an alert that explicitly names ACCOUNT-OLD. Compare the exact account selected in Generate Alert with the broker’s account list. Also confirm the new account is enabled for the intended instrument and order type.
Step 3: check the subscription after a funded account change
In the documented .io workflow, a paid plan must be assigned to a broker connection. The subscription management guide describes viewing assignments, moving subscriptions between connections, and reassigning a plan after disconnection. Changing an account is therefore a reason to inspect the existing assignment before buying another plan.
- Open Dashboard → Payments and inspect the Active subscriptions tab for the plan and expiry.
- In Brokers, identify the connection currently assigned to the plan.
- If a different connection is required, use the documented plan-assignment or subscription-move control in Brokers; confirm the target before applying it.
- Confirm the resulting connection and validity before enabling execution.
A new trading account under an existing connection is not necessarily the same billing event as creating a new connection. Check the arrangement shown in your dashboard. The .io documentation does not establish automatic transfers between separate .io and .trade registrations, or guarantee that every replacement account qualifies for the same subscription treatment.
If the paid plan appears on one connection while the intended destination shows inactive, investigate the mapping with support. Share the registration email, relevant connection names, and receipt reference privately. Do not send full payment-card details or assume a second payment is needed just because the replacement account is new.
Step 4: regenerate saved alerts with the new destination
Update the saved configuration before copying a replacement message into TradingView. PickMyTrade’s Saved Alerts guide documents editing account IDs, symbols and risk settings, then regenerating the alert. Choose Update Alert to replace the template or Save As New to keep a separately named version.
Check the entire generated configuration, not only the first account field you recognize. Additional destinations may appear in a multi-account section, while the strategy may construct part of the outgoing message itself. Preserve the connector’s supported field names and format. A global search-and-replace is not a substitute for regenerating the correct route.
| Setting | Funded-account-change check |
|---|---|
| Primary destination | The new account is selected in the generated setup |
| Additional accounts | Obsolete destinations are removed from the intended new route |
| Authentication and webhook | Both belong to the correct application and supported connection |
| Symbol and instrument | Mapping matches the instrument the new account is allowed to trade |
| Quantity or percentage sizing | Recalculated for the new account’s limits and sizing basis |
| Exits and protection | Stops, targets, partial exits and close messages use the intended destination |
| Repeats and reversals | Existing behavior is understood before enabling the revised route |
Use a private version label such as “MNQ indicator — replacement route — October 22” to identify the migration. Keep historical templates clearly marked so they are not accidentally reused. A label helps organization; the account fields in the generated configuration remain the execution evidence.
Step 5: update the running TradingView alert too
A saved template and a running TradingView alert are separate copies of configuration. The Saved Alerts documentation explicitly says template edits do not affect active TradingView alerts until you apply the changes there. Open every affected alert and inspect its actual message, webhook destination, condition and enabled state.
Update the account routing in every applicable entry and exit alert. An indicator system may use separate buy, sell and close alerts. A strategy may send one stream of order events or use messages embedded in Pine. Follow the supported setup for your workflow and identify the source of the final emitted message.
If Pine code, strategy inputs, chart symbol or timeframe must change for the new route, recreate the strategy alert from the updated chart setup. TradingView explains that strategy alerts run a saved server copy independently of subsequent chart changes. Updating a message alone does not refresh that saved strategy logic.
Retire obsolete alerts deliberately. Running old and new versions together can produce duplicate instructions or send orders to two destinations. Before starting a replacement alert, check how any old position’s exits will be handled. An exit intended for ACCOUNT-OLD should not be redirected to ACCOUNT-NEW without a separate plan for managing that position.
Step 6: inspect copier masters, followers and allocation
Review copier configuration independently from direct alert configuration. Determine whether the replaced account was a master, follower, or both in different jobs. Check each selected destination and remove obsolete selections from the intended active setup. Do not assume that a newly visible account automatically replaces the old one everywhere.
Recalculate destination size after changing accounts. A multiplier that was acceptable for an evaluation may produce an unsuitable position on the replacement account. Check symbol mappings, accepted quantity increments, risk settings and account limits. Treat each destination as its own verification task rather than judging the group by the master’s status.
For ProjectX users, follow the ProjectX copier guide. Other connectors need their own copier instructions. Also look for overlap: if a direct TradingView alert and a copier can reach the same destination, establish which route should own the trade before resuming either one.
Step 7: prove where the next instruction goes
Verify the route in stages: alert event, PickMyTrade receipt, broker order, fill or rejection, and resulting position. A received message is insufficient proof of execution. Start in an appropriate demo environment where available; any later live check must fit the account’s permissions, limits and intended risk.
| Stage | Evidence to record | What it establishes |
|---|---|---|
| TradingView event | Alert name, trigger time and outgoing message | The intended source fired |
| PickMyTrade receipt | Connection, action, symbol, status and order references | The request reached the selected connection |
| Broker order | Destination account, instrument, side, quantity and order state | The broker received the expected instruction |
| Position and protection | Actual fills, remaining size and working stops/targets | The resulting exposure matches the plan |
| Old account | Order and position history around the test time | No unintended new activity appeared on the retired route |
| Followers | The same checks for each intended destination | Copying behaved as intended for each account |
The Alerts monitoring guide lists timestamps, connection names, statuses, and entry, limit and stop IDs for investigation. Match those records to the broker account. “Successfully placed” and “filled” are different milestones; pending orders still need their state and protection checked.
Test the supported exit as well as entry, inspect partial fills, and confirm the final position. For a multi-account route, record intended and actual quantity for each destination. Keep credentials removed from any shared evidence. Resume the complete workflow only after unexplained account, instrument or quantity mismatches are resolved.
Worked example: replace one follower under the same login
Suppose ACCOUNT-OLD and ACCOUNT-NEW belong to the same broker login and environment. ACCOUNT-OLD is a copier follower, and a separate indicator alert also sends it trades. The intended new arrangement uses only the copier. This fictional example shows what to compare; it is not evidence of a successful product test.
| Component | Before | Intended after |
|---|---|---|
| Broker connection | Existing authorized connection | Same connection, if ACCOUNT-NEW is available and authorized |
| Follower destination | ACCOUNT-OLD | ACCOUNT-NEW |
| Direct indicator alert | Sends entries and exits to ACCOUNT-OLD | Retired after resolving old exposure; no replacement direct route |
| Saved indicator template | Contains ACCOUNT-OLD | Marked retired or retained only as a clearly labeled historical record |
| Running TradingView alert | Old direct alert still enabled | Disabled after old trades and pending entries are handled |
| Subscription | Plan assigned to existing connection | Assignment and validity checked; no assumed new-plan requirement |
| Allocation | Old follower quantity settings | New follower quantity calculated against its own limits |
First inspect ACCOUNT-OLD and decide how any open position will exit. Then stop its unintended new-entry sources, update the follower selection, and check allocation. Because the direct indicator route is being retired, generating another direct alert for ACCOUNT-NEW would defeat the intended design and could create overlapping orders.
For the controlled verification, record the expected destination and size before the event. Compare the copier record with the broker order, fill and protection in ACCOUNT-NEW. Inspect ACCOUNT-OLD for unintended new activity over the same period. This verifies the specific observed event; it does not guarantee later events cannot fail.
What should you do if verification fails?
Stop unintended new entries, inspect both accounts, and locate the first mismatch before retrying. A failed new-account test does not make the old account a valid fallback. Its status, permissions, or account identity may be the reason for the migration. Keep any required exits and protection under deliberate control.
| Recovery step | Action |
|---|---|
| Contain new activity | Stop the identified entry sources and copier jobs; confirm the effect instead of relying on one pause control |
| Inspect exposure | Check both accounts for positions, pending entries, partial fills and working protection |
| Locate the mismatch | Compare source message, connection, account, broker response and resulting position |
| Correct one cause | Fix the destination, permissions, subscription assignment or allocation shown by the evidence |
| Verify again | Use a fresh controlled event; do not blindly resend an old buy or sell instruction |
| Resume deliberately | Enable only the intended route after confirming its outcome and any paused-event behavior |
Troubleshooting a funded account change
| Symptom | First checks |
|---|---|
| Broker connected, new account missing | Login, server/environment, account entitlement and broker account list |
| New connection shows no active plan | Existing subscription assignment and expiry in the .io dashboard |
| Alert still references old account | Actual TradingView message, Pine message source and additional-account entries |
| Master works, follower does not | Follower selection, connection, allocation, permissions and rejection record |
| Unexpected duplicate order | Old running alert, repeated event or overlapping direct/copier route |
| Account already linked elsewhere | Existing registration or binding; ask support to investigate ownership and eligibility |
If the issue concerns an existing binding, subscription transfer, or duplicate registration, use the official PickMyTrade support page. Ask for help with the existing account association. Repeated registrations do not resolve ownership checks or establish eligibility for a new trial.
| Support evidence | What to provide privately |
|---|---|
| Application and broker | Whether you use .io or .trade, plus broker and environment |
| Change summary | Same-login replacement, new connection, master change or follower change |
| Account references | Old and new account identifiers; redact public copies |
| Time | Event timestamp with timezone |
| Configuration | Redacted outgoing message and relevant copier selections |
| Outcome | Expected destination and quantity versus actual result |
| Execution references | Alert status, broker response and order IDs where available |
Remove tokens, API keys and passwords before sharing configuration. Include the connection names and a receipt reference if billing assignment is involved. This gives support enough context to trace the route without asking them to infer the migration from a connection-status screenshot alone.
Frequently asked questions
Do not assume so. Broker connectivity and alert routing are different parts of the setup. Inspect the actual running TradingView message and every additional destination after reconnecting. If the account identifier changed, regenerate the supported configuration and apply it to all affected entry and exit alerts.
Check the existing plan and connection assignment first. PickMyTrade.io documents moving subscriptions between connections and reassigning a subscription after a connection is disconnected. Whether your specific change requires another plan depends on the arrangement in your account. That documentation does not establish automatic transfers between separate .io and .trade registrations.
Only if the rest of the route remains valid and the supported configuration requires no other changes. Review broker connection, environment, authentication, symbol mapping, sizing, exits and followers. A replacement under the same login can still have different trading limits. Verify the final generated message and broker outcome.
Recreate it when changes to the strategy or its chart setup must be reflected in the running alert. TradingView strategy alerts use an independent saved copy. A routing-message edit and a refresh of saved strategy logic are different tasks; identify where your workflow stores the account details before making the change.
Treat pause as an execution control, not proof that a position is closed. The documented PickMyTrade.io pause stops processing incoming alerts while they remain visible. Inspect positions and working orders directly at the broker, and establish how exits will be managed before pausing a route that an open position relies on.
Finish the account change with a verified route
A funded account change is complete when the intended account receives the expected instruction, the resulting size and protection match your plan, and the retired route shows no unintended new activity. Keep a short before-and-after record, update every affected alert and copier, and use the execution records to investigate any mismatch before restarting the full setup.
Disclaimer:
This content is for informational purposes only and does not constitute financial, investment, or trading advice. Trading and investing in financial markets involve risk, and it is possible to lose some or all of your capital. Always perform your own research and consult with a licensed financial advisor before making any trading decisions. The mention of any proprietary trading firms, brokers, does not constitute an endorsement or partnership. Ensure you understand all terms, conditions, and compliance requirements of the firms and platforms you use.
Also Checkout: Connect Tradovate with Trading view using PickMyTrade
