Migrate from Smart CRM Online to Salesforce Sales Cloud

Smart CRM Online Company records map directly to Salesforce Account. The export produces a Company ID (used as dedupe key during import) and Company name. We import Accounts first so that the AccountId foreign key is available when Contacts are loaded. Any Company records that reference each other via a parent-company field in the export are flagged for Salesforce's Account Hierarchy configuration post-migration.

Smart CRM Online Contacts map to Salesforce Contact. The export carries Contact name, email, phone, and a Company name or ID string rather than a foreign key. We resolve the Company name string against the destination AccountId during transformation using the account dedupe key. If the export produces a Company ID reference that does not match a destination Account, we hold the Contact in a reconciliation queue for manual Account assignment before import resumes.

Smart CRM Online Deals map to Salesforce Opportunity. The export carries deal name, stage, value, close date, owner email, and a Company ID or Company name string. We resolve the Company reference to AccountId and the owner email to Salesforce OwnerId during the transform phase. Stage names from the export are mapped to Salesforce StageName values that we configure in the destination Sales Process before migration.

Smart CRM Online pipeline stages are configurable and export with the Deal record. We capture the full stage list and sequence from the discovery export, then configure Salesforce Opportunity Stages (StageName, Probability, and Closed flags) to match. If the customer has custom stage naming, we rename Salesforce stages to match during Salesforce Setup configuration before import.

Smart CRM Online supports custom fields per object but publishes no field schema. During discovery we request a full CSV export and cross-reference field names against the standard Smart CRM Online object template to identify custom properties. Each identified custom field is presented to the customer for explicit mapping to a Salesforce custom field (__c API name) or a note that the field will not migrate. Any unmapped custom fields are excluded from import and documented in the migration handoff.

Smart CRM Online activity logs (calls, emails, meetings) export with a parent reference to Contact name or Deal name. We resolve the parent reference to WhoId (Contact ID) and WhatId (Opportunity ID) during transformation. Calls land as Task with TaskSubtype=Call; meetings land as Event; emails land as EmailMessage linked to a Task. We load via Salesforce Bulk API 2.0 because volume typically exceeds CSV loader capacity. Activity timestamps are preserved as ActivityDate for timeline fidelity.

Smart CRM Online Notes export as a supplemental payload attached to Contact records, carrying the note body, author, and creation date. We extract Note records and import them as Salesforce Note objects, linking each via ContentDocumentLink to the parent Contact using the Contact's destination Salesforce ID resolved by email match.

Smart CRM Online exports Tags as a comma-separated or multi-value field on Contact or Deal records. We present two options to the customer during scoping: map tags to a Salesforce multi-select picklist field (preserving all tag values as picklist entries) or map them to Salesforce Topics with TopicAssignment records for content classification use cases.

Smart CRM Online exports owner information as an email address or user name on Contact, Company, and Deal records. We match owner email against the destination Salesforce org's User table. Any Owner without a matching Salesforce User is held in a reconciliation queue; the customer's admin provisions the missing User before record import resumes. Inactive Salesforce Users cannot own records in standard orgs, so we flag this constraint during scoping.

Smart CRM Online task engagements (completed tasks, to-dos) export with status, priority, due date, and owner email. We resolve the owner email to Salesforce OwnerId, set Task.Status and Task.Priority from the source values, and preserve the original due date as Task.ActivityDate. Tasks are loaded in the same Bulk API pass as other activity records.

Smart CRM Online deal monetary values export as a numeric field. We map this directly to Opportunity.Amount in Salesforce. If the source export produces values in a currency format that requires conversion, we apply the customer's specified exchange rate during transformation. CurrencyISOCode defaults to USD unless the customer specifies otherwise.

Smart CRM Online close date exports as a date field on the Deal record. We map this directly to Opportunity.CloseDate. Dates are validated for Salesforce date range constraints (records cannot have CloseDate before 1700 or after 4000) and reformatted to YYYY-MM-DD during the transform phase.