CRM migration
Field-level mapping, validation, and rollback between Simple Sales Tracking and Salesforce Sales Cloud. We move data and schema; workflows are rebuilt natively in Salesforce Sales Cloud.
Simple Sales Tracking
Source
Salesforce Sales Cloud
Destination
Compatibility
9 of 12
objects map 1:1 between Simple Sales Tracking and Salesforce Sales Cloud.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Simple Sales Tracking to Salesforce Sales Cloud is a structural upgrade, not a record copy. Simple Sales Tracking uses a flat object model with Leads, Opportunities, Accounts, and Contacts at a flat $15 per user with no tiered features; Salesforce introduces a multi-object hierarchy (Lead, Contact, Account, Opportunity, Task, Event) with advanced automation, unlimited pipelines, and a rich API ecosystem. The migration's primary technical challenge is Simple Sales Tracking's lack of a bulk export endpoint: we implement paginated API polling against its standard object endpoints with conservative request pacing and checkpoint recovery. Custom field definitions on Sales Records are not exposed via a schema endpoint, so we extract field names from UI metadata during discovery. We migrate the full appointment, task, and note history; the Activity Feed does not migrate because it is a real-time stream with no historical query API. Workflows, email sequences, and commission tracking configurations do not migrate; we deliver a written inventory for the customer's admin to rebuild in Salesforce Flow.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Simple Sales Tracking object lands in Salesforce Sales Cloud, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Simple Sales Tracking
Lead
Salesforce Sales Cloud
Lead
1:1Simple Sales Tracking Leads map directly to Salesforce Lead. The source Lead status field maps to Salesforce Lead Status; custom Lead-level properties migrate to custom Lead fields that we create during schema setup. We use the email address as the external ID for deduplication. If the customer has converted Leads in Simple Sales Tracking, we treat the converted records as Contacts in Salesforce with Account linkage and preserve the conversion timestamp in a custom field.
Simple Sales Tracking
Opportunity
Salesforce Sales Cloud
Opportunity
1:1Simple Sales Tracking Opportunities map to Salesforce Opportunity. The amount, expected close date, stage name, owner assignment, and linked Account reference migrate. Custom Opportunity-level properties migrate to custom Opportunity fields. Stage names from Simple Sales Tracking map to Salesforce Stage values within a Sales Process that we configure before migration. Commission percentage fields from Simple Sales Tracking migrate to a custom commission__c field on Opportunity.
Simple Sales Tracking
Account
Salesforce Sales Cloud
Account
1:1Simple Sales Tracking Accounts map to Salesforce Account. The Account name, billing and shipping address, industry tag, phone, website, and any custom Account-level fields migrate. Account is created before Contact import so that AccountId is resolved at the moment of Contact insert. We use Account name as the dedupe key during import.
Simple Sales Tracking
Contact
Salesforce Sales Cloud
Contact
1:1Simple Sales Tracking Contacts map to Salesforce Contact. Name, email, phone, title, address, and any custom Contact-level properties migrate. Contact-to-Account linking is resolved explicitly during import by matching the Simple Sales Tracking Contact's associated Account reference to the migrated Account record. Records without a matching Account are held in a reconciliation queue.
Simple Sales Tracking
Custom Sales Record Fields
Salesforce Sales Cloud
Custom Fields (Account, Contact, Opportunity)
lossySimple Sales Tracking does not expose a schema API endpoint for custom field definitions. We extract custom field names, types, and picklist values from the platform's UI during discovery (asking the customer to provide a screen capture of their custom field configuration page) and cross-reference against a sample API response. Each custom field is then provisioned in Salesforce as a custom field on the appropriate standard object before migration, preserving data type fidelity.
Simple Sales Tracking
Custom Pipeline Stages
Salesforce Sales Cloud
Sales Process + Stage Values
lossySimple Sales Tracking allows custom stage names and reordering within a single pipeline. We capture the full stage sequence during discovery and create a Salesforce Sales Process that whitelists each named stage as a Stage value. Probability percentages from Simple Sales Tracking migrate to StageProbability on each stage. If the customer uses multiple named pipelines in Simple Sales Tracking, we map them to Salesforce Record Types on Opportunity.
Simple Sales Tracking
Appointment
Salesforce Sales Cloud
Event
1:1Simple Sales Tracking Appointments map to Salesforce Event. StartDateTime, EndDateTime, Subject, Location, and description migrate. The linked Contact reference resolves to the Salesforce Contact record via email matching. Owner assignment migrates by resolving the Simple Sales Tracking owner email to the Salesforce User. EventRelation records are created to link attendees to the Event.
Simple Sales Tracking
Task
Salesforce Sales Cloud
Task
1:1Simple Sales Tracking Tasks map to Salesforce Task with Status, Priority, Subject, ActivityDate, and description preserved. Task assignment migrates by resolving the Simple Sales Tracking owner email to the Salesforce OwnerId. Simple Sales Tracking does not store a full activity log of status changes, so the task history reflects the final state at time of migration rather than a timeline of changes.
Simple Sales Tracking
Note
Salesforce Sales Cloud
Note
1:1Simple Sales Tracking Notes map to Salesforce Note records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, or Opportunity). Note body migrates as plain text. We do not guarantee retention of formatting or embedded file links; any formatting-dependent notes are flagged for manual review post-migration.
Simple Sales Tracking
Lead Source
Salesforce Sales Cloud
Lead Source Picklist
lossyLead Sources in Simple Sales Tracking are a configurable reference taxonomy. We migrate the source labels and associate them with the corresponding Lead records. In Salesforce, the Lead Source values are added to the standard Lead Source picklist before migration so that the imported values are valid picklist entries rather than free text.
Simple Sales Tracking
Files and Attachments
Salesforce Sales Cloud
ContentDocument + ContentVersion
1:1Simple Sales Tracking provides 1 GB of total uploaded file storage. We export files attached to Contacts, Opportunities, and Notes as individual downloads and re-attach them in Salesforce as ContentVersion records linked via ContentDocumentLink to the parent record. File size is constrained by Simple Sales Tracking's storage ceiling; large attachment sets may require the customer to clean up or archive files before migration.
Simple Sales Tracking
User
Salesforce Sales Cloud
User
1:1Simple Sales Tracking multi-level user permissions and owner assignments map to Salesforce User records. We resolve owners by email match against the destination Salesforce org's User table. Any Simple Sales Tracking user without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Role naming conventions differ, so we map to the closest applicable Salesforce profile and territory.
| Simple Sales Tracking | Salesforce Sales Cloud | Compatibility | |
|---|---|---|---|
| Lead | Lead1:1 | Fully supported | |
| Opportunity | Opportunity1:1 | Fully supported | |
| Account | Account1:1 | Fully supported | |
| Contact | Contact1:1 | Fully supported | |
| Custom Sales Record Fields | Custom Fields (Account, Contact, Opportunity)lossy | Mapping required | |
| Custom Pipeline Stages | Sales Process + Stage Valueslossy | Mapping required | |
| Appointment | Event1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Lead Source | Lead Source Picklistlossy | Fully supported | |
| Files and Attachments | ContentDocument + ContentVersion1:1 | Mapping required | |
| User | User1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Simple Sales Tracking gotchas
Trial import ceiling of 50 records masks true data volume
No public bulk export API requires iterative extraction
Custom field definitions are not exposed via a schema endpoint
Activity Feed is a real-time stream with no historical query API
Salesforce Sales Cloud gotchas
Workflow Rules and Process Builder are retired
Bulk API batch quota exhaustion during large imports
Storage overage billing is non-obvious
Account-Contact many-to-many relationship mapping
Territory and team member import ordering dependencies
Pair-specific challenges
Migration approach
Discovery and data-volume assessment
We audit the Simple Sales Tracking account via API polling to confirm record counts across Leads, Opportunities, Accounts, Contacts, Appointments, Tasks, and Notes. We ask the customer to provide a screen capture of their custom field configuration page and their custom pipeline stage names. We assess file attachment volume against the 1 GB storage ceiling and flag any customer whose dataset includes records approaching the trial import ceiling. We pair this with a Salesforce edition review: Starter ($25/user) covers basic Lead-Contact-Opportunity migration; Professional ($100/user) is required for Sales Processes, multiple Record Types, and Flow; Enterprise ($165/user) is needed for advanced territory management, forecasting, and quota management. The discovery output is a written migration scope and a Salesforce edition recommendation.
Custom field and pipeline schema discovery
Because Simple Sales Tracking has no schema API endpoint, we extract custom field definitions from the platform's UI during discovery. We ask the customer to provide a screen capture of their Sales Record custom field configuration and their pipeline stage definitions. We cross-reference this against a sample API response to identify any fields not visible in the UI but present in the API payload. We then provision the corresponding custom fields in Salesforce on the appropriate standard objects (Account, Contact, Opportunity) before any data migration begins. Pipeline stage names from Simple Sales Tracking become Salesforce Stage values within a Sales Process that we configure in the destination org.
Sandbox migration and reconciliation
We run a full migration into a Salesforce Sandbox (Developer or Full Copy depending on data volume) using production-like record counts. The customer's Salesforce admin reconciles record counts against the Simple Sales Tracking source, spot-checks 25-50 random records for field-level accuracy, and validates that Account-Contact linking is intact. Any mapping corrections for custom fields, stage name misspellings, or picklist value mismatches happen here before production migration begins. We do not proceed to production until the sandbox sign-off is received.
Owner reconciliation and User provisioning
We extract every distinct owner referenced on Leads, Opportunities, Accounts, Contacts, and Appointments and match by email against the Salesforce destination org's User table. Owners without a matching Salesforce User are held in a reconciliation queue. The customer's Salesforce admin provisions any missing Users (active or inactive depending on whether the original Simple Sales Tracking user is still active). Migration cannot proceed past this step because OwnerId references are required on Opportunity, Task, Event, and Note records.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Simple Sales Tracking Accounts), Contacts (with AccountId resolved), Leads (with lead source picklist values validated), Opportunities (with AccountId, OwnerId, and stage name validated against the Sales Process), Products and Pricebook entries (if Opportunity Products are used), Appointments (as Event records with Contact linking), Tasks, Notes, and Files (as ContentVersion with ContentDocumentLink). Each phase emits a row-count reconciliation report before the next phase begins. We use the Salesforce REST API for standard record inserts and the Bulk API 2.0 for high-volume phases (Tasks, Notes, Events) with batch chunking and exponential backoff.
Cutover, validation, and automation handoff
We freeze Simple Sales Tracking writes during the final cutover window, run a delta migration of any records modified during the migration, then enable Salesforce as the system of record. We deliver a written inventory of Simple Sales Tracking workflows (daily reminders, BCC email rules), commission tracking configurations, and custom field dependencies requiring rebuild in Salesforce Flow or custom fields. We support a one-week hypercare window where we resolve reconciliation issues raised by the customer's team. We do not rebuild automations or commission structures inside the migration scope; those are separate engagements or internal admin tasks.
Platform deep dives
Simple Sales Tracking
Source
Strengths
Weaknesses
Salesforce Sales Cloud
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Simple Sales Tracking and Salesforce Sales Cloud.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Simple Sales Tracking: Not publicly documented.
Data volume sensitivity
Simple Sales Tracking doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Simple Sales Tracking to Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.
Walk through your Simple Sales Tracking to Salesforce Sales Cloud migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Simple Sales Tracking
Other ways to arrive at Salesforce Sales Cloud
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.