Migrate from coreplus to Freshsales

Coreplus clients with a person name map to Freshsales Contact; clients with a business name map to Freshsales Account. The primary company association from Coreplus creates an AccountId lookup on the contact record. Multi-contact households in Coreplus collapse to one contact with household details stored in a custom field.

Coreplus practitioners map to Freshsales users via email matching. This is the most migration-specific gotcha: Freshsales requires every user to have a valid email, but Coreplus practitioners may not. We flag all practitioners without email addresses before migration and ask your team to add emails or designate fallback Freshsales users for each unresolved practitioner record.

Coreplus appointments with a duration of one day or less map to Freshsales Event records with the original start and end times preserved. Multi-day or all-day appointments in Coreplus split into separate Freshsales task records, one per day, with the full appointment description and service type preserved in the task Notes field. Practitioner assignments resolve to Freshsales user IDs via the email-matching step.

Coreplus referrers map directly to Freshsales Account records. The referrer name becomes the Account Name; referral type maps to Industry or a custom pick-list field. Referral-specific notes become Account Description. Referrer contact details map to Account phone and email fields if present in the Coreplus record.

Freshsales has no native invoice object. We create a custom text field (Invoice_Reference__c) on the Contact record and populate it with the Coreplus invoice ID and basic billing reference. The full invoice line-item data is exported as a CSV and linked from the contact record for post-migration reference.

Coreplus service types with associated fees map to Freshsales Product records. Fee amounts map to Product unit_price; service type name maps to Product name. Active and archived status is preserved. If service types are used purely as categorization labels without pricing, they map to a custom pick-list field on the appointment task or event instead.

Any custom fields added to the Coreplus client record are exported via the REST API and recreated as Freshsales custom fields on the Contact object before migration. Custom field data types (text, number, pick-list, date, checkbox) are matched to the equivalent Freshsales field type. Pick-list custom fields require value-by-value mapping if the allowed values differ between platforms.

Custom practitioner fields in Coreplus are mapped to custom fields on Freshsales User records or on contact records where practitioner context is stored. If the practitioner field captures credentials or specializations relevant to client records, we store it on both the User and as a custom contact field for visibility on the client side.

Coreplus does not support attachment import and Freshsales standard CSV import does not handle files. We document all attachment URLs and file types referenced in appointment notes so your team can re-upload via Freshsales Files after migration. This is scoped separately from the standard migration price.

Coreplus appointment location data (clinic room, telehealth link, client address) has no equivalent native field in Freshsales tasks or events. We create an Appointment_Location__c custom text field on the Task object and populate it from the Coreplus location field. Virtual appointment links are stored in the same field.

Freshsales sets CreatedDate at migration time, overwriting any historical timestamp. We preserve the original Coreplus created_date as a custom datetime field (Original_Create_Date__c) on every contact, account, and task record so reporting reflects the true record history from the source system.

The Coreplus unique record ID is stored in a custom text field (Source_System_ID__c) on every migrated record — contacts, accounts, tasks, and events. This enables delta-run de-duplication if the migration runs more than once and provides a traceability link back to the source record for audit purposes.