Migrate from RSoft CRM to Zoho CRM

RSoft Company records map directly to Zoho CRM Account. We extract company name, industry, size, address, and owner from the RSoft CSV export and map them to the corresponding Zoho Account fields. The Account is created before any Contact import so that the Account lookup relationship is satisfied at the moment of Contact insert. Any RSoft Company with no address data is flagged as incomplete and flagged for manual enrichment before import.

RSoft Contact records map to Zoho Contacts with name, phone, email, address, lifecycle stage, and owner transferred as standard fields. Custom contact properties above the 5-field limit on RSoft's Standard or Advanced plan require remapping to Zoho custom fields, which we pre-create during schema design. Contact-to-Account linkage is resolved via email domain match or explicit Account_ID field in the RSoft export.

RSoft Leads captured via web forms, WhatsApp, and manual entry map to Zoho Leads with lead source, status, score, assigned owner, and associated activities transferred. RSoft's Lead-to-Contact conversion record is preserved as a Zoho Lead custom field for audit. Unconverted Leads import as Zoho Leads; Leads already converted in RSoft import as Zoho Contacts attached to the corresponding Account.

RSoft Deals map to Zoho Deals with pipeline stage, amount, probability, expected close date, and owner transferred. We extract the pipeline name and stage label explicitly from the RSoft export and map them to Zoho's pipeline and stage configuration before import, ensuring that the stage exists in Zoho and has the correct probability percentage assigned.

RSoft allows custom stage names and reorderable stages per pipeline. We extract the stage name, position, and probability from RSoft and configure matching Zoho pipeline stages before Deal import begins. Stage-specific automation triggers from RSoft are documented separately as a Zoho Blueprint inventory item rather than migrated as live automation.

RSoft Activities (calls, emails, SMS, notes logged against Contacts, Leads, or Deals) map to Zoho Tasks. We map the activity type, subject, description, date, and owner. RSoft call logs from IVR and autodialer are stored separately and do not appear in the standard CSV export; these are flagged as a separate file-transfer scope for the customer's admin to handle manually after migration.

RSoft Ticket records (processed from email, online, phone, chat, and social media) map to Zoho Cases. We map ticket subject, status, priority, assignee, and description. Custom ticket fields are limited by RSoft's plan tier; any custom fields beyond the 5-field limit are created as Zoho custom fields and mapped explicitly to prevent silent data loss during import.

Tags on RSoft Contacts, Leads, and Deals export via CSV and map directly as Tags in Zoho CRM. We deduplicate tags during import to avoid duplicate tag entries. If a tag in RSoft contains characters that Zoho does not support in tag names, we sanitize the tag name and document the original-to-sanitized mapping for the customer's reference.

RSoft Standard and Advanced plans cap custom fields at 5 per object, which we audit during discovery. Any migrated record with custom field data that exceeds the RSoft plan limit has those fields pre-created as Zoho custom fields before import. We validate the field data type (text, number, date, picklist) against Zoho's field types and reject any mapping that would result in type coercion data loss.

RSoft user accounts map to Owner fields on Deals, Contacts, Leads, and Tickets. We extract the full user roster from RSoft and match by email address against the Zoho destination's User table. Owners without a matching Zoho User go to a reconciliation queue for the customer's admin to provision before record import resumes. Orphaned owner references are flagged as a separate data-quality issue in the migration report.