Open the receiving exchange's deposit page first, select the asset and supported network, and copy its address and memo if required. Use matching details in the sending exchange's withdrawal form. Check net arrival and both providers' requirements, then follow the withdrawal and deposit records.

Define the destination before touching the source balance

Choose the asset you actually need on the receiving exchange. A familiar stablecoin or low-fee network is useful only if the destination supports that exact deposit and you can use it for the intended next action.

Open Deposit in the receiving account and inspect the network list, current operational status, address, memo, minimum, and transfer-type requirements. Use the instructions for your own account rather than a general public address.

If you plan to trade a particular pair after arrival, verify that market and the account's permission to use it. A deposit route can work while the eventual market or product remains unavailable.

Record which balances are already available at the source. If you must sell or convert first, include the trade's costs and any constraints. Do not assume a displayed total is free from open-order reservations or product commitments.

Destination depositSource withdrawalAccount credit
A transfer between exchanges must match receiving deposit instructions, sending withdrawal details, and final customer-account credit.

Build a compatible route

Open Withdraw at the sending exchange for the chosen asset. Find a network that exactly matches the destination's supported route. If one side uses an abbreviation, verify its full meaning through official help.

Do not choose based on fee alone. Address formats can be shared across EVM networks, and token symbols can describe different contracts. The recipient's stated support determines whether the deposit can be allocated.

Inspect the source's withdrawal status and the destination's deposit status. If either side has suspended the required route, that route is not currently usable just because a historical fee table lists it.

If no common route exists, research a complete alternative before moving anything. It may involve another asset or a legitimate conversion route, with additional costs and risks. A network dropdown does not automatically bridge an incompatible transfer.

Some providers offer connected-account transfer features. When used, read the integration, authorization, conversion, and delivery terms. A simplified interface can still send an ordinary on-chain transfer whose compatibility requirements remain important.

Calculate net arrival before submission

Read whether the sending form expects total deduction or amount received. Record the withdrawal fee and expected net delivery. Compare that net amount with the receiving exchange's minimum credit.

A test amount must meet both ends' thresholds. An amount accepted for withdrawal can still be too small for the destination to credit. Include the extra fee of a test when planning the main transfer.

If the source balance is subject to a funding hold, inspect its withdrawable portion. Buying or converting another asset may not remove an underlying restriction. Check the provider's account notice.

If a trade is necessary before sending, use actual net holdings after its fees. If a trade is needed after receipt, include that step when comparing total cost. The best route is determined at the final usable endpoint rather than the cheapest isolated withdrawal.

Keep the amount in original token units before converting it to money. Market prices can change during processing, so a different fiat valuation at the destination does not by itself mean tokens are missing.

Send and retain both sides' references

  1. Copy the destination's current address and required memo from its authenticated deposit page. Verify the entire value after pasting at the source.
  2. Select the matching asset and network, enter the amount, and review the source's final withdrawal summary.
  3. Complete any destination-registration, beneficiary, or security checks through the sending provider's official flow.
  4. Save the withdrawal request reference. Once a transaction hash becomes available, record the network and open the correct explorer.
  5. Monitor the receiving exchange's deposit history. Check its confirmation and review requirements instead of assuming on-chain inclusion equals immediate availability.
  6. Confirm the net credit and any restrictions before placing a trade or forwarding the funds.

Troubleshoot the missing milestone

If the source is still processing and no hash exists, start with its withdrawal record and support. The destination cannot credit a transfer that has not been sent.

If the network transaction is pending, inspect that record and the sending provider's guidance. As a customer, you normally do not control the provider's transaction nonce or replacement fee.

If it succeeded to the correct deposit address, check the recipient's confirmation count, asset support, memo, and crediting status. A customer-account ledger is a separate layer from the public address balance.

If a memo is missing, use the destination's official recovery procedure where available. Do not send a second transfer with the missing memo and assume it will repair the first automatically.

If the route is wrong, preserve the actual hash, asset, network, and destination. The receiving custodian controls the address and may need to assess recovery. Any availability, charge, or timing is case-dependent.

Avoid sharing passwords, authentication codes, or wallet recovery material while asking either provider to trace the transfer. Public references and appropriate account evidence should identify the relevant process.

Make the route repeatable without assuming it is permanent

Keep the source withdrawal, public transaction, and destination credit references together. These explain how funds moved between the accounts and can support later reconciliation.

If the source batched withdrawals, the explorer's total network fee can differ from the fee charged to your customer account. Use each record for the question it actually answers.

Before using a saved destination again, reopen its deposit page and check support and address instructions. Providers can change networks, retire addresses, or update requirements.

When recording the route's cost, include only steps actually performed and mark estimates separately. If you considered an alternative but did not execute it, do not present its quote as a tested result.

The task ends with the intended asset credited and usable under the receiving account's rules. A successful source withdrawal is important evidence, but it is not the whole cross-exchange workflow.

When transferring for a deadline, note the deposit availability required for the next task. A balance credited for trading can still have a different withdrawal status. If the plan is immediately forwarding the funds again, verify that permission explicitly. This avoids measuring success at an intermediate account credit that does not yet complete the route you actually need.

Reader questions

Is an internal transfer between users the same as moving between exchanges?

No. A provider's internal transfer can use a different record and fee model. Transfers across providers need the route supported by both sides.

Should I always convert to the coin with the smallest fee?

Include conversion costs, market exposure, minimums, and destination support. A low withdrawal fee alone is insufficient.

Can the source exchange fix a missing recipient memo itself?

The receiving custodian usually needs to assess allocation or recovery. Provide the source record and hash through the appropriate official process.

Sources and further reading