Migrate from Ringy (formerly iSales) to HighLevel

Ringy Leads are the primary record object and the only object with a documented CSV export path. We extract via the UI-based 'Generate CSV' function with 'Include all custom fields' checked. The CSV maps to GoHighLevel Contact records with FirstName, LastName, Phone, Email, and address fields preserved. Custom properties on the Lead migrate to GoHighLevel Contact custom fields, which we provision in the destination account before import. The export filter should capture all non-auto-blocked Leads; we audit the auto-block keyword list during scoping to identify any records that may have been silently excluded.

Ringy exports Contacts through the same Lead CSV workflow rather than a separate object path. Contact-level fields (name, phone, email, custom properties) appear in the same export rows as Leads. We deduplicate by email during transform to avoid double-importing records that exist as both Lead and Contact types in Ringy, and we preserve the original Ringy record type as a custom field ringy_record_type__c for reconciliation.

Ringy Company records appear in the Lead export via filtering rather than a dedicated export path. Company name, address, and any associated custom properties migrate to GoHighLevel Company records. We normalize company data from Lead rows where the company field is populated and create a Company record before importing the associated Contact so that the Contact-to-Company relationship is satisfied at insert time.

Ringy Deals are associated with Leads and included in CSV exports via filtering. Deal name, amount, stage, close date, and pipeline assignment transfer to GoHighLevel Pipeline Deals. Pipeline names and stage labels from Ringy are preserved as metadata and mapped to GoHighLevel Pipeline and Stage configurations, which we provision in the destination account before Deal import begins.

Call history appears as associated history within Ringy Lead rows and in the CRM activity log, but there is no dedicated call log export or bulk download for call recordings or detailed call metadata. We extract any call disposition data, timestamps, and duration values that surface in the Lead CSV and migrate them as GoHighLevel Contact notes with a call__c type flag. Call recordings do not migrate from Ringy. We flag this limitation in the migration scope and document it for the customer.

Email and SMS engagement history that appears in the Ringy Lead activity timeline migrates as GoHighLevel Contact notes. There is no bulk export for email thread bodies or SMS message content from Ringy. We extract the engagement type, timestamp, and any available disposition from the Lead CSV where present and flag the limitation of message-body migration in the scope document.

Tags applied to Ringy records appear in the Lead CSV export depending on how the record was structured. There is no dedicated tag export path. We extract tag values from Lead CSV rows where present and migrate them as GoHighLevel Contact tags. Tags serve as segmentation markers in both platforms, though the UI for tag management differs.

Custom fields on Ringy Leads must be explicitly included via the 'Include all custom fields' checkbox during CSV export. We verify this option was selected during extraction scoping and flag any custom fields that do not appear in the exported dataset. Custom properties migrate to GoHighLevel Contact custom fields, which we provision before import using the custom field name as a label and inferring field type from the data format in the CSV.

Ringy drip campaigns and automation sequences are platform-native automation objects with no documented export API. Campaign names, stage labels, associated templates, and sequence order are documented as reference metadata during scoping, but the automation logic itself cannot be extracted. We deliver a written campaign inventory to the customer's admin for rebuild in GoHighLevel's Automation builder, which uses a trigger-and-action workflow model different from Ringy's sequence-based drip engine.