CRM migration
Field-level mapping, validation, and rollback between Simple Sales Tracking and HubSpot. We move data and schema; workflows are rebuilt natively in HubSpot.
Simple Sales Tracking
Source
HubSpot
Destination
Compatibility
11 of 11
objects map 1:1 between Simple Sales Tracking and HubSpot.
Complexity
BStandard
Timeline
48–72 hours
Overview
Simple Sales Tracking organizes sales data around Leads, Opportunities, and Accounts — a straightforward model suited to small teams tracking pipeline without heavy customization. HubSpot CRM uses Contacts, Companies, and Deals, with an additional lifecycle_stage property that tracks how prospects move from subscriber through customer. The two platforms share core object equivalents (Account ≈ Company, Contact ≈ Person, Opportunity ≈ Deal), but the field naming conventions differ and HubSpot adds its own required properties. We map Simple Sales Tracking's custom sales record fields into HubSpot custom properties, translate lead sources to HubSpot's standard list, and preserve deal stages as HubSpot deal pipeline stages. Commission tracking — a Simple Sales Tracking feature — has no direct HubSpot equivalent; we migrate commission data as a custom number field and recommend rebuilding commission calculations in HubSpot's native tools or a connected app. Workflows and automations do not migrate; these must be rebuilt in HubSpot's workflow builder after the data lands. The migration runs via HubSpot's native import API with batch processing to handle volumes efficiently, followed by a delta-pickup window to capture any records modified during cutover.
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 HubSpot, 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 (Person)
HubSpot
Contact
1:1Simple Sales Tracking stores persons as Contacts with name, email, phone, and address fields. HubSpot Contact is the direct equivalent. Email address is the primary lookup key for owner resolution during migration. We also map the original contact creation timestamp to a custom property to retain historical context. Additionally, any phone number formatting differences are normalized before import to ensure consistency across records.
Simple Sales Tracking
Account
HubSpot
Company
1:1Simple Sales Tracking Account maps directly to HubSpot Company. Company name, website, industry, and phone transfer as standard HubSpot company properties. Parent-child account hierarchies are not natively supported in Simple Sales Tracking but would map to HubSpot company associations if present.
Simple Sales Tracking
Opportunity
HubSpot
Deal
1:1Simple Sales Tracking Opportunity maps to HubSpot Deal. Deal name, amount, close date, stage, and owner transfer directly. HubSpot requires a primary company association per deal — we link the deal to the matched Company record using the opportunity's account reference.
Simple Sales Tracking
Lead
HubSpot
Contact (with lifecycle stage)
1:1Simple Sales Tracking Lead records route to HubSpot Contact with lifecycle_stage set to 'lead'. This preserves the record without splitting into HubSpot's separate Lead object, which is preferred for most migrations unless the team actively uses lead conversion workflows. If custom lead status values exist, we map them to corresponding HubSpot lifecycle stages during import, ensuring that downstream segmentation and automation reflect the original sales process.
Simple Sales Tracking
Task
HubSpot
Task
1:1Simple Sales Tracking Tasks migrate to HubSpot Tasks. Task subject, status, priority, due date, and associated record link (Contact, Account, or Opportunity) are preserved. HubSpot Tasks do not support native recurring task patterns — recurring tasks transfer as individual instances.
Simple Sales Tracking
Appointment
HubSpot
Meeting
1:1Simple Sales Tracking Appointments map to HubSpot Meetings. Start time, end time, location, subject, and associated record link transfer with original timestamps preserved. Meeting body or notes content maps to the HubSpot Meeting notes field. We also preserve any meeting description text as a separate property, and if the original appointment includes attendee information, we store it in a custom multi-email property for reference.
Simple Sales Tracking
Note
HubSpot
Note
1:1Simple Sales Tracking Notes migrate to HubSpot Notes. Note title and body text transfer as HubSpot note title and body. Notes are associated to the parent Contact, Company, or Deal record based on the source link. If a note contains multiple sections or attachments, we preserve the full text and store attachment URLs in a custom property, ensuring no context is lost during the transition.
Simple Sales Tracking
Custom Sales Record Field
HubSpot
Custom Property (Contact, Company, or Deal)
1:1Simple Sales Tracking custom fields attached to Contacts, Accounts, or Opportunities become HubSpot custom properties. We create the custom property in HubSpot with the matching field type before migration runs. Field type mapping: text to single-line text, number to number, date to date-time, picklist to single-option or multi-option.
Simple Sales Tracking
Lead Source
HubSpot
Lead Source (standard property)
1:1Simple Sales Tracking lead sources (e.g., Website, Referral, Trade Show) map to HubSpot's standard hs_lead_source property. We build a value-by-value map for all source values present in the data. Any unmapped values are preserved as custom property notes. If a source value is missing, we flag it for review and assign a temporary placeholder until the team defines the mapping.
Simple Sales Tracking
Commission Tracking Data
HubSpot
Custom Number Property
1:1Simple Sales Tracking commission percentages and assignments have no HubSpot native equivalent. We migrate commission data as a custom number field on the relevant record type. Commission calculations and automation should be rebuilt using HubSpot's workflow builder or a connected commission app post-migration.
Simple Sales Tracking
User (Owner)
HubSpot
HubSpot User
1:1Simple Sales Tracking owners are resolved by email match against HubSpot users. If a Simple Sales Tracking owner email matches an existing HubSpot user, records are assigned to that user. Unmatched owners are flagged before migration so the team can either create HubSpot users or assign records to a fallback owner.
| Simple Sales Tracking | HubSpot | Compatibility | |
|---|---|---|---|
| Contact (Person) | Contact1:1 | Fully supported | |
| Account | Company1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Lead | Contact (with lifecycle stage)1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Appointment | Meeting1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Custom Sales Record Field | Custom Property (Contact, Company, or Deal)1:1 | Fully supported | |
| Lead Source | Lead Source (standard property)1:1 | Fully supported | |
| Commission Tracking Data | Custom Number Property1:1 | Fully supported | |
| User (Owner) | HubSpot 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
HubSpot gotchas
Marketing Contacts billing model is migration-critical
Feature tier gating is not visible until onboarding
Mandatory onboarding fees inflate year-one cost
HubSpot CSV importer cannot migrate engagements or attachments
Custom objects require Enterprise and a pre-existing schema
Pair-specific challenges
Migration approach
Extract and audit Simple Sales Tracking data
FlitStack connects to Simple Sales Tracking via the API using account credentials. We pull a full export of Contacts, Accounts, Opportunities, Leads, Tasks, Appointments, Notes, and any custom field definitions. The export includes record counts, field-level null rates, and value distributions for pick-list fields. We surface duplicate records, orphaned opportunities (no account link), and custom field type information needed for HubSpot property creation.
Map objects and create HubSpot custom properties
We build the object mapping plan covering all 11 object equivalences. For custom fields in Simple Sales Tracking, we create corresponding HubSpot custom properties with matching types before any records are imported. Lead status values are mapped to HubSpot lifecycle stages per the value-mapping table. Commission fields are created as custom number properties. HubSpot pipelines and stages are configured to match Simple Sales Tracking opportunity stages where present.
Resolve owners by email match
Simple Sales Tracking owner records are matched against HubSpot users by email address. This determines which HubSpot user each Contact, Account, Opportunity, Task, and Meeting is assigned to after migration. Any Simple Sales Tracking owner with no matching HubSpot user is flagged in a pre-migration report. The team either creates HubSpot user accounts for those owners or selects a fallback owner before the migration run proceeds.
Run sample migration with field-level diff
A representative sample — typically 100 to 500 records across all object types — migrates first. We generate a field-level diff comparing each source field value against the corresponding HubSpot field value post-import. The diff confirms that lifecycle stage mapping, deal stage mapping, owner assignment, and custom property population are working as expected. You review the diff and approve before the full migration run commits.
Execute full migration with delta-pickup cutover
The full dataset migrates in batches via HubSpot's native import API. After the initial load completes, a delta-pickup window of 24 to 48 hours runs a second pass to capture any records created or modified in Simple Sales Tracking during the cutover. FlitStack generates a reconciliation report showing record counts by object, any records that failed to import, and the reason for each failure. One-click rollback is available if the reconciliation report shows unexpected gaps or data quality issues.
Platform deep dives
Simple Sales Tracking
Source
Strengths
Weaknesses
HubSpot
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 HubSpot.
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 HubSpot migration scoping. Not seeing yours? Book a call.
Walk through your Simple Sales Tracking to HubSpot 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 HubSpot
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.