Migrate from RSoft CRM to HighLevel

RSoft Contacts map directly to GoHighLevel Contacts. We extract name, phone, email, address, lifecycle stage, tags, and owner email from the RSoft CSV export. Custom contact properties above the 5-field tier limit on RSoft Standard or Advanced are flagged during scoping. We map each RSoft Contact owner email to the corresponding GoHighLevel User by email lookup. RSoft's lead_status and lead_score properties migrate as GoHighLevel Contact custom fields.

RSoft Leads are sourced from web forms, WhatsApp, and manual entry. RSoft's Lead-to-Contact conversion record preserves the conversion timestamp. We import all Leads into GoHighLevel as Contacts with a custom field rsoft_lead_type__c set to true and the original lead source recorded. This preserves the distinction between converted and unqualified leads without needing GoHighLevel's separate Lead object (which is available but less commonly used by SMB teams in GoHighLevel).

RSoft Company records hold organization data linked to multiple Contacts. GoHighLevel uses an Organization field on the Contact record to represent the company. We extract company name, industry, size, address, and owner and map them to the Contact's Organization field. Company-to-Contact relationships are preserved by extracting the RSoft company_id from the Contact CSV row and resolving it to the Organization field in GoHighLevel.

RSoft Deals map to GoHighLevel Opportunities. We extract pipeline stage, amount, probability, expected close date, and owner email. RSoft uses a drag-and-drop pipeline builder and allows multiple pipelines; we map each RSoft pipeline name to a GoHighLevel pipeline with matching stage labels and probabilities. Deal owner email resolves to GoHighLevel User by email lookup.

RSoft custom stage names and reorderable stages per pipeline map to GoHighLevel Pipeline stages with matching names and probability percentages. Stage-specific automation triggers from RSoft are flagged in the workflow inventory document since automation rules do not migrate. Probability values migrate to the GoHighLevel stage probability field.

RSoft Activities logged against Contacts, Leads, or Deals migrate to GoHighLevel Activities (calls, emails, SMS, notes) linked by Contact name or Opportunity name lookup. The parent record reference is resolved at migration time using the Contact or Opportunity name as the dedupe key. IVR call logs stored in RSoft-specific modules are not included in the standard CSV export; we flag this gap and transfer call recording metadata as a separate file deliverable.

RSoft Tickets from the Ticket Management module (sourced from email, online, phone, chat, and social media) map to GoHighLevel Tickets. We map ticket subject, status, priority, assignee, and conversation thread. Custom ticket fields are limited by RSoft plan tier and are flagged for GoHighLevel custom field creation before import.

Tags on RSoft Contacts, Leads, and Deals export via CSV and map as GoHighLevel Tags. We deduplicate tags during import. Tags used for pipeline stage marking in RSoft are preserved as GoHighLevel Tags and can be used in automation triggers post-migration.

RSoft user accounts map to Owner fields on Deals, Contacts, Leads, and Tickets. We extract the full user roster from RSoft and map each to a GoHighLevel User by email address. Orphaned owner references (RSoft users without a corresponding GoHighLevel User) are flagged in a reconciliation report for the customer's admin to provision before record import resumes.