Migrate from Nookal to Freshsales

Nookal client records map directly to Freshsales Contacts. Client first name, last name, email, phone, and address fields map to Freshsales Contact fields. Records without an email address require special handling — Freshsales Create Contact API requires a valid email, so FlitStack flags email-missing records before migration for manual resolution.

Nookal client business details (company name, industry, website) merge into a Freshsales Account record linked to the Contact via the AccountId lookup. If a Nookal client has no company affiliation, FlitStack attaches the Contact to a default 'Unassigned Account' record in Freshsales.

Nookal locations (clinics, practice sites) map 1:1 to Freshsales Account records. Location name becomes Account Name, and location address, phone, and email map to the corresponding Account fields. Each location-account retains its address as the primary billing or service address for appointments and invoices associated with that site.

Nookal practitioner records map to Freshsales Users by email address match. FlitStack resolves each practitioner email against Freshsales user accounts before migration — unmatched practitioners are flagged so they can be invited to Freshsales before the migration runs. Practitioner specialty and title map to custom fields on the User or Contact record.

Nookal appointment records have no direct Freshsales equivalent because Freshsales is not a scheduling system. FlitStack creates a custom Appointments module in Freshsales with fields for appointment date, time, duration, practitioner (linked via Contact or User lookup), client (linked via Contact), location (linked via Account), appointment type, and status. If your Freshsales plan does not support custom modules, appointments migrate as custom fields on the Contact record with date, type, and practitioner encoded as text.

Nookal clinical notes, treatment plans, and assessment data store as custom text or long-text fields in Freshsales. FlitStack creates Treatment_Plan__c and Clinical_Notes__c custom fields on the Contact object. Large clinical documents may be attached as Files linked to the Contact record. Note timestamps and practitioner author information are preserved in custom datetime fields.

Nookal invoice records do not map to a standard Freshsales object because Freshsales has no native invoicing. Invoice amount, status (paid/unpaid/overdue), and date map to custom fields on a Freshsales Deal record — Invoice_Amount__c, Invoice_Status__c, Invoice_Date__c. Line items are stored as custom multi-select or text fields. Full invoice PDF files are attached to the Deal record as Salesforce Files equivalents.

Nookal payment records (Medicare bulk-bill payments, patient payments, DVA claims) migrate as custom fields on the related Deal (for invoiced amounts) or as activity Notes attached to the Contact. Payment date, amount, payment method, and reference number are preserved. Payment history that spans multiple appointments is aggregated into a Payment_Summary__c text field on the Contact record.

Nookal Medicare and DVA claiming data has no Freshsales equivalent. Claim status, provider number, service type, and claim reference number migrate as custom fields on the Contact or Deal record. FlitStack creates Medicare_Provider_Number__c, DVA_Claim_Status__c, and Claim_Reference__c fields. Note that Medicare 2.0 claiming logic (deadline June 30, 2025) must be rebuilt as Freshsales workflows or handled through a dedicated Medicare-integrated tool.

Nookal custom properties on client, practitioner, or location records map to Freshsales custom fields on the corresponding object. FlitStack inspects Nookal's full property list and pre-creates matching custom fields in Freshsales (via API) before data loads. Field types are mapped: Nookal text to Freshsales text, Nookal date to Freshsales date, Nookal dropdown to Freshsales picklist with value-by-value mapping.

Nookal file attachments (clinical documents, referral letters, imaging files) linked to client records re-upload to Freshsales as Files attached to the Contact record. File size limits apply per Freshsales plan — FlitStack splits large file batches and retries failed uploads. Inline images in clinical notes are extracted and rehosted as separate file attachments.

Nookal staff records map to Freshsales Users for owner assignment. Active staff members are matched to Freshsales users by email. Nookal staff roles (admin, practitioner, receptionist) map to Freshsales roles and profiles, though sharing rules and permission sets must be configured manually in Freshsales after migration.

Nookal referral source data (referring practitioner, referral letter, external provider) migrates as a custom Referral_Source__c field on the Contact object. If referral data represents an external organization, it may map to a separate Account record linked via lookup relationship. Referral tracking workflows in Freshsales must be rebuilt manually.

Nookal waiting list entries do not have a direct Freshsales equivalent. FlitStack creates a Waiting_List__c custom module (or custom fields on the Contact) with fields for preferred appointment date, practitioner preference, service type, and waitlist status. As clients move off the waiting list into booked appointments, the status updates via Freshsales workflows that your admin rebuilds post-migration.