Migrate from Ringy (formerly iSales) to Microsoft Dynamics 365 Sales

Discovery and scoping

We audit the Ringy portal for Lead volume, custom field count, pipeline and stage names, deal history, activity attachment count, and any known auto-block keyword lists. We confirm the customer's Microsoft Dynamics 365 tenant status (existing tenant or new provisioning) and the target edition (Sales Professional at $65/user/mo or Sales Enterprise at $95/user/mo). We establish the current billing baseline in Ringy, verify no outstanding usage overages exist, and confirm the customer's acceptance that call recordings, SMS threads, drip campaigns, and attachments cannot be migrated.

CSV extraction with custom field audit

We guide the customer through the Ringy Lead CSV export with the 'Include all custom fields' checkbox selected. For datasets exceeding 5,000 records, we split the export by date range or record status to avoid browser timeout. We cross-reference the exported column headers against the customer's confirmed field inventory to ensure all custom properties are captured. We review the auto-block keyword list and flag any records that may have been silently filtered.

Dynamics 365 schema design and pipeline configuration

We design the destination schema in Microsoft Dynamics 365 Sales . This includes configuring the Lead-to-Contact-to-Account entity model, creating custom fields to receive Ringy custom properties, defining Opportunity pipeline stages and sales processes, and setting up security roles. Schema is validated in a Dynamics 365 Sandbox environment before any production migration begins. We map Ringy pipeline stage names to Dynamics stage values with appropriate probability percentages.

Transform and split at migration time

We split the Ringy Lead CSV into three target objects: Dynamics 365 Account (company-level fields), Dynamics 365 Contact (individual-level fields where a Contact is warranted), and Dynamics 365 Lead (for records not yet ready for conversion). We apply the custom field mapping, normalize field types for Dynamics compatibility, and prepare the import packages in CSV format for the Dynamics Data Import Wizard or KingswaySoft/SSIS-based import.

Sandbox migration and reconciliation

We run a full migration into the Dynamics 365 Sandbox using production-like data volume. The customer's Dynamics administrator reconciles record counts (Leads in, Contacts in, Accounts in, Opportunities in), spot-checks 25-50 random records against the Ringy source export, and validates that pipeline stages and custom field values match expectations. Any mapping corrections happen here, not in production.

Production migration and automation inventory delivery

We run production migration in dependency order: Accounts first (for lookup resolution), then Contacts, then Leads, then Opportunities. Activities migrate last using the Dynamics Data Import Wizard or bulk API path available in the target tenant. We freeze Ringy writes during cutover and run a final delta migration of any records modified during the window. We deliver the Ringy drip campaign and automation inventory document to the customer's admin team for rebuild in Power Automate or Dynamics Sales Automation. We do not rebuild Ringy automation logic inside the migration scope.