Migrate from RAYNET CRM to Freshsales

RAYNET Contact records map directly to Freshsales Contact. Standard fields (first name, last name, email, phone, address) map 1:1. The RAYNET lifecycle stage property (contact_status) maps to Freshsales lifecycle_status, which supports standard values (Lead, Customer, Evangelist, etc.) configurable in Freshsales CRM Settings. GPS coordinates auto-derived from RAYNET address fields transfer as two custom text fields (latitude, longitude) since Freshsales has no native GPS storage. Custom Contact fields extract from RAYNET XLSX export and map to Freshsales custom fields of matching type.

RAYNET Account records (RAYNET calls them Companies) map to Freshsales Account. The Account name, website, industry, phone, and address fields map directly. Accounts are imported before Contacts so that the Contact-Account lookup is satisfied at the moment of Contact insert. Custom Account fields map to Freshsales Account custom fields by type. Multi-address support (billing and shipping) is handled by mapping RAYNET address fields to Freshsales billing and shipping address composites.

RAYNET Deal records map to Freshsales Deal. Deal name, value, probability, estimated close date, and owner map directly. Pipeline stage mapping is explicit: each RAYNET pipeline stage becomes a Freshsales deal stage value in the matching pipeline. Closed-Lost and Closed-Won statuses from RAYNET translate to Freshsales Won and Lost stages. RAYNET ENTERPRISE customers with multiple pipelines must decide how to consolidate or map to Freshsales pipelines before migration; this is resolved in scoping.

RAYNET pipeline stages (stage name, order, probability percentage) map to Freshsales pipeline stages with the same properties. If RAYNET uses a single pipeline (START or PROFESSIONAL tier) and the customer wants multiple Freshsales pipelines, we create the target pipeline structure before Deal import. Probability values map from RAYNET to Freshsales stage probabilities, rounded to whole numbers. Stage count limits are not a constraint on Freshsales Growth and above.

RAYNET activity records (calls, emails, meetings) map to Freshsales activities. Call duration, disposition, email subject and body, and meeting start/end times and locations transfer directly. Each activity is linked to the migrated Contact or Account via Freshsales CRM lookup. Activity timestamps are preserved in the activity record to maintain the chronological timeline. Custom activity types require value mapping against Freshsales activity type picklist.

RAYNET Sales Order is a separate object with Subject, Final Price, Status, Estimated Costs, Delivery Date, and address fields. Freshsales does not have a native standalone Sales Order object; line-item detail is managed within a Deal via products. We offer two migration paths during scoping: map Sales Order line items to Freshsales products attached to a Deal, or create a Freshsales custom object (Sales_Order__c) to preserve the standalone record. The customer chooses based on their quoting workflow needs. XLSX export of Sales Orders is the primary extraction method since the REST API does not expose a dedicated Sales Order endpoint.

RAYNET Quote records (linked to Deals and Accounts with validity dates and line-item pricing) do not have a native Freshsales Quote object at the Growth and lower tiers. We map Quote data to Freshsales Deal custom fields (quote_validity_start, quote_validity_end, quote_status) and attach Quote PDFs as files to the Deal record. If the customer requires a formal quote object, Freshsales Estate tier includes a native Quotes module; we flag this for the customer during scoping.

RAYNET User records map to Freshsales User by email match. We extract every distinct owner referenced on Contact, Account, Deal, and Activity records and resolve to Freshsales User IDs before record import. Owners without a matching Freshsales User go to a reconciliation queue for the customer admin to provision before the relevant record phase begins.

RAYNET Tags on Contacts and Deals are extracted as label arrays from the XLSX export and mapped to Freshsales Tags (native tag functionality on Contacts and Accounts) or to a multi-select custom field depending on the customer's tagging strategy. Tags used for lead scoring or segmentation are better stored as a multi-select picklist to support filtering and reporting.

Files attached to RAYNET Contacts, Accounts, Deals, and Activities are exported via XLSX export with cross-referenced record IDs. In Freshsales, attachments re-associate using the migrated record's Freshsales ID cross-referenced against the original RAYNET ID mapping table. The file name and any metadata are preserved. Large attachment sets (over 5 GB total) may require batched upload to avoid Freshsales file import timeout.