Migrate from Brokerkit to Zoho CRM

Recruiting workflows and drip sequences do not migrate — they must be rebuilt in Zoho

BrokerKit sequences and recruiting drip emails are proprietary workflow objects with no Zoho CRM equivalent. Zoho's Blueprint and workflow automation tools handle process control differently — they use stage-based blueprints rather than time-triggered drip sequences. FlitStack AI exports your BrokerKit workflow definitions as a structured reference document so your Zoho specialist can rebuild recruiting sequences in Blueprint or Zoho Campaigns. This is the single most common source of migration surprises for BrokerKit teams and must be planned separately.

Agent license number and specialties require Zoho custom field creation before data loads

BrokerKit stores license_number and specialties as standard fields on the Agent object, but Zoho CRM has no native equivalents. Agent_License_Number__c and Agent_Specialties__c must be created as custom fields in Zoho before migration data can be written. If these fields are absent, license data is silently dropped during import. FlitStack creates these fields in Zoho during the setup phase using Zoho's Field API (POST /crm/v8/settings/fields), matching data types (text for license number, multi-select picklist for specialties) before any records are loaded.

BrokerKit recruiting pipelines need Zoho Pipeline creation before deal migration

BrokerKit deal records carry a pipeline association that maps to Zoho's Pipeline object. Zoho Pipelines are not created automatically during data import — the pipeline must exist in Zoho before Deals are loaded so the Pipeline_Id foreign key resolves. If the pipeline is missing, deals land with an unassigned pipeline in Zoho and stage values fail to map. FlitStack creates all Zoho Pipelines during the setup phase using the Pipeline API, replicating BrokerKit pipeline names and stage counts before any deal records are written.

Multi-select specialty fields in BrokerKit require value-by-value mapping in Zoho

BrokerKit agents with multiple specialties store the list as a comma-separated or array value. Zoho CRM multi-select picklist fields require each value to exist in Zoho's picklist definition before import. If a BrokerKit specialty value (e.g., 'Commercial', 'Property Management') does not exist in the Zoho picklist, the record fails to save for that field. FlitStack extracts all BrokerKit specialty values during the discovery phase, creates matching picklist options in Zoho using the Field API before import, and maps each agent's specialties to the corresponding Zoho multi-select field.

Owner resolution by email match can leave orphaned records if BrokerKit agents lack email addresses

BrokerKit agents without a recorded email address cannot be matched to Zoho user accounts during migration. Unmatched agents and recruits are flagged and held in a review queue rather than loaded without an owner. If the original BrokerKit account uses team-based login rather than individual agent email addresses, your team needs to map BrokerKit agent IDs to Zoho user email addresses before migration begins. FlitStack surfaces this during the discovery audit and provides a mapping spreadsheet for your team to complete.