Insightly ✓ Salesforce Migration
Insightly
Salesforce

Migrate from Insightly to Salesforce in hours, not months

Insightly's limited customization and rigid pipeline structure leave sales teams outgrowing their CRM. SuprSwitch's proprietary transformation layer automatically maps your Contacts, Organizations, and Deals into Salesforce's native Accounts, Leads, and Opportunities—preserving field fidelity and relationship history in a single pass, no manual data cleanup required.

< 24 hrs
Migration Speed
100.00%
Data Integrity
Instant
Field Mapping
"Will my Insightly custom fields on Organizations and Contacts actually convert to Salesforce, or will I lose them?"
SuprSwitch's native schema mapping extracts every custom field from Insightly's Organizations and Contacts objects and intelligently maps them to Salesforce Account and Contact objects. Our proprietary transformation layer preserves field data types (picklists become Salesforce picklists, checkboxes become checkboxes) and handles Insightly's unique multi-select custom fields by converting them to Salesforce multi-select picklists where possible, or storing them as text fields with separator notation when needed to maintain data integrity.
"What happens to all my Activities and Tasks history? Will Insightly's linked activity records show up in Salesforce records?"
Our in-house engine extracts complete activity history from Insightly—Tasks, Calls, Emails, and Notes—and maps them directly to Salesforce Activities (Tasks and Events) while preserving timestamps, descriptions, and associations. Insightly's linked Activities (which can relate to multiple records) are handled through SuprSwitch's relationship flattening: each activity is assigned to its primary associated Contact/Account, with secondary relationships logged in a custom lookup field so you retain the context without orphaning records.
"How does Insightly's Projects structure map to Salesforce if I don't have Projects module?"
SuprSwitch's direct data extraction transforms Insightly Projects into Salesforce's native Campaign object, mapping Project name, description, budget, and custom fields accordingly. Project Milestones become Campaign Hierarchies, and all Project Tasks are converted to Salesforce Tasks linked to the Campaign. This approach respects Salesforce's platform strengths while maintaining your project structure—though note that Salesforce Campaigns function differently from Insightly Projects, so you may want to configure Campaigns-for-Projects workflows post-migration for best results.
Why SuprSwitch

Why Sales Teams Choose SuprSwitch Over a DIY Insightly CSV Export to Salesforce

Insightly's native CSV export flattens hierarchical relationships, dropping critical Organisation–Contact links and Project–Task associations that are essential in Salesforce. The export also loses custom field types (picklists collapse to text, currency fields lose formatting), fails to migrate Insightly's Activity timeline, and doesn't map Insightly's pipeline stages to Salesforce Opportunity stages intelligently. SuprSwitch's in-house transformation layer preserves referential integrity, performs native schema mapping of platform-specific objects, and ensures every record arrives in Salesforce with full data fidelity and relationship structure intact.

🔗

Organisation–Contact Links Fully Preserved

Insightly Organisations and Contacts maintain many-to-many relationships that are fundamental to sales workflows—a Contact works for multiple Organisations, and an Organisation has multiple Contacts. CSV export treats each relationship as a separate row, breaking the association structure entirely. SuprSwitch's transformation layer reconstructs these relationships as Salesforce Accounts and Contacts with proper lookup fields and junction objects, maintaining the exact many-to-many cardinality. Your sales team lands in Salesforce with complete visibility of which contacts belong to which accounts.

📋

Custom Field Types Land as Real Properties

Insightly's custom fields include proper picklists, currency, and date types, but CSV export flattens everything to text strings. A picklist like "Engagement Status" becomes plain text, forcing manual re-mapping in Salesforce. SuprSwitch's native schema mapper recognizes Insightly field definitions, translates Insightly picklist values into Salesforce picklists with correct recordTypes, and converts currency and date fields to their proper Salesforce field types. Your reports and validation rules work correctly from day one.

📅

Activity History Migrates with Full Timeline

Insightly Activities (tasks, calls, emails logged against Contacts, Organisations, and Projects) are not included in standard CSV exports—your team loses the entire engagement history. SuprSwitch extracts Insightly Activities via direct data extraction, maps them to Salesforce Tasks and Events with correct date/time stamps, and attaches them to the correct Accounts, Contacts, and Opportunities. Your sales reps see the full communication history the moment they log in.

🎯

Pipeline Stages Map Intelligently to Opportunities

Insightly uses a Pipeline object with custom Stages (e.g., 'Discovery', 'Demo', 'Proposal') that have no direct equivalent in a Salesforce CSV import. CSV export leaves Pipeline data orphaned. SuprSwitch's in-house engine recognizes Insightly Pipelines, maps each stage to a Salesforce Opportunity stage, and populates Opportunity records with the correct StageName, probability, and close date. Your pipeline reporting and sales process automation activates without manual stage re-configuration.

Trusted by 200+ sales-led teams who migrated off
Data Coverage

Every Insightly Asset, Accounted For

Insightly organizes customer data across six core object types: Contacts, Organizations, Opportunities, Projects, Activities, and Notes. SuprSwitch migrates all of these objects with complete field mapping, preserving relationships, custom fields, and historical data throughout your transition to Salesforce.

👤 Contacts
All records
Contacts
Salesforce Contacts
💡 Insightly Contacts map directly to Salesforce Contacts. Multi-value email and phone fields in Insightly are normalized into Salesforce's single Email and Phone fields, with additional emails/phones stored in related Contact records or custom fields as needed.
🏢 Organizations
All records
Organizations
Salesforce Accounts
💡 Insightly Organizations map to Salesforce Accounts. Organization relationship hierarchies (parent/child) are preserved through Salesforce's Parent Account lookup field. Custom organization fields transfer as custom Account fields with type preservation.
🎯 Opportunities
All records
Opportunities
Salesforce Opportunities
💡 Insightly Opportunities map to Salesforce Opportunities with full stage, probability, and close date preservation. Custom opportunity fields and pipeline-specific picklist values are converted to Salesforce field definitions; related Contact and Organization relationships are maintained via Contact Role and Account lookup fields.
📋 Projects
All records
Projects
Salesforce Projects (Salesforce Project Management/Custom Objects)
💡 Insightly Projects, which function as project/service delivery containers, map to Salesforce Project records (via Salesforce Projects module or custom objects) or can be linked to Opportunities/Accounts depending on your use case. Project milestones and tasks are migrated as related records.
Activities
All records
Activities
Salesforce Tasks & Events
💡 Insightly Activities (calls, meetings, emails, to-dos) map to Salesforce Tasks or Events based on type. All-day and timed activities are normalized to Salesforce event/task records. Activity relationships to Contacts, Organizations, and Opportunities are preserved via lookup fields.
📝 Notes
All records
Notes
Salesforce Notes & Attachments
💡 Insightly Notes map to Salesforce Notes (or Notes/Attachments objects depending on Salesforce edition). Note-to-Contact, Note-to-Organization, and Note-to-Opportunity relationships are maintained; file attachments in Insightly transfer as Salesforce file attachments on related records.
📸

Pre-Migration Data Preview

Before we touch anything, SuprSwitch generates a full data inventory of your account: record counts per object, custom field list, pipeline structure, and owner mapping. You approve the field map before the migration runs.

Under the Hood

Built for Insightly's Relational Object Graph

Insightly uses a deep relational model with polymorphic associations—Organizations, Contacts, and Leads can each relate to Projects, Opportunities, and custom objects through a flexible linking system. SuprSwitch's proprietary extraction engine reads Insightly's native record identifiers and relationship metadata directly, preserving the exact cardinality and object types without flattening or CSV intermediaries. Our transformation layer reconstructs these polymorphic associations into Salesforce's Account-Contact-Opportunity hierarchy, maintaining referential integrity across the entire dataset.

Native Insightly Record Extraction

Direct Pipeline

Insightly stores Contacts, Organizations, Leads, Opportunities, and Projects as discrete relational entities with unique RecordID sequencing and system-managed timestamps. SuprSwitch's proprietary extraction engine reads these record types and their metadata fields (CreatedDate, UpdatedDate, RecordStatus) directly from Insightly's data layer without CSV export. We capture field-level lineage and custom field definitions (text, number, date, picklist, multi-select) for each object, ensuring no data shape loss during migration.

Polymorphic Association Rebuild

Referential Integrity

Insightly's linking system allows Contacts to relate to Organizations, Opportunities, and Projects through flexible many-to-many associations, and Opportunities to link to multiple Contacts via relationship roles. Our transformation layer reads the source association metadata and role definitions, then rebuilds these connections as Salesforce's Account-Contact junction records, Opportunity Contact Roles, and custom lookup relationships. All role mappings and historical association timestamps are preserved to prevent orphaned records.

Custom Field Type Mapping

Schema-Aware

Insightly supports text fields, textarea, number, currency, date, datetime, checkbox, picklist, and multi-select custom fields on every object type. SuprSwitch maps Insightly's picklist definitions and multi-select options directly into Salesforce's record types and field values, preserving choice lists and dependencies. We auto-detect field validation rules and character limits, then apply equivalent Salesforce field constraints to ensure data compliance post-migration without manual remapping.

Delta Sync on Cutover

Live-Safe Migration

Insightly tracks all record changes via CreatedDate, UpdatedDate, and RecordStatus fields, allowing us to isolate net-new and modified records created after the initial bulk load. SuprSwitch's incremental sync engine performs a final delta pass on migration day, capturing last-minute Opportunities, Contact updates, and ownership changes. This zero-downtime approach lets you keep Insightly live until final cutover, then load only day-of deltas into Salesforce without re-migrating stable records.

100% Data Fidelity Guarantee

We verify record counts and field values in before sign-off. Any discrepancy is fixed before you go live.

30-Day Post-Migration Support

A dedicated migration engineer is available for 30 days post-launch to fix any data issues that surface after your team starts using.

SOC 2 Compliant Process

Data is encrypted in transit and at rest. We never store your credentials — OAuth tokens are used and revoked per migration.

Migration Architecture

Migration Architecture: Insightly → Salesforce

SuprSwitch's purpose-built migration engine ingests Insightly's hierarchical contact, company, and deal structure, automating field mapping and relationship resolution before native Salesforce object creation. The process maintains data integrity across Insightly's custom fields, linked records, and activity streams while conforming to Salesforce's standard and custom object taxonomy.

1
Schema Audit & Mapping
Inventory all Insightly Contacts, Companies, Opportunities, Projects, and custom fields. Map to Salesforce Accounts, Contacts, Opportunities, and custom objects with field-type conversion rules.
Day 1
2
Primary Object Migration
Migrate Insightly Companies and Contacts to Salesforce Accounts and Contacts. Apply custom field values and organization hierarchies in batches.
Day 2–3
3
Relationships & Activity History
Link migrated Contacts to Accounts, migrate Insightly Opportunities and Projects to Salesforce Opportunities, and hydrate all Activities and Notes with timestamps and ownership.
Day 3–4
4
Delta Sync & Validation + Go-Live
Capture Insightly changes during migration window, validate record counts and field accuracy across all objects, run duplicate detection, and cutover to Salesforce.
Day 4–5
🔄

SuprSwitch's proprietary extraction engine directly ingests Insightly's contact, company, opportunity, and activity databases, decompressing linked record relationships and custom metadata in a single scan without intermediate staging.

Native schema mapping and transformation layer automatically converts Insightly field types to Salesforce equivalents (text to picklist, currency scaling, date formatting) and batches records into optimal Salesforce load chunks for parallel processing.

Post-migration validation engine compares record counts, field-by-field checksums, and relationship cardinality between Insightly source and Salesforce target, flagging orphaned records and data type mismatches before go-live.

The Human Element

Beyond Automation: In-House RevOps Experts

Our proprietary engine handles 99% of the heavy lifting, but every CRM has strict platform limitations. When HubSpot restricts automated imports for complex workflows or proprietary activity history, our in-house RevOps professionals step in.

We manually rebuild the business logic that machines can't touch, ensuring your new environment is perfectly tuned and ready for your sales team on day one.

RevOps Expert RevOps Expert RevOps Expert

Dedicated RevOps Engineer included with every migration.

What our experts handle manually:

Complex Workflows & Automations

Automated engines cannot migrate business logic. We manually translate and rebuild your HubSpot automations natively in HubSpot.

Restricted Activity History

Some historical data types are locked by HubSpot. Our team uses creative data-structuring to ensure no context is lost.

Custom Object Architecture

When standard mapping isn't enough, we architect and deploy custom objects in HubSpot to match your exact sales motion.

Choose the Migration Plan That Fits Your Business

Whether you want complete control or expert guidance, we’ve got you covered.

Self-Service

$499

Starting price, up to 50,000 records

Check

Access to all supported CRMs

Check

Free Sample migrations

Check

Real-time Preview

Check

Migration Analytics Report

Custom Migration

$Talk to us

Custom quotes for complex migrations.

Group

Everything in Guided Migration +

Group

Complex Field Transformations

Group

Industry-Specific Customizations

Group

Legacy System Integration

Group

Complex Data Filtering

FAQs

Common Questions About Migration

Edge Case Insightly has Projects with milestones and task dependencies—how does SuprSwitch handle this in Salesforce where Projects aren't a native object?
Insightly's Project object is a unique feature that doesn't map directly to Salesforce's standard objects. SuprSwitch's transformation layer converts Insightly Projects into Salesforce Campaigns paired with custom Milestone tracking through Tasks with custom fields for dependency relationships. Project milestones become Campaign Milestones (Salesforce's native milestone object), while task dependencies are preserved through lookup fields and custom formula fields that maintain the parent-child relationship. This approach keeps your project structure intact while leveraging Salesforce's native functionality for timeline and resource tracking.
Technical How does SuprSwitch map Insightly's custom dropdown picklists to Salesforce picklists, especially if the values differ between systems?
Insightly and Salesforce handle picklist values differently in their data models. SuprSwitch's native schema mapping analyzes both systems' picklist definitions during the pre-migration phase and creates a mapping table for any values that don't match exactly. If Insightly has a picklist value like 'Follow-up Required' and Salesforce expects 'Needs Follow-up', our engine automatically translates during migration. For unmapped values, SuprSwitch flags them in a migration report so you can manually adjust field definitions before migration runs, ensuring zero data loss and preventing validation errors on custom fields.
Timeline What's the typical timeline for migrating from Insightly to Salesforce, and what happens to my Insightly data during the migration window?
A typical Insightly to Salesforce migration takes 2-4 weeks depending on your data volume and custom field complexity. The process breaks into phases: assessment and mapping (3-5 days), test migration (3-5 days), stakeholder validation (2-3 days), and cutover (24-48 hours). During cutover, your Insightly org remains unchanged; we create a complete duplicate of your data in Salesforce independently. Once validation is complete and you've signed off, we perform the final sync to pull any last-minute changes, then you switch your team to Salesforce. Your Insightly instance stays live until you decide to sunset it—there's no forced cutoff.
Edge Case Insightly allows multiple pipeline stages with custom field visibility per stage—does Salesforce support this same conditional visibility logic?
Salesforce doesn't natively support per-stage field visibility the way Insightly does with its stage-dependent field mapping. SuprSwitch handles this by converting Insightly's conditional field logic into Salesforce's Page Layout architecture combined with Lightning Record Types. Each Insightly opportunity pipeline becomes a distinct Record Type in Salesforce, with corresponding Page Layouts that show/hide fields based on stage position, replicating your original visibility rules. This requires an additional setup step but preserves your field governance without forcing users to see irrelevant fields at each stage.
Data Integrity How does SuprSwitch verify that all my Insightly data arrived correctly in Salesforce, and what happens if a record fails to migrate?
SuprSwitch runs a multi-layer validation engine post-migration: record count reconciliation (ensuring every Insightly record has a Salesforce equivalent), field-level checksums (comparing data values to spot transformation errors), and relationship integrity scans (verifying all lookups and parent-child links are intact). Any failures are logged in a detailed exception report showing the record ID, field, and reason for failure—most commonly validation rule violations or missing required fields on the Salesforce side. We provide a remediation guide to fix the root cause and re-migrate only the failed records. You'll also have temporary read-only access to both systems during a 30-day validation window to spot-check critical records before decommissioning Insightly.

Ready to move your team off Insightly ?

Start with a free sample migration — see your actual Insightly data in Salesforce before you commit.

Try Free Sample Migration