Migrate from Ringy (formerly iSales) to HubSpot

Ringy combines Leads and Contacts in one object. All records map to HubSpot Contacts by default. If your team uses HubSpot's separate Lead object, we can split records by Ringy's lead_status field — records with status 'New' or 'Contacted' route to HubSpot Leads, established records route to Contacts.

Direct 1:1 mapping. Ringy companies export with name, domain, address, and industry. HubSpot Company properties accept these directly. Ringy's parent-child company hierarchy maps to HubSpot's parent company association field if your Ringy instance uses it. We also validate that each company record includes a unique identifier for matching.

Ringy deals map to HubSpot Deals. Each deal carries deal name, amount, stage, close date, and owner. Ringy pipeline stages map to HubSpot pipeline stage values via value mapping. Stage probability is set per pipeline stage in HubSpot after migration.

Ringy pipelines become HubSpot Pipelines. HubSpot allows multiple pipelines per CRM instance — Sales Starter supports 5, Professional 15, Enterprise 50. We create the matching pipeline structure in HubSpot before migrating deal records so foreign keys resolve correctly and set stage probability percentages for accurate forecasting.

Ringy call logs export as Tasks with type='Call'. We transform these to HubSpot's native Call object, mapping Ringy's call duration, disposition, and recording URL (if available) to HubSpot's call_duration_milliseconds, call_disposition, and associated custom properties. This transformation also preserves call outcome and ensures the activity timeline reflects the original interaction details.

Ringy SMS history has no native HubSpot equivalent — HubSpot SMS lives in the Conversations inbox, not as a structured CRM property. We preserve SMS logs (direction, timestamp, content snippet) as a custom property on each Contact record, with the full thread reference stored as JSON.

Ringy general tasks (follow-ups, to-dos) map to HubSpot Tasks. Subject, body, due date, and completion status transfer directly. Owner resolution happens via email match against HubSpot user accounts. We also handle task priority mapping and ensure recurring tasks are recreated with the same recurrence pattern in HubSpot.

Ringy email logs map to HubSpot Emails. Subject, body, timestamp, and recipient are preserved. HubSpot links emails to Contact records automatically via email address matching. We also map email thread identifiers and preserve any attachments as file links in the contact's record for complete historical reference.

Ringy notes export with body, associated record, and timestamp. We map these to HubSpot Notes linked to the corresponding Contact, Company, or Deal. Note associations are preserved so context isn't lost. We also retain note author information and any tags or categories for downstream filtering and reporting.

Ringy custom fields require pre-creation in HubSpot (Settings > Properties > Create property). We audit your Ringy custom field list during discovery, generate the HubSpot property creation plan, and apply it before the migration run so all custom data lands in the correct fields.

Ringy drip campaigns and automations do not export in a format compatible with HubSpot Workflows. FlitStack exports campaign definitions (trigger conditions, step delays, message content) as a JSON reference document your HubSpot admin uses to rebuild in HubSpot's Workflow tool.

Ringy users export with name, email, and role. We match Ringy user emails against existing HubSpot user accounts. Unmatched users are flagged — your HubSpot admin either creates accounts before migration or assigns records to a fallback HubSpot owner. This ensures all records have a designated owner in HubSpot after migration.