Migrate from SortScape to Freshsales

SortScape clients who are sole traders or residential customers map directly to Freshsales Contacts. We preserve the primary contact name, phone, email, and all custom client fields as Freshsales Contact custom fields. The SortScape client ID is stored as Source_System_ID__c for delta-run deduplication.

SortScape commercial clients with multiple contacts require both a Freshsales Account record (the business) and one or more Contact records (the people). The primary SortScape contact becomes the primary Freshsales Contact linked via AccountId; additional contacts on the same client become related Contact records with their own AccountId links.

SortScape stores service addresses on clients. For residential clients, the address migrates to the Freshsales Contact address fields (Street, City, State, Postal Code, Country). For commercial clients, the service address becomes the primary address on the Freshsales Account record, with any site-specific variations stored as custom fields on the linked Contact.

Each SortScape job run becomes a Freshsales Deal. The job name maps to Deal name, the billed amount maps to Deal amount, the job status (Completed, In Progress, Scheduled) maps to Freshsales Deal stage via value mapping. Close date is set to the job completion date for closed jobs; open jobs retain their scheduled date. The linked SortScape client resolves to the Freshsales Contact or Account before the Deal is created.

SortScape job statuses map to Freshsales Deal stages by business rule: 'Completed' maps to 'Closed Won', 'Cancelled' maps to 'Closed Lost', 'Scheduled' maps to 'Prospecting' or your first pipeline stage, and 'In Progress' maps to 'Value Proposition'. Your existing Freshsales pipeline stages take precedence — we map SortScape statuses to the closest stage name in your current Freshsales deal pipeline.

Each SortScape field visit — the individual stop within a job run — migrates as a Freshsales Task (for completed actions like mowing, pruning, mulching) or Event (for scheduled appointments with a start/end time window). Original visit date, duration, and worker assignment are preserved on the task or event record. The task/event is linked to the parent Deal and the Contact representing the client.

SortScape workers resolve to Freshsales Users by email address match. Workers without an email in SortScape are flagged during planning — your team decides whether to create Freshsales user accounts for them or assign their completed jobs to a fallback owner. Workers who do not need CRM access are not migrated as users but their job history still transfers as completed Tasks linked to the client Contact.

SortScape custom fields like 'Service Type' (e.g., Lawn Mowing, Hedge Trimming, Garden Design) that are set on jobs migrate as Freshsales Deal custom fields. We create a pick-list custom field on Deal using the exact service type values from SortScape, so reporting by service type works in Freshsales out of the box.

Equipment tracking fields from SortScape (e.g., mower type, leaf blower, ride-on mower, hedge trimmer, or brush cutter) migrate to Freshsales Deal custom fields. When SortScape stores multiple equipment values per job, we configure a multi-select pick-list in Freshsales to preserve the complete equipment inventory for each job, ensuring that all asset information is captured and available for service reporting and analytics within Freshsales.

SortScape notes fields capturing site-specific conditions, access instructions, or client preferences migrate to Freshsales Contact custom fields (for client-level notes) or Deal custom fields (for job-level notes). We store these as text-area fields so the full note text is preserved and searchable in Freshsales.

SortScape invoices pushed to Xero or QuickBooks have no direct Freshsales equivalent. We map the invoice amount to the Deal amount and preserve the invoice reference number as a custom field on the Deal. Actual invoice records remain in your accounting software — they are not duplicated inside Freshsales.

SortScape recurring schedule templates and availability rules cannot migrate to Freshsales. Freshsales has no native scheduling engine. Teams rebuilding scheduling in Freshsales should use Freshsales Tasks with due dates, or integrate a third-party scheduling tool like Calendly or a field-service add-on from the Freshworks Marketplace.