CRM migration
Field-level mapping, validation, and rollback between Onsite CRM and HubSpot. We move data and schema; workflows are rebuilt natively in HubSpot.
Onsite CRM
Source
HubSpot
Destination
Compatibility
14 of 14
objects map 1:1 between Onsite CRM and HubSpot.
Complexity
CModerate
Timeline
24–48 hours
Overview
Onsite CRM stores contacts, companies, and deals in a relational model that maps directly to HubSpot's flat object structure. The key translation happens at the property level: Onsite CRM field names become HubSpot property names, and Onsite CRM's pipeline stages map to HubSpot deal pipeline stages. We extract records via Onsite CRM's API, then bulk-load them into HubSpot using the Contacts, Companies, and Deals APIs. Custom fields from Onsite CRM require HubSpot custom property creation before data lands — we handle that setup as part of the migration plan. Activity history (calls, emails, meetings, notes) migrates as HubSpot engagements with original timestamps and owners preserved. Owner resolution happens by email match against HubSpot user accounts. We surface data that cannot migrate natively (such as Onsite CRM-specific relationship metadata) as custom properties for post-migration reference. The migration preserves create timestamps as custom properties, and Onsite CRM internal IDs are stored on HubSpot records for traceability and delta-run de-duplication.
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 Onsite CRM 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.
Onsite CRM
Contact
HubSpot
Contact
1:1Onsite CRM Contact records map directly to HubSpot Contact records. Each Onsite CRM contact property becomes a HubSpot property. Primary company association maps to HubSpot's company association. Owner email resolves to a HubSpot user account. Original create date is preserved as a custom property. Onsite CRM internal ID is stored on the HubSpot Contact for traceability and delta-run de-duplication.
Onsite CRM
Company
HubSpot
Company
1:1Onsite CRM Company records map 1:1 to HubSpot Company records. Company name, domain, industry, employee count, and revenue fields translate to their HubSpot equivalents. Parent-company hierarchies map using HubSpot's parent company association. Original create date is preserved as a custom property. Onsite CRM internal ID is stored for traceability and delta-run de-duplication.
Onsite CRM
Deal
HubSpot
Deal
1:1Onsite CRM Deal records map to HubSpot Deal records. Each deal's pipeline and stage map to a HubSpot deal pipeline and stage. Amount, close date, and owner translate directly. Deals without a primary company link attach to a default HubSpot company or are flagged for manual resolution. Original create date preserved as custom property.
Onsite CRM
Pipeline
HubSpot
Deal Pipeline
1:1Onsite CRM pipelines become HubSpot deal pipelines. If Onsite CRM has multiple pipelines, we create corresponding pipelines in HubSpot. Each pipeline's stages map to HubSpot stage names with probabilities preserved as stage-level metadata. Stage names and probabilities are maintained throughout the migration.
Onsite CRM
Lead Status
HubSpot
lifecycle_stage (property)
1:1Onsite CRM's lead status field transforms to HubSpot's lifecycle_stage property on Contact. Status values map to HubSpot lifecycle stages (subscriber, lead, MQL, SQL, customer, evangelist) based on the most granular matching available in the source data. Stage-change timestamps are preserved as custom datetime properties.
Onsite CRM
Activity (Call)
HubSpot
Engagement (Call)
1:1Onsite CRM call logs migrate as HubSpot engagement calls with original timestamps, duration, outcome, and owner preserved. Call associations link to the original Contact, Company, or Deal record in HubSpot. All original call details are transferred during the migration.
Onsite CRM
Activity (Email)
HubSpot
Engagement (Email)
1:1Onsite CRM email logs migrate as HubSpot engagement emails. Subject, body, direction (sent/received), timestamp, and owner transfer. Associations to contacts and deals are preserved in HubSpot's engagement record. Email history is fully transferred with original metadata.
Onsite CRM
Activity (Meeting)
HubSpot
Engagement (Meeting)
1:1Onsite CRM meeting records become HubSpot engagement meetings with start time, end time, title, body, and owner. Meeting associations to contacts, companies, and deals map to HubSpot engagement associations. Meeting details transfer completely.
Onsite CRM
Activity (Note)
HubSpot
Engagement (Note)
1:1Onsite CRM notes migrate as HubSpot notes attached to the corresponding Contact, Company, or Deal. Original create date and owner are preserved. Rich-text formatting in Onsite CRM notes is preserved where the source data supports it. All note content transfers with original metadata intact.
Onsite CRM
Custom Fields
HubSpot
Custom Properties
1:1Onsite CRM custom fields on any standard object require pre-creation of HubSpot custom properties before data loads. We deliver a property creation plan as part of the migration package, including property type mapping (text, number, date, picklist) from Onsite CRM field types. Picklist fields are mapped value-by-value.
Onsite CRM
User / Owner
HubSpot
Owner (HubSpot user)
1:1Onsite CRM owner IDs resolve to HubSpot user accounts by email address. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts or assigns records to a fallback owner. No record lands without an owner in HubSpot.
Onsite CRM
Attachment / File
HubSpot
HubSpot Files
1:1Onsite CRM file attachments associated with contacts, companies, or deals re-upload to HubSpot Files and attach to the corresponding record. File size limits per HubSpot plan apply (25MB default per file). Inline images in notes are downloaded and rehosted with note content updated.
Onsite CRM
Tag / Label
HubSpot
HubSpot custom property (list)
1:1Onsite CRM tag or label data that lacks a direct HubSpot equivalent is preserved as a multi-value custom property (comma-separated text or list type). Tags used for segmentation are flagged so your team can recreate lists in HubSpot's native list or cohort tools.
Onsite CRM
Task / To-Do
HubSpot
Engagement task
1:1Onsite CRM tasks migrate as HubSpot engagement tasks with subject, due date, status, and owner preserved. Completed vs. open status maps to HubSpot's task completion model. Task associations to records transfer as engagement associations. Task history transfers with original metadata.
| Onsite CRM | HubSpot | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Deal Pipeline1:1 | Fully supported | |
| Lead Status | lifecycle_stage (property)1:1 | Fully supported | |
| Activity (Call) | Engagement (Call)1:1 | Fully supported | |
| Activity (Email) | Engagement (Email)1:1 | Fully supported | |
| Activity (Meeting) | Engagement (Meeting)1:1 | Fully supported | |
| Activity (Note) | Engagement (Note)1:1 | Fully supported | |
| Custom Fields | Custom Properties1:1 | Mapping required | |
| User / Owner | Owner (HubSpot user)1:1 | Fully supported | |
| Attachment / File | HubSpot Files1:1 | Fully supported | |
| Tag / Label | HubSpot custom property (list)1:1 | Fully supported | |
| Task / To-Do | Engagement task1: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.
Onsite CRM gotchas
No public API documentation found
Weebly-hosted infrastructure limits data access
Limited historical activity export
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
Audit Onsite CRM data volume and custom field inventory
We connect to Onsite CRM via API (read-only scope) and pull a full inventory of all object types, record counts per object, and every custom field definition including data types and picklist values. This audit determines the migration scope, identifies which custom fields need HubSpot property pre-creation, and surfaces any Onsite CRM-specific objects that require custom mapping logic. The audit output is a data dictionary shared with your team before any migration work begins.
Create HubSpot custom properties from Onsite CRM field inventory
Before any data loads, we create all required HubSpot custom properties identified in the audit. This includes setting property types (text, number, date, checkbox, picklist), defining picklist values for mapped fields, and configuring whether each property appears on the contact, company, or deal record. Properties are created via HubSpot's API using a properties configuration file generated from the Onsite CRM field audit. Your team reviews and approves the property plan before the migration run.
Run a sample migration with field-level diff on a representative record slice
A test migration runs against a sample set of 100–500 records covering contacts, companies, deals, and activities across different Onsite CRM data categories. We generate a field-level diff report comparing source values against destination values in HubSpot. Your team reviews the diff to verify lifecycle stage mapping, pipeline-to-stage mapping, owner resolution, and custom property population. No full migration runs until your team signs off on the sample results.
Execute full migration with delta-pickup window and audit log
The full migration runs against HubSpot, processing contacts, companies, deals, and engagement history in dependency order (companies first, then contacts, then deals, then activities). A delta-pickup window of 24–48 hours captures any records created or modified in Onsite CRM during the migration cutover. An audit log records every operation (create, update, associate) for post-migration reconciliation. If validation fails, one-click rollback reverts the HubSpot instance to its pre-migration state.
Deliver export package for workflow and automation rebuild reference
We export Onsite CRM workflow definitions, automation rules, assignment logic, and any custom formula fields as structured documentation. This package gives your HubSpot admin a reference to rebuild equivalent automations in HubSpot's workflow builder. We do not migrate the automation logic itself — the export package is the handoff artifact for your team to configure HubSpot workflows, sequences, and lead routing based on the documented Onsite CRM logic.
Platform deep dives
Onsite CRM
Source
Strengths
Weaknesses
HubSpot
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 Onsite CRM and HubSpot.
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
Onsite CRM: Not publicly documented.
Data volume sensitivity
Onsite CRM 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 Onsite CRM to HubSpot migration scoping. Not seeing yours? Book a call.
Walk through your Onsite CRM 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 Onsite CRM
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.