Migrate from Realvolve to Freshsales

Realvolve person records map 1:1 to Freshsales Contacts. Name, email, phone, address, social handles, and custom properties migrate directly. Person type (Buyer, Seller, Agent, Vendor) is preserved as a custom pick-list field since Freshsales has no native person-type label. All standard address components are merged into Freshsales address fields; social URLs are stored as custom text fields if needed. The original Realvolve ID is retained for reference.

Realvolve people records flagged as 'Prospect' or without a closed transaction map to Freshsales Leads. Any person that already has a closed transaction record maps to a Freshsales Contact. The split is based on whether a Realvolve Transaction record exists with stage = Closed/Won or Closed/Lost.

Realvolve company records (brokerages, team offices) map to Freshsales Accounts. Account name, website, industry, and employee count fields map directly. Multi-office brokerages may require splitting into multiple Account records if Realvolve stores each office as a separate company record. If a brokerage is represented as a single company with multiple locations in Realvolve, we recommend creating a parent Account and linking each location as a child Account to preserve hierarchy in Freshsales.

Realvolve Property records do not have a direct Freshsales equivalent — property address, MLS number, listing price, and status migrate as custom fields on the associated Freshsales Deal. Listings used across multiple deals may alternatively map to Freshsales Products for price-book alignment.

Realvolve Transaction records map to Freshsales Deals. Transaction stage (Active, Under Contract, Closed, Cancelled) maps to Freshsales Deal stage names. Transaction value, close date, and commission fields migrate to Deal amount, close date, and custom currency fields respectively. Any ancillary data such as escrow instructions or referral source is stored as additional custom fields on the Deal to preserve context beyond the standard pipeline fields.

Realvolve transaction pipelines (Active, Under Contract, Closed) map to Freshsales Deal pipelines. Each pipeline is created as a separate Freshsales pipeline with its own Kanban stages. Stage-order and probability defaults are configurable per pipeline. During migration, we match each Realvolve pipeline name to a newly created Freshsales pipeline, copying stage labels and order; probability percentages can be imported from Realvolve or set to defaults based on deal stage.

Realvolve task records map to Freshsales Tasks. Task subject, due date, assigned user, status, and description fields migrate directly. Tasks linked to Realvolve People or Transactions retain their parent record linkage in Freshsales via the related_to lookup. If a task references a Realvolve person or transaction that hasn't yet been created in Freshsales, we queue the task and resolve the link after the parent record is imported, preserving the relationship.

Realvolve calendar events (showings, closings, inspections) map to Freshsales Events with original start/end timestamps, location, and invitee list preserved. Events linked to Realvolve People or Transactions carry the corresponding Freshsales Contact or Deal lookup. All event details, including description, attendee responses, and reminders, are transferred as part of the event record to ensure no appointment history is lost during the transition.

Realvolve files attached to people, properties, or transactions re-upload to Freshsales as Files attached to the corresponding Contact, Deal, or Account record. File size limits (25MB per Freshsales file) are enforced; files exceeding the limit are flagged for manual retrieval.

Realvolve notes migrate to Freshsales Notes. Rich-text formatting is preserved where possible. Notes are attached to the parent Contact, Account, or Deal record based on the Realvolve note's association context. If a note references an object that hasn't yet been created in Freshsales, we store the note temporarily and attach it after the parent record is available, maintaining the original context.

Realvolve workflow packages (Transaction Coordination, Listing Management, Sphere of Influence, Past Client Follow-up) and individual automation rules do not migrate. FlitStack exports the workflow definition JSON as a rebuild reference for your Freshsales admin to recreate in Freshsales workflows or via the workflow builder API.

Realvolve email and document merge field templates (used for drip campaigns, anniversary reminders, birthday emails) require manual recreation in Freshsales email templates. Template variable names differ between platforms — we export a mapping table of Realvolve merge fields to Freshsales placeholder syntax.

Realvolve user accounts map to Freshsales users by email match. Unmatched users are flagged before migration; the team either creates Freshsales accounts first or assigns records to a fallback user. Role and permission sets do not migrate — Freshsales profile and role assignment is a post-migration configuration step.

Realvolve tags applied to People, Properties, and Transactions migrate as Freshsales tags on the corresponding Contact, Account, or Deal record. Tags are preserved exactly; Freshsales does not enforce tag hierarchies so flat tag lists map cleanly. Any tag that does not yet exist in Freshsales is created on-the-fly during migration, ensuring no tags are dropped due to pre-existing absence in the target system.

Realvolve custom person properties (e.g., lead source, referral source, special instructions) that have no Freshsales standard field equivalent are created as Freshsales custom fields on Contact or Lead. Field type is matched (text, number, date, pick-list) during the mapping phase.