Client Management

Yes, and they behave like the fields that ship with it. Custom fields can be text, numbers, dates, currencies or lists, they can be required at a particular stage, they can be restricted to certain roles, and they can be segmented on and reported from like anything else. Most desks add a handful in the first month — a regulatory category, an internal risk grade, a referral note — and the point is that those become part of the record rather than a comment field somebody agreed to keep updated.

To the field. A role decides which clients open at all, which sections of the record are visible, which fields can be read, which can be changed and what the operator is allowed to approve. A sales desk sees its own book and nothing from another; support can open any client but not the ledger; compliance reads everything and writes nothing. Approval limits sit on the operator rather than the department, so covering for someone on leave never quietly hands over a larger limit than it should.

They merge, and nothing is thrown away. Duplicate detection runs on email, phone and document number as records are created, so most never get that far; when one does, merging keeps both histories, both sources and both sets of documents against the surviving record, and notes which record it came from. Trading accounts and wallet movements follow the merge, and the introducing partner tag on each is preserved — which matters, because a merge that quietly reassigned a rebate would be a worse problem than the duplicate was.

It holds them. Identity documents, proof of address, bank statements and anything else a client uploads sit on the record with their type, their status, who approved them and when they expire. Expiry is the part most systems miss: the record warns before the date rather than after it, so the request for a fresh document goes out while nothing is urgent instead of on the morning the client is trying to withdraw and is already annoyed.

That is what segments are for. Any field on the record can be a condition, conditions combine, and the result is saved and reused rather than rebuilt. Clients in Malaysia on MT5 who funded once and have not logged in for ninety days is a segment, not a ticket to the data team. Because a segment is a live query rather than a snapshot, the list is right on the morning it is opened, and bulk actions run against it where the role permits.

Client records, trading accounts, documents that were already verified, wallet balances, the partner tree and the history attached to all of it. A client who logs in after the move finds the account they had rather than a blank one, and an operator opening a record finds the notes their predecessor left. Platform connections are set up alongside the migration, so a desk switching systems is not also switching how it trades while it learns a new console.