Migrate from Agentbox to Freshsales

Agentbox contacts migrate directly to Freshsales contacts via a one-to-one field mapping. The primary linked Agent becomes the OwnerId reference in Freshsales, resolved through email matching against Freshsales user accounts. All standard contact fields — including first name, last name, email address, phone number, mobile number, physical address components, and contact type — map directly without transformation. The contact type field in Agentbox may require a pick-list value review in Freshsales to ensure consistency across migrated records.

Agentbox company records encompass agency branches, property developer clients, and landlord records, all mapping to Freshsales accounts. The company type and industry fields present a mapping challenge because Freshsales standard industry pick-list values do not fully cover real estate sub-types such as property management firms, strata management companies, or boutique developer agencies. We store these specialized sub-types in a custom pick-list field on the Account record to preserve the full agency classification context from Agentbox.

Agentbox agent profiles containing name, email address, mobile number, and license credentials transform into Freshsales user accounts. License numbers representing regulatory compliance requirements are preserved in a custom text field named License_Number__c on the User record. Email address serves as the matching key driving the OwnerId linkage for all records migrated from Agentbox, ensuring that agent-owned contacts, properties, and listings land under the correct Freshsales user account automatically.

Agentbox native property objects containing address, property type, number of bedrooms, number of bathrooms, and price guide have no direct Freshsales equivalent. FlitStack creates a Property custom module within Freshsales and migrates every property record into this module, establishing a lookup relationship linking each property to its owning Contact or Account record. This lookup preserves the relationship context from Agentbox where properties were tied to specific contacts or companies.

Agentbox listing records storing listing status, listing type, asking price, and REA listing identifier migrate into a Freshsales Listing custom module. Historical REA import data originally brought into Agentbox may include structured sub-records such as price history or agent notes that do not map cleanly to individual fields. When direct field mapping is not possible, this nested historical data is preserved as a JSON-formatted text blob within a custom long-text field on the Listing record, maintaining data completeness even if the original structure cannot be normalized.

Agentbox appraisal records containing property address, appraisal date, appraised value, and appraiser agent information require a dedicated Appraisal custom module in Freshsales. Each migrated appraisal record is linked via lookup relationships to both the corresponding Property custom module record and the Contact record of the client who requested the appraisal, preserving the relational structure from Agentbox where appraisals were inherently tied to specific properties and clients.

Agentbox buyer and tenant requirement records containing budget range, property type preferences, preferred location, and desired bedroom count migrate as custom fields on the Freshsales Contact record. When Agentbox stores multiple criteria values within a single field, these are preserved using pipe-delimited text strings or converted to multi-select custom fields depending on the original source field structure, ensuring the requirement data remains searchable and actionable in Freshsales.

Agentbox notes and tasks attached to contacts, properties, or listings migrate to Freshsales Notes and Tasks respectively, with original creation timestamps and linked agent associations preserved. When notes in Agentbox were attached to Property or Appraisal custom module records that cannot receive notes directly in Freshsales, those notes are attached to the linked Contact record instead, maintaining the informational context even if the attachment point shifts within the data model.

Agentbox contact categories and tags migrate to Freshsales tags applied to the corresponding Contact, Account, or custom module record depending on what object received the tag in Agentbox. Tags transfer as-is without transformation so that all filtering logic, segmentation rules, and automated workflow triggers built on tag conditions in Agentbox continue functioning in Freshsales using the identical tag names and application scope.

Files attached to Agentbox contacts, companies, or listings are downloaded from the source system and re-uploaded to Freshsales Files attached to the equivalent record in the destination CRM. Freshsales enforces a 25-megabyte per-file size limit; any files exceeding this threshold are flagged in the migration audit report for manual handling, ensuring your team can individually assess and transfer oversized attachments through alternative methods.