Define what the firm needs to keep
You see the same pattern in nearly every prop firm technology setup: the provider says the firm owns its data, but the contract does not say what that data includes or how the firm can retrieve it. That gap matters when a provider changes its product, raises fees or becomes unsuitable for the business.
Start with an inventory. A funded-trader operation may need to retain:
- Trader profiles, account identifiers, challenge purchases and status history.
- Orders, fills, balances, drawdown events, rule breaches and risk decisions.
- KYC outcomes, payment references, support tickets and communication records.
- Configuration history, audit logs, user permissions and linked documents.
Separate ownership from privacy obligations. A firm may be the data controller for trader records while the platform acts as a processor. That does not automatically give the firm a usable copy of every record, source file or log.
Nor does it settle how long information must be retained, who can access it or what must be deleted after termination. Those duties need to match the firm's privacy notices, processing agreement and regulatory obligations.
For a shortlist of platform vendors, use the PropFirm Provider marketplace to compare what each one offers, then verify the data rights in the contract itself.
Compare the ownership models
Contracts usually land somewhere between four approaches. Each can work, but they shift control, cost and operational responsibility in different ways.
- Provider-hosted with a basic export. The vendor runs the database and grants the firm a right to retrieve selected records, often as CSV files. This is usually the simplest arrangement to operate. It can be adequate for reporting or an orderly wind-down, but exports may omit relationships, event history or attachments. The firm remains dependent on the provider's export tooling.
- Provider-hosted with API access. The firm can retrieve defined records through an application programming interface, sometimes with webhooks for ongoing changes. This supports regular backups and connection to a separate warehouse. It costs more to build and maintain, and API limits, version changes or missing endpoints can make it less complete than it appears.
- Customer database or warehouse copy. The provider sends data into a database controlled by the firm, either continuously or on a schedule. This gives operations and analytics teams more control and reduces reliance on a one-off exit export. The firm must pay for storage, access controls and technical support, and must reconcile records when the two systems disagree.
- Self-hosted or licensed deployment. The firm runs more of the stack itself or holds a licence that permits continued use. This can offer stronger control over infrastructure and retention, but shifts patching, security, backups and business continuity onto the firm. Check whether licences include third-party components that stop working when the provider contract ends.
There is also a distinction between a copy of data and a copy of the working system. A provider may export account history while retaining its schemas, scoring logic, dashboards and proprietary risk rules. For most firms, a well-defined data export is more achievable than a transfer of the provider's software or intellectual property.
Make portability testable
"Export on request" is not a specification. The contract or a technical schedule should describe the export format, fields, frequency, delivery method and support included.
Ask for a sample file before signing. Have an operations or data lead confirm that it can be read without the vendor's software.
A practical export should preserve stable trader and account IDs, timestamps with stated time zones, status changes and links between challenges, accounts, trades and payments. It should include both current records and relevant history. If the provider supplies CSV, ask for a field dictionary and a separate file for each related record type. For JSON or an API, request a schema, authentication method, pagination rules, rate limits and a notice period for breaking changes.
Test the awkward parts, not just the headline fields. Can the firm retrieve rejected KYC outcomes, attachments, deleted-account history, risk rule changes and support notes?
Are trade events recorded as a sequence, or only as the latest account balance? Does an export show which rule version triggered a breach? Missing context can prevent the firm from answering a trader dispute or reconstructing a risk decision.
Also map the boundaries. Trading platforms, payment providers and identity-check services may retain their own records under separate contracts. A prop firm technology provider may only pass through a reference or status. List those third parties, identify who can request their data and confirm whether their own exit terms fit the main platform agreement.
Price the exit before signing
Ask for a written exit quote with the same scope as the proposed contract. The figures below are typical market ranges for planning, not quotes or audited results for any named provider. The actual fee depends on data volume, record quality, custom fields, attachments and the amount of mapping or reconciliation required.
| Exit approach | Typical one-off cost range | Typical delivery range | Common scope |
|---|---|---|---|
| Standard CSV export | £0 to £5,000 | 5 to 15 business days | Defined tables and basic field mapping |
| Assisted standard migration | £2,000 to £15,000 | 2 to 6 weeks | Export, mapping support and validation |
| Bespoke migration | £10,000 to £50,000 or more | 4 to 12 weeks | Custom schemas, attachments and reconciliation |
These typical market ranges can overlap because "migration" may mean a file delivery at one end and a tested transfer into a replacement system at the other. Ask whether fees cover a full data set, one export or repeat requests.
Check for separate charges for engineering time, storage, secure transfer, API access and post-termination archive access. An archive fee may be charged monthly, so ask how long the firm must pay it and whether the charge stops once the export is accepted.
Set the service level too. A typical market range for an exit window is 30 to 60 days after termination, but the clock should start only when the firm has received a complete export in the agreed format. Provide for a short acceptance period, correction of missing or corrupt files and reasonable read-only access while the replacement is being tested.
Negotiate the rights and limits
Make the contract distinguish firm data, provider materials and third-party data. The firm should retain rights to trader and business records it supplies or generates. The provider can reserve its software, generic templates and know-how, but that reservation should not be used to withhold the firm's transaction history or prevent it from using its own records with another supplier.
Check these clauses against the main agreement, data processing agreement and any service schedule. In particular, align them on:
- Scope and format: identify records, attachments, logs, schemas and field definitions. Avoid wording that limits delivery to "available data" without defining what is available.
- Frequency and access: state whether exports are self-service, scheduled or request-based. Set a response time and include a right to retrieve data during the contract, not only at exit.
- Fees and assistance: list included exports and any chargeable migration work. Require prior approval for additional work and a rate card or capped estimate.
- Retention and deletion: state when live data, backups and copies held by subprocessors are deleted, subject to lawful retention duties. Require written confirmation when deletion is complete.
- Suspension and termination: ensure a billing dispute or termination does not immediately block access to records needed for a safe transition. Define any read-only period and the conditions for using it.
- Change of control and insolvency: clarify notice and access rights if the provider is acquired, stops trading or discontinues the service.
Do not rely on an informal promise from sales or implementation staff. Attach the export specification and agreed exit assistance to the signed contract. If the supplier says a requirement is outside its standard terms, record the exception and its cost. Comparing contract detail alongside platform capabilities is part of the vendor review; the provider directory can help structure that shortlist.
Use a checklist before committing
Before signature, assign a named owner for the export test, usually someone in operations or data. A technical contact should verify the files, while compliance checks retention and deletion requirements. Run this numbered checklist with each shortlisted provider:
- Request a sample export using realistic trader, challenge, account and trade records.
- Confirm the export includes history, identifiers, timestamps, attachments and audit events the firm needs.
- Load the files into a neutral database or spreadsheet without vendor-only tooling.
- Reconcile sample account totals and status changes against the live platform.
- Ask for the complete fee schedule, delivery window and support scope for an exit.
- Confirm the firm can access data during the contract and has a defined post-termination window.
- Document third-party records, retention duties and deletion evidence in the contract pack.
- Save the export specification, test result and agreed exceptions with the signed documents.
This week, ask every shortlisted provider to complete the same timed export test against a sample account and return the formats, fees and delivery time in writing.
Frequently Asked Questions
Who owns trader data in a prop firm platform contract?
The contract should identify the firm's rights to trader, account, transaction and operational records, while separating those records from the provider's software and generic materials. Privacy law may also make the firm a controller and the provider a processor, but those roles do not by themselves guarantee a complete, usable export.
What data should a prop firm get when leaving a provider?
Request trader and account records, challenge and payment references, trade and risk history, status changes, support records, audit logs and relevant attachments. Ask for stable identifiers, timestamps, a field dictionary and the links between related records.
How much does a prop firm platform data migration cost?
Typical market ranges run from £0 to £5,000 for a standard CSV export, £2,000 to £15,000 for assisted migration and £10,000 to £50,000 or more for bespoke work. Data volume, attachments, schema changes and reconciliation can move the cost beyond those planning ranges.
Can a provider charge for exporting my data?
A contract may allow reasonable fees for engineering or migration support, so check what routine exports already include and require approval for extra charges. Agree the format, delivery window and any post-termination archive fees before signing.
