Import trades from Moomoo

What this does

Brings Moomoo, also known as Futu, trades into VEXA from a trade history export.

Before you start

• Automatic sync shows a Coming soon banner, and even when it arrives it will not be for most people. Moomoo’s API requires their OpenD gateway application running on your own computer, an approved developer application, and a wait of a day or two. VEXA’s own instructions say most users should upload a file instead, and that advice stands.
• Set your broker server timezone first, and set it to the market you trade, not where you live. Moomoo covers US, Hong Kong, mainland China, Singapore and Australia markets, and each is on its own clock. See Set your broker server timezone.
• Two years of history.

Steps

Limits and gotchas

• The timezone is the thing that goes wrong. If you trade US markets from Singapore and leave the setting on Singapore, every trade lands on the wrong day.
• Modern Moomoo exports break each order into fill rows and carry a long list of fee columns: commission, platform fees, trading fees, clearing fees, stamp duty and levies. VEXA reads all of them, so your profit figures are net.
• If you trade more than one market, export and upload them separately and set the timezone for each before uploading.

What you should see

A result panel naming the Moomoo trade history format, with counts. Fees appear in the trade’s execution timeline, so a trade’s net profit should match what Moomoo shows.

If it doesn’t work

• Every trade is on the wrong day. The broker server timezone is set to the wrong market. Fix it and re-import.
• “No trades were found in this file.” You exported an account or cash statement rather than trade history, or the file is still in Excel format.
• You are trying to set up the API. Unless you are comfortable running the OpenD gateway on your own machine, use the file.