Migrate from Skyward CRM to Freshsales

Skyward CRM Contact records map directly to Freshsales Contact. We extract standard contact fields (name, email, phone, address) and any discovered custom fields during the scoping phase. Email serves as the dedupe key during import. The Freshsales Contact is created before any child Activity import so that the Contact lookup relationship is satisfied at the moment of activity insert. Owner assignment resolves by email match against Freshsales User records.

Skyward CRM Lead records map to Freshsales Lead with the original lead status preserved in a custom field if the customer's lead lifecycle has values not present in the Freshsales default lead status picklist. We extract lead source, rating (if applicable), and any custom fields. Freshsales Lead conversion at migration time is not automatic; the customer chooses whether to convert migrated Leads to Contacts and Accounts post-migration based on their sales process.

Skyward CRM Company records map to Freshsales Account. Company name serves as the primary dedupe key. We extract industry, website, address, and phone fields. Account is created before any Contact import so that the Contact-to-Account lookup is satisfied at the moment of Contact insert. Multi-contact accounts are supported in Freshsales with no junction-table required.

Skyward CRM Deal records map to Freshsales Deal with the contact and company lookups resolved at migration time. The deal amount, expected close date, and owner fields transfer directly. Pipeline stage names in Skyward CRM use customer-defined labels that must be mapped explicitly to Freshsales pipeline stage values during import; we produce a stage-mapping table during scoping. Closed-won and closed-lost dispositions map to Freshsales Deal status values.

Skyward CRM pipeline stages are fully customizable and do not map by name to Freshsales stages. We capture the complete Skyward pipeline configuration during scoping, enumerate every active stage, and map each to a corresponding Freshsales stage value. Probability percentages from Skyward transfer to Freshsales stage weights. Multi-stage pipelines require additional validation to confirm all deal records land in the correct stage after import.

Skyward CRM Activity records tied to contacts and deals map to Freshsales activity types: call engagements to Freshsales Call, email engagements to Freshsales Email, meeting engagements to Freshsales Meeting, and task engagements to Freshsales Task. Activity timestamps are normalized to UTC during import. We resolve the parent Contact or Deal lookup at migration time using the relationship data extracted from Skyward.

Skyward CRM Product catalog entries linked to deals map to Freshsales Product records. We extract product name, SKU, pricing, and description. Product-to-deal associations require junction-table handling during import to preserve the line-item structure. If the customer uses Freshsales CPQ ($19 per user add-on), product pricing tiers and quotes migrate as part of the deal migration scope.

Skyward CRM custom fields on any core object (Contact, Lead, Account, Deal) require manual discovery from the admin panel because no public metadata API exposes the schema. We enumerate every discovered custom field, capture its data type, picklist values, and whether it is required or optional, then configure equivalent custom fields in Freshsales before the import phase. Any custom field missed during discovery results in a post-migration data gap review and a corrective delta import.

Skyward CRM Partner records use a distinct schema from standard contacts, including partner type, commission structure, and shared lead attribution fields. Partner records do not automatically merge with contacts even when the partner is also a customer. We extract partner data into a separate staging table and map each partner to either a Freshsales Contact, a Freshsales Account, or a custom module based on the customer's intended use. The mapping choice is confirmed during scoping.

Skyward CRM Users referenced as record owners map to Freshsales User records. We extract the full user roster by email during discovery and match by email against the Freshsales User table. Any Skyward Owner without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on records resolves at migration time using the validated user mapping.