Migrate from Lofty to Freshsales

Lofty People records are migrated directly to Freshsales Contacts, using email as the primary deduplication key. Standard fields such as phone, mobile, job title, and address transfer as‑is, and any custom fields are created in Freshsales before load. People lacking a linked Company become unlinked Contacts, while owner assignment is resolved by email matching to Freshsales users.

Lofty inbound Leads are migrated to Freshsales Leads when they have not yet been converted to People. The Lead Source, Lead Status, and any custom fields are transferred directly, and owner resolution is performed by matching the agent email to a Freshsales user. Leads that share an email with an existing People record are reconciled to the Contact deduplication key, preventing duplicate Contact creation during migration.

Lofty Company records become Freshsales Accounts with direct transfer of name, website/domain, industry, employee count, and annual revenue. Billing address components such as street, city, state, and country map to the Account's billing address fields. Parent‑child hierarchies are resolved by creating the parent Account first and then linking child Accounts via the Parent Account lookup; any circular references are flagged for manual review.

Lofty Deals map to Freshsales Opportunities with deal name → Opportunity Name, amount → Amount, close date → Close Date, and pipeline stage → deal status. Freshsales pipeline and stage names are configured to match Lofty's stage labels. Each Lofty pipeline maps to one Freshsales pipeline.

Each Lofty pipeline stage label (e.g., Showing Scheduled, Offer Made, Under Contract) is assigned a corresponding Freshsales deal status value in the matching pipeline. During migration, FlitStack creates the Freshsales pipeline with the same name and configures each stage with an explicit probability and forecast category. Stages that have no exact counterpart are created as custom status values, ensuring no deal loses its original workflow classification.

Lofty lifecycle stage values are translated into Freshsales Lifecycle Stage pick‑list entries on the Contact record on a one‑to‑one basis. For example, Lofty's Active Lead maps to Freshsales Lead, while Client maps to Customer, and other states follow the same logic. If a Lofty lifecycle value has no matching Freshsales option, FlitStack creates a custom pick‑list entry so that no contact loses its original status after migration.

Lofty custom fields on People, Companies, and Deals are reproduced in Freshsales as custom fields on the matching objects. FlitStack pre‑creates each field in Freshsales using the same data type—currency fields become Freshsales Currency, single‑select become Picklist, and multi‑select become Multi‑select. Default values, pick‑list options, and field help text are also transferred where present, ensuring consistency across the schema.

Lofty communication activities are migrated as follows: calls and emails become Freshsales Sales Activities with the Type field set to Call or Email, preserving the original date and duration where available. Meetings are transferred to Freshsales Meetings, retaining start time, end time, location, and any custom fields. Notes are moved to Freshsales Notes with their original timestamps, and the owning user is resolved by email matching to a Freshsales user, ensuring attribution in reporting.

Lofty tags are migrated as a custom multi‑select field on the Contact record, preserving each tag as an option. Because Freshsales lacks a native tag taxonomy, the tag field does not appear in standard list views but is filterable via custom reports. Lofty segments that encode geographic regions or team assignments are translated into Freshsales Territory rules where supported; dynamic segment logic must be rebuilt as Freshsales Workflows after migration.

Lofty agents map to Freshsales users matched by email address. If a Lofty agent has no matching Freshsales user, records are assigned to a fallback owner or a placeholder User record is created. Agent-level permissions do not transfer — Freshsales profile and role assignments are configured separately.