Migrate from Market Maker to Freshsales

Trading-specific custom fields require Freshsales custom field creation before data lands

Market Maker stores strategy names, risk tiers, instrument types, P&L figures, and order parameters as custom fields on trader, firm, position, and order objects. Freshsales requires each of these to be pre-created as custom fields on the corresponding standard object (Contact, Account, Deal, Task) before the migration runs — the Freshsales API rejects records with unknown field names. FlitStack AI delivers a Freshsales custom field setup plan before data moves, specifying the field label, type (text, pick-list, number, currency), and pick-list values for every trading-specific field so your Freshsales admin can create them in advance. Without this pre-work, records migrate without these fields and the data is lost.

Multi-leg positions require Deal Products — single Deal rows do not capture leg-level P&L

Market Maker multi-leg strategies (options spreads, pairs trades, straddles) store each leg as a separate position record linked by a group ID, with P&L tracked at both the leg and group level. Freshsales Deals are single-row records with one amount field — storing each leg as a separate Deal loses the group-level P&L view and creates orphan Deals with no clear association. FlitStack AI maps multi-leg positions to a single Freshsales Deal with multiple Deal Products: each leg becomes a Product Line Item with quantity, price, and side (long/short) preserved. The strategy group ID is stored as a custom field on the parent Deal so reporting can aggregate across legs.

Freshsales API rate limit of 10 requests per second affects large order-history migrations

Freshsales API enforces a 10 requests per second rate limit per integration key. Market Maker setups with large order histories (hundreds of thousands of rows) can exceed this limit with naive API calls, resulting in 429 Too Many Requests responses that stall migration progress. FlitStack AI implements request queuing with exponential backoff — orders are batched into payloads of up to 100 records per call and spaced to stay within the 10 req/s ceiling. Migration logs track every throttled request and retry so no orders are silently dropped. For setups with over 200,000 orders, FlitStack coordinates a migration window outside peak API usage hours to maximize throughput without hitting rate limit errors.

Risk alert rules and threshold triggers do not migrate — they must be rebuilt as Freshsales workflows

Market Maker risk alerts (margin call notifications, drawdown threshold breaches, position limit warnings) are configured as automation rules with conditions tied to position P&L, account balance, and instrument price data. Freshsales workflow rules use a different condition syntax, object model, and action set — there is no import, export, or conversion path between them. FlitStack AI exports the Market Maker alert rule definitions as a written specification document (rule name, trigger condition, action, and notification recipient) so your Freshsales admin can rebuild them as Freshsales workflow rules or Freshsales AI conditions. This specification is delivered alongside the migration plan and does not delay the data migration itself.

Firm hierarchy mapping to Freshsales parent Account requires a top-down migration sequence

Market Maker firm hierarchies with multiple levels (holding company → regional firm → desk-level entity) map to Freshsales Account with Parent Account links. Freshsales requires parent Accounts to exist before child Accounts can reference them via ParentId — migrating all firms simultaneously causes foreign-key validation errors for any firm with a parent reference. FlitStack AI sequences the migration top-down: the top-level firm migrates first as a root Account, then child firms migrate and link to the parent. Firms with no parent reference migrate in parallel. This sequencing is specified in the migration plan and automated by FlitStack's dependency graph before the first API call lands in Freshsales.