Migrate from coreplus to Zoho CRM

Core+ clients without a referring organization route to Zoho Lead. Clients associated with a Core+ organization (if applicable) or with an existing referrer link route to Zoho Contact linked to a Zoho Account. The split decision is based on whether the client has a referrer_type field populated — referring clients land as Contacts under the referrer's Account.

Core+ does not have a standalone organization object. If your Core+ data contains clinic or practice names as client groupings, we create Zoho Accounts from those groupings and attach associated clients as Contacts. The account name derives from the most-common practice name in the client record set.

Core+ practitioners map directly to Zoho Users. Email is the resolution key — each Core+ practitioner email must match a Zoho User email for owner assignment. Unmatched practitioners are flagged before migration; your Zoho admin provisions them as Users before the run. Profile and role assignment defaults to Standard CRM user unless otherwise specified.

Core+ appointments migrate as Zoho Events for the scheduled time block (with Start DateTime, End DateTime, and Duration preserved) and Zoho Tasks for the follow-up action items. The original practitioner owner maps to the Zoho User by email match. Service type becomes the Event description or a custom Service_Type__c field for reporting.

Core+ invoices with line items, service types, fees, and payment status migrate as Zoho Quotes (if you want them in the sales pipeline) or as records in a custom Invoice module built in Zoho Creator for non-sales invoice tracking. Payment status and amounts are preserved; the migration does not create Zoho Payments or accounting ledger entries.

Core+ referrers migrate as Zoho Contacts with a custom pick-list field Referrer_Type__c marking them as referral sources. Their contact details (name, email, phone, organization) map directly. Referrer-to-client associations are preserved as Zoho Activity records linking the referrer Contact to the referred client Contact.

Core+ service types (with fees and stock levels) migrate as records in a Zoho custom Service_Types module. If service types drive appointment categorization only, they can alternatively become a pick-list field on the Event/Task records. We configure this based on your Zoho configuration before the migration runs.

Core+ positions field (healthcare role or specialty designation) migrates as a custom pick-list field Positions__c on the Zoho Contact and Lead modules. Values are mapped one-to-one; any positions not present in Zoho are flagged for addition before import. The Positions__c pick-list is created during pre-migration schema configuration and validated against the Core+ export to ensure no values are dropped during transfer.

Core+ specialties field migrates as a custom multi-select pick-list Specialties__c on the Zoho Contact and Lead modules. Zoho's multi-select fields support up to 150 values; if your Core+ specialties exceed this, we collapse rarely-used values into an 'Other' bucket and flag the distinction.

Core+ client address fields (street, city, state, postal code, country) map to Zoho's standard address block on Contact and Account modules. The address is associated with whichever record the contact lands on (Lead or Contact) and linked to the Account if a practice-group Account was created. We verify each address component aligns with Zoho's field structure and confirm proper associations are established between Contact/Lead and Account records based on the organizational hierarchy in the source data.

Core+ file attachments associated with clients, appointments, or invoices are downloaded and re-uploaded to the corresponding Zoho record as Attachments. Zoho's per-file size limit is 25MB; files exceeding this are flagged for manual delivery. We verify attachment integrity by comparing file size and checksum post-upload. Inline images embedded in appointment notes are extracted and stored as separate file attachments on the Event record.

Core+ scheduling rules, notification automations, and appointment reminders do not have a Zoho equivalent that can be auto-migrated. We export your Core+ workflow definitions as a structured document referencing Zoho Blueprint, Functions, and Workflow Rules as the rebuild targets. Your Zoho admin uses this as a step-by-step reference.