CRM migration
Field-level mapping, validation, and rollback between Simple Sales Tracking and Pipedrive. We move data and schema; workflows are rebuilt natively in Pipedrive.
Simple Sales Tracking
Source
Pipedrive
Destination
Compatibility
9 of 12
objects map 1:1 between Simple Sales Tracking and Pipedrive.
Complexity
CModerate
Timeline
2-3 weeks
Overview
Moving from Simple Sales Tracking to Pipedrive is a structural upgrade for teams that have outgrown the entry-level CRM tier. Simple Sales Tracking provides Leads, Opportunities, Accounts, Contacts, Tasks, Notes, Appointments, and custom Sales Record fields at a flat $15/user/month with no bulk export API and no public rate limit documentation. Pipedrive starts at $14/user/month annually on the Lite plan and offers visual Kanban pipeline management, an activity-based selling methodology, a documented REST API, and a third-party migration partner (Import2) that the source platform does not match. We extract from Simple Sales Tracking via iterative paginated API polling because no bulk endpoint exists, we resolve custom field definitions by inspecting the platform UI during discovery, and we import into Pipedrive's Persons, Organizations, Deals, and Activities in dependency order with Owner resolution by email. Workflows, BCC Email automations, and the real-time Activity Feed do not migrate; we deliver a written inventory of these for the customer's admin to rebuild in Pipedrive's automation builder.
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 Pipedrive, 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
Contact
Pipedrive
Person
1:1Simple Sales Tracking Contacts map directly to Pipedrive Persons. Name, email, phone, and address fields map to the corresponding Pipedrive Person fields. We resolve the Contact-to-Account link from Simple Sales Tracking and attach the Person to the matching Organization in Pipedrive at import time. Any Contact without an associated Account in the source becomes an unlinked Person; we flag these in the reconciliation report.
Simple Sales Tracking
Account
Pipedrive
Organization
1:1Simple Sales Tracking Accounts map to Pipedrive Organizations. Account name, address, industry, and website fields map directly. Organization is created before any Person import so that the link between Person and Organization is satisfied at the moment of Person insert. We use Organization name as the dedupe key to avoid creating duplicate Organizations from repeated account data.
Simple Sales Tracking
Lead
Pipedrive
Lead
1:1Simple Sales Tracking Leads map to Pipedrive Leads. Lead status, source, owner assignment, and any custom Lead-level properties migrate directly. In Pipedrive, Leads and Deals share the same custom field structure, so any custom fields defined on Leads in Simple Sales Tracking map to Pipedrive custom fields that we pre-create on both object types before import.
Simple Sales Tracking
Opportunity
Pipedrive
Deal
1:1Simple Sales Tracking Opportunities map to Pipedrive Deals. Deal title, amount, expected close date, owner assignment, and stage map to the corresponding Pipedrive Deal fields. We resolve the Opportunity-to-Account link and set the Deal's Organization ID accordingly. Commission percentage or amount fields from Simple Sales Tracking's Commission Tracking feature migrate to custom Deal fields in Pipedrive if the destination plan supports them.
Simple Sales Tracking
Pipeline Stages
Pipedrive
Pipeline Stages
lossySimple Sales Tracking custom pipeline stages map to Pipedrive pipeline stages within the selected Pipeline. We capture the full stage sequence and probability percentages from the source and create matching Pipedrive stages with equivalent probability values. If the source has more stages than the default Pipedrive template, we create a custom pipeline in Pipedrive during the configuration phase before any Deal import begins.
Simple Sales Tracking
Task
Pipedrive
Task
1:1Simple Sales Tracking Tasks map to Pipedrive Tasks with due date, assignee, status, and title preserved. We resolve the assignee by email match against the User table and set the task's linked Person or Organization at import time. Simple Sales Tracking does not expose a full task status change history, so we migrate the current task state without historical transition logs.
Simple Sales Tracking
Appointment
Pipedrive
Activity (type: Meeting)
1:1Simple Sales Tracking Appointments map to Pipedrive Activities of type meeting. Title, date, time, duration, and linked Contact migrate directly. We resolve the Contact reference to the corresponding Person in Pipedrive and attach the Activity to that Person and any related Organization. Attendees beyond the primary Contact require manual re-assignment in Pipedrive post-migration.
Simple Sales Tracking
Note
Pipedrive
Note
1:1Simple Sales Tracking Notes migrate to Pipedrive Notes attached to the parent record (Person, Organization, or Deal). Note content and creation timestamp preserve; formatting beyond plain text (bold, italic, embedded images) may not carry over depending on the source export format. We attach each Note to its parent record via ContentDocumentLink at import time.
Simple Sales Tracking
Custom Sales Record Fields
Pipedrive
Custom Fields (Deal and Lead)
lossyCustom fields defined on Simple Sales Tracking's Sales Records require resolution without a schema API endpoint. During discovery we ask the customer for a screen capture of their custom field configuration page and cross-reference it against a sample API export to build the complete field map. We pre-create matching custom fields in Pipedrive on both Deal and Lead objects before migration, matching field type (text, number, date, dropdown) from the source definition.
Simple Sales Tracking
Files and Attachments
Pipedrive
Files
1:1Files attached to Contacts, Opportunities, and Notes in Simple Sales Tracking are exported as individual downloads from the 1 GB total storage allocation. We re-attach each file to its corresponding Person, Organization, or Deal in Pipedrive using Pipedrive's Files API. File size and count are constrained by the source's 1 GB ceiling, so we scope file migration during discovery to avoid discovering storage overrun mid-extraction.
Simple Sales Tracking
Lead Source
Pipedrive
Custom Field or Label
lossyLead sources in Simple Sales Tracking are a configurable reference taxonomy. We migrate source labels as values and map them to a Pipedrive custom field on Deal or Lead (type: set options) so that the customer's historical source data remains segmented in Pipedrive reporting. If Pipedrive's UTM tracking fields are active in the destination account, we may alternatively map sources to those fields based on the customer's preference during scoping.
Simple Sales Tracking
User
Pipedrive
User
1:1Simple Sales Tracking user records and permission levels migrate to Pipedrive Users by email match. Role naming conventions differ between the platforms, so we map Simple Sales Tracking permission levels to the closest applicable Pipedrive role (Admin, Manager, Regular Member) and flag any non-standard permission configurations in the handoff document for manual review.
| Simple Sales Tracking | Pipedrive | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Account | Organization1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Pipeline Stages | Pipeline Stageslossy | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Appointment | Activity (type: Meeting)1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Custom Sales Record Fields | Custom Fields (Deal and Lead)lossy | Mapping required | |
| Files and Attachments | Files1:1 | Mapping required | |
| Lead Source | Custom Field or Labellossy | Fully supported | |
| 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
Pipedrive gotchas
Custom field hash keys differ per account
Export access gated by visibility groups
Token-based API rate limits since December 2024
Sequences and Automations not exposed via REST API
Cost escalates via workflow caps and add-ons
Pair-specific challenges
Migration approach
Discovery and scope confirmation
We audit the source Simple Sales Tracking account for record counts (Contacts, Accounts, Opportunities, Leads, Tasks, Appointments, Notes), custom field definitions (via UI metadata), custom pipeline stage names, file attachment volume, and user count. We confirm the destination Pipedrive plan (Lite through Ultimate) and identify which add-ons (LeadBooster, Campaigns, Smart Docs) the customer has licensed or intends to license, since custom field creation and automation features vary by plan. We request a screen capture of the custom field configuration page and a record count estimate from the customer before the migration date is scheduled.
Custom field resolution and schema pre-creation
Using the UI metadata captured during discovery, we build the complete custom field map for Simple Sales Tracking's custom Sales Record fields. We then pre-create matching custom fields in Pipedrive on both Deal and Lead objects with the correct field type and option list before any data import begins. We also configure the pipeline and stage structure in Pipedrive to match the source's custom stage names and probability percentages.
Source extraction with checkpointing
We extract data from Simple Sales Tracking's REST API using paginated polling. Because no bulk export endpoint exists, we iterate through record pages and checkpoint our progress after each page fetch. We implement request pacing to avoid undocumented throttling and handle session timeouts by resuming from the last confirmed record. We extract files and attachments as individual downloads within the 1 GB storage ceiling and tag each file with its parent record reference for re-attachment in Pipedrive.
Owner and Organization pre-provisioning
We extract all distinct owner email addresses from Contacts, Accounts, Opportunities, and Tasks and match them against the Pipedrive User table. Any owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId references are required on most standard objects. We also ensure all Organizations exist in Pipedrive before Person import begins, because Person-to-Organization linking requires the Organization to already exist.
Production migration in dependency order
We run production migration in record-dependency order: Organizations (from Accounts), Persons (with OrganizationId resolved), Leads, Deals (with OrganizationId and OwnerId resolved, pipeline and stage assigned), Tasks, Activities, Notes, and Files (last, re-attached to their parent records). Each phase emits a row-count reconciliation report before the next phase begins. Custom fields are populated during the relevant object import using the pre-created field map.
Cutover, delta sync, and automation handoff
We freeze writes in Simple Sales Tracking during the cutover window, run a final delta migration of any records modified during the migration window, then set Pipedrive as the system of record. We deliver a written inventory of Simple Sales Tracking workflows, BCC Email automations, and daily reminder configurations that require manual rebuild in Pipedrive's automation builder. We support a one-week hypercare window for reconciliation issues. We do not rebuild automations inside the migration scope; that work is a separate engagement or an internal admin task.
Platform deep dives
Simple Sales Tracking
Source
Strengths
Weaknesses
Pipedrive
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 4 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Simple Sales Tracking and Pipedrive.
Object compatibility
4 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 Pipedrive migration scoping. Not seeing yours? Book a call.
Walk through your Simple Sales Tracking to Pipedrive 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 Pipedrive
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.