Migrate from Ringy (formerly iSales) to Pipedrive

Ringy Leads contain both person-level fields (name, phone, email) and company-level fields (company name, address) in a single record. We split these at migration time: person fields map to Pipedrive Person, company fields map to Pipedrive Organization. The Organization is created first so that the org_id lookup is satisfied when Person records are inserted. We use the email domain from the Ringy Lead as a deduplication key across both objects.

Company data extracted from Ringy Lead rows maps to Pipedrive Organization. Field names in Ringy's CSV (company name, website, address fields) map to Pipedrive's Organization name, address fields, and custom properties. Organizations are inserted before Persons so that the lookup relationship is available at Person insert time.

Ringy Deals associated with Leads map to Pipedrive Deals. We extract pipeline names and stage definitions from Ringy as metadata and map them to Pipedrive pipeline and stage configuration. Deal value, stage, owner, and expected close date migrate directly. Ringy stage names are preserved as Pipedrive stage labels to maintain visual continuity for sales reps during the transition.

Ringy pipeline and stage configuration migrates as Pipedrive pipeline and stage setup. We extract the stage names and order from Ringy's configuration during scoping and create matching Pipedrive pipelines with corresponding stages. Stage probabilities are approximated to Pipedrive's supported integer range. The customer chooses whether to create separate Pipedrive pipelines per Ringy pipeline or consolidate into a single pipeline.

Activity history associated with Ringy Leads (calls, emails, SMS dispositions) migrates to Pipedrive Activity records. Call activities use activity_type=call, email activities use activity_type=email, and general logged activities use activity_type=task. We preserve the original timestamp and duration where available. Note that Ringy's full SMS message bodies may not appear in all CSV exports depending on how the record was structured.

Ringy custom fields on Leads are extracted by explicitly enabling the 'Include all custom fields' checkbox during CSV export scoping. We create matching custom fields in Pipedrive before migration using the same field types (text, number, date, picklist, etc.) as configured in the Ringy source. Pipedrive API v2 requires strict type compliance — we validate that numeric custom fields in Ringy do not contain string values before mapping to Pipedrive numeric custom fields.

Tags applied to Ringy Lead records are extracted from the CSV export where present. They map to Pipedrive Labels on the Person object. We flag any tag values that exceed Pipedrive's label length limits and truncate or split them as needed. If the customer's tagging taxonomy is complex (nested or multi-value per record), we document the tag strategy during scoping and apply it during migration.

Ringy Lead owners are resolved by matching the owner's email address against Pipedrive User records. We extract every distinct owner referenced on Leads and Deals during scoping and match against the destination Pipedrive org's User table. Owners without a matching Pipedrive User go to a reconciliation queue for the customer's admin to provision before record import proceeds.

File attachments associated with Ringy Leads or Companies have no documented export path in Ringy. We do not migrate attachments as part of standard scope. If the customer requires attachment migration, we document the affected record IDs and file locations during scoping and provide a separate file-transfer procedure outside the CRM migration scope.

Ringy drip campaigns, automated follow-up sequences, and automation rules cannot be exported as they are stored as platform-native automation objects with no documented export API. We document the visible campaign structure — names, stages, associated templates, and sequence order — as reference metadata for the customer's Pipedrive admin to use when rebuilding sequences in Pipedrive's automation builder.