Migrate from noCRM.io to Salesforce Sales Cloud

noCRM Lead records require a split in Salesforce. Leads with a company name that implies an existing business relationship map to Salesforce Contact attached to a new or matched Account. Unqualified prospects with no established company context remain as Salesforce Lead. We apply the split rule at migration time using noCRM's status field (Won, Lost, To-Do, Standby) and the presence of a company name field. The original noCRM Lead status is preserved in a custom field nocrm_original_status__c on both Lead and Contact for audit and reporting continuity.

Each noCRM Pipeline Step becomes a Salesforce Opportunity StageName value. We map the step order, probability, and status type (Open, Won, Lost) from noCRM to the corresponding Salesforce Stage properties. If the source account uses multiple Pipelines (Expert or Dream), each Pipeline becomes a Salesforce Record Type with its own Sales Process that whitelists only its relevant stage values.

noCRM Pipelines map to Salesforce Record Types on Opportunity. Starter accounts limited to one Pipeline map to a single Opportunity Record Type. Expert and Dream accounts with multiple Pipelines map to multiple Record Types, each with a corresponding Sales Process that scopes stage values per pipeline.

noCRM does not have a separate Account object. The company name stored on each Lead becomes a Salesforce Account during migration. We create an Account record for each distinct company name in the Lead export, then link the converted Contact (from the Lead split) to that Account via AccountId. Duplicate company names are deduplicated at Account creation so one Account parent has multiple Contact children where appropriate.

noCRM tags are freeform labels applied to Leads. We preserve all tags and map them to a Salesforce multi-select picklist field on Lead and Contact. If the number of unique tags exceeds the Salesforce multi-select picklist limit of 500 values, we map them to a custom text field with semicolon-delimited values. Tag strategy is confirmed with the customer during scoping.

noCRM Prospecting Lists group Leads for outbound campaigns and reporting. We create a Salesforce Campaign per Prospecting List, add all Lead and Contact records from that list as Campaign Members, and preserve the list creation date and owner. Prospecting List statistics (lead count, response rate if available) are stored as Campaign custom fields.

noCRM stores a chronological activity log per Lead capturing comments, status changes, step transitions, and manual entries. We migrate each activity log entry as a Salesforce Task record linked to the parent Lead or Contact. The original timestamp, activity type (comment, status change, step transition), and author are preserved. Large comment histories are chunked and loaded via Bulk API to avoid governor limits.

noCRM Users assigned to Leads map to Salesforce User records by email match. Role and permission structures do not transfer directly and must be reconfigured in Salesforce Profile and Permission Set assignments post-migration. Inactive noCRM users are mapped to inactive Salesforce users so historical assignment is preserved without creating active license consumption.

noCRM Predefined Fields are custom lead fields configured under Admin > Sales process > Predefined Fields. These vary per account and may include text, number, date, checkbox, or dropdown types. We extract the field definitions from noCRM's admin export, create equivalent Salesforce custom fields (with __c API suffix) of matching types, and map the field values during Lead import. Field-level security is set to editable for the migration user during import and adjusted post-migration.

noCRM Custom Actions are menu items on lead cards that trigger account-specific workflows (e.g., adding won leads to an invoicing system). These have no standard schema and do not export cleanly. We document each Custom Action's name, trigger context, and destination URL or API call as part of the migration scope. The customer's admin or a Salesforce developer rebuilds equivalent functionality as a Salesforce custom button, Quick Action, or Flow.

Files attached to noCRM Leads export as binary blobs alongside the lead record. We preserve the original file name and attachment reference, upload each file as a Salesforce ContentDocument, and link it via ContentDocumentLink to the parent Lead or Contact record. File metadata (upload date, uploader) migrates as ContentVersion fields.

noCRM Statistics exports cover company performance, team activity, forecasts, and lead performance per Prospecting List. These aggregate metrics do not have a direct Salesforce equivalent. We export the statistics as structured JSON, store them as Salesforce Report custom fields or custom report types, and deliver the structure as a read-only reporting layer that the customer's admin can include in dashboards. Individual metric rebuild is out of scope; the raw data is preserved for manual reconstruction.