Migrate from Results to Freshsales

Results person records map to Freshsales Lead as the initial import target. If the Results export contains a lifecycle_stage or status property, we use it to determine whether records should land directly as Freshsales Contact instead of Lead. Any email address in Results becomes the Lead Email field and serves as the dedupe key during import. The Results first_name and last_name split is reconstructed at migration time; if only a single name field exists, we use it as LastName and flag the FirstName blank for the customer's admin to populate post-migration.

Results organization records map directly to Freshsales Account. The organization name becomes the Account Name field, and any domain or website field in the Results export becomes the Account Website field. Account is created before any Lead or Contact import so that the Account Lookup relationship is satisfied at the moment of record insert. If the Results export does not include a separate organization record for each person record, we perform email-domain grouping to generate Account records during the transform phase.

If Results exports a separate Lead object distinct from person records, those map directly to Freshsales Lead with status preserved. Any lead_score or rating property from Results migrates to the Freshsales Lead Rating field (Hot/Warm/Cold) or a custom numeric field for raw scoring values. Lead owner resolves by email match against Freshsales User records created during the migration User setup phase.

Results deal records map to Freshsales Deal. The deal name, amount, close_date, and stage from Results export map to Freshsales Deal Name, Amount, Close Date, and Deal Stage respectively. If Results includes a pipeline identifier, we configure Freshsales Pipeline and Stage values before migration to match the customer's pipeline structure. Stage values that do not exist in Freshsales are pre-created during the schema setup phase.

Each distinct stage value in the Results deal export requires a corresponding Deal Stage in Freshsales. We create the stage values during schema setup, preserving the Results stage name and optionally mapping to a standard Freshsales stage label (Appointment Scheduled, Qualified to Buy, Presentation Scheduled, Decision Maker Bought-In, Contract Sent, Closed Won, Closed Lost) if the customer approves a label normalization. Stage probability percentages from Results migrate as-is if numeric, or we assign default Freshsales probabilities if the source does not track probability.

Results owner records map to Freshsales User by email address match. We require the customer to pre-create Freshsales User accounts matching the owner emails in the Results export before migration begins, or we hold owner references in a reconciliation queue until User provisioning is complete. Active/inactive status on Freshsales User must match whether the original owner is active in Results. OwnerId is required on Deal and Contact insert; unresolved owners block import.

Results task records map to Freshsales Task. Status, Priority, ActivityDate, and subject migrate directly. The Task WhoId links to the migrated Lead or Contact; the Task WhatId links to the migrated Deal or Account. We resolve these parent references by querying the migrated record IDs using the email address or external ID from the Results activity record as the lookup key. If the Results export does not include the person ID on activity records, we fall back to email-based matching.

Results meeting records map to Freshsales Event. StartDateTime, EndDateTime, and Location migrate directly. Attendee information from Results migrates to EventRelation records linked to the corresponding Contact or Lead. If Results stores meeting attendees in a separate association table, we reconstruct EventRelation records during the transform phase. Meeting subjects become the Event Subject field.

Results notes map to Freshsales Note records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, or Deal). Note body migrates as plain text. If the Results export includes note attachments, those migrate as ContentDocument records linked to the same parent. We preserve the original created date as the Note CreatedDate for audit continuity.

Any custom fields in the Results export require pre-creation in Freshsales before migration begins. We create Freshsales custom fields with the exact column header name from the Results CSV export to enable automatic field mapping during import. Field types must match: text exports map to Freshsales text fields, numeric exports map to number fields, date exports map to date fields. If a Results custom field uses a picklist format, we create the corresponding Freshsales picklist with the exact option values before migration.