Migrate from CRM.io by 500apps to Salesforce Sales Cloud

CRM.io Contact records hold name, email, phone, company association, and tag fields. We assess each record against the customer's Lead versus Contact strategy during scoping. Records with a clear buyer-company association and active pipeline history map to Salesforce Contact attached to the matching Account. Records representing unqualified prospects map to Salesforce Lead. The original CRM.io contact record ID is preserved in a custom field crm_io_original_id__c for audit and cross-reference. Tags stored as comma-separated values in the CSV are expanded into a multi-select picklist in Salesforce.

CRM.io Lead records are standalone with name, source, status, and owner fields. They map directly to Salesforce Lead with LeadSource and Status preserved. The original CRM.io lead ID is held in crm_io_original_id__c. Any lead scoring values present in CRM.io custom fields migrate to a custom field lead_score__c in Salesforce. If the customer plans to convert Leads to Contacts at scale, we document the conversion workflow separately.

CRM.io Account records store business name, industry, size, and address fields. They map 1:1 to Salesforce Account. The Account object is migrated first in dependency order because every Contact requires an AccountId lookup. We use Account Name as the dedupe key and validate uniqueness before insert to prevent duplicate Accounts that would orphan Contact records.

CRM.io Deals carry stage, value, close date, owner, and associated Account. They map to Salesforce Opportunity with StageName, Amount, CloseDate, and OwnerId preserved. The Account-to-Deal link is reconstructed via a compound lookup key combining Account Name and Deal Name because there is no API to retrieve the internal CRM.io relationship ID. Pipeline stage order is inferred from the distribution of stage values across existing Deal records; we do not have access to a pipeline configuration API in CRM.io.

CRM.io pipeline stages are configurable within the UI but not retrievable via API. We infer the active stage set from Deal records at migration time, extracting all distinct stage values and their relative frequency. Each distinct stage becomes a Salesforce Opportunity Stage value, ordered by the inferred progression sequence. We configure a Salesforce Sales Process and Record Type to whitelist those stages per the customer's line-of-business split.

CRM.io Activities link to Contacts or Deals with type, subject, date, duration, and disposition fields. CSV exports may not preserve the parent record ID reliably. We reconstruct Activity-to-Contact associations using date matching and subject parsing as a fallback, and fall back to matching by Contact name and Account name where date-based matching is ambiguous. Calls migrate as Task with TaskSubtype=Call. Meetings migrate as Event. Tasks and emails migrate as Task records. The original Activity timestamp is preserved in ActivityDate for timeline ordering.

CRM.io Document Management stores file attachments associated with Contacts, Accounts, and Deals. CSV exports capture metadata only: filename, file type, and associated record ID. Binary files are handled as a separate bulk transfer via secure shared storage. We provide a mapping table linking CRM.io document metadata to Salesforce ContentDocument records attached to the parent Account, Contact, or Opportunity via ContentDocumentLink. The customer reviews and uploads actual files post-migration or approves a bulk binary transfer as a separate line item.

CRM.io assigns record ownership to Users within the platform. We map Owner names to Salesforce User records using a customer-supplied lookup table matching CRM.io owner email or name to the destination Salesforce User email or username. Owners without a matching Salesforce User are placed in a reconciliation queue for the customer's admin to provision before the relevant record phases proceed.

CRM.io stores tags as comma-separated values in Contact and Deal records. We parse the CSV field, expand each tag into individual values, and load them into Salesforce multi-select picklist fields on Contact and Opportunity. We agree on a naming convention and maximum picklist length with the customer during scoping because multi-select picklists have a 255-character limit per field value list.

CRM.io explicitly states Customization Possible: No. There are no documented custom fields, custom objects, or extended schemas to migrate. We confirm this during scoping by reviewing the CSV export column headers against the CRM.io standard field set. Any non-standard fields found in the export are flagged as potential data anomalies rather than intentional custom fields.

CRM.io supports email templates within the platform. Standard CSV export does not capture template content or markup. We do not migrate email templates. We document any templates observed in the CRM.io UI during scoping and provide the customer with a manual export checklist so the admin can retrieve templates from the CRM.io interface before the wind-down date.

Forecasting in CRM.io is a reporting view derived from Deals data. Historical forecast snapshots are not independently exportable. We recommend rebuilding forecasts in Salesforce using migrated Opportunity data as the source. We document the CRM.io forecast report structure (filters, groupings, date ranges) during scoping so the customer's admin can replicate the logic in Salesforce Reports and Forecasting.