Highrise to Salesforce migration
We migrate People, Companies, Deals, Cases, Tasks, and Engagement history from Highrise into Salesforce Sales Cloud with Highrise's plain-text exports parsed into structured Salesforce fields, parent-record lookup resolution across the Account-Contact-Opportunity hierarchy, and the flat-rate to per-user pricing shift documented before cutover.
FlitStack AI migrates contacts, accounts, opportunities, cases and opportunity stages from Highrise to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-6 weeks.

What moves from Highrise to Salesforce?
Moving from Highrise to Salesforce Sales Cloud is a migration from a minimalist, flat-rate contact manager to a full enterprise CRM with a fundamentally different data architecture.
Read the full summary
Highrise stores People and Companies as Party types, Deals and Cases as plain-text exports, and all notes and emails as Recordings; Salesforce uses separate Account, Contact, Lead, and Opportunity objects with typed fields, a formal Opportunity Stage model, and a Case object for service tracking. We handle the TXT parsing for Deals and Cases, resolve the Highrise Party-to-Account-Contact relationship, and use the Salesforce Bulk API for large engagement histories. Highrise has no native automation engine, so there are no Workflows or Sequences to migrate—only an inventory of any Zapier Zaps the customer built outside Highrise. We deliver that Zap inventory as a written handoff document for rebuilding in Salesforce Flow or a dedicated sales engagement tool. Timeline ranges from four weeks for clean, small-account migrations to twelve weeks for accounts with large Cases, complex custom fields, or extensive recording histories.
People → Contact
Highrise People are the primary contact records and map directly to Salesforce Contact.
How it maps
We extract all standard fields (name, email, phone, address, social links) from the CSV/Excel export and map them to typed Salesforce fields. The Highrise contact's associated Company (Party link) resolves to a Salesforce Account that we create before Contacts are imported. Any Highrise People without a linked Company map to Contacts without an AccountId and are flagged for the customer to assign accounts manually or merge.
Companies → Account
Highrise Companies are a distinct Party type and map to Salesforce Account.
How it maps
The parties.xml API endpoint provides the export, and we preserve the Company-Contact association using Highrise's party_id foreign key. Account is created before any Contact import so that the AccountId Lookup is satisfied at Contact insert. The Company name becomes the Account Name; any custom fields on the Company Party map to custom fields on Account.
Deals → Opportunity
Highrise Deals export as plain-text (.txt) only, not CSV.
How it maps
We parse the TXT output to extract deal name, stage, value (as currency), responsible user (mapped to Salesforce OwnerId), and linked Party. We reconstruct these as Salesforce Opportunity records with the Highrise stage name mapped to a Salesforce StageName value in the configured Sales Process. Closed dates from Highrise migrate to CloseDate. Deals with complex or ambiguous data are flagged for manual review before the final migration step.
Cases → Case
Highrise Cases (Customer Cases) handle support or task tracking and export as TXT only.
How it maps
We parse the text to extract case title, status, linked Party, and responsible user, then map these to Salesforce Case with Subject, Status, and OwnerId resolved. Any embedded attachment references in the TXT output are flagged because attachments cannot transfer through the TXT export mechanism. If the destination Salesforce org includes Service Cloud, Cases map with full Status and Priority field support; otherwise, Cases map to a custom Case__c object in Sales Cloud.
Deal Stage → Opportunity Stage
Highrise's named deal stages (e.g., New, Contacted, Qualified, Won, Lost) are extracted during scoping and mapped to Salesforce StageName values in a pre-configured Sales Process.
How it maps
We create the Sales Process in the destination Salesforce org during the schema design phase, whitelisting only the stages that exist in the Highrise account. Stage probabilities are approximated from Highrise's implied stage progression or set to Salesforce defaults if no probability data is available.
Tasks → Task
Highrise Tasks are standard API-accessible objects and export cleanly via the tasks.xml endpoint.
How it maps
Completed and open tasks transfer with due dates, assignees (mapped to Salesforce OwnerId via the User lookup), and related Party references. Status (completed, open, deferred) maps to Salesforce Task Status, and Priority maps to Task Priority. Tasks linked to Deals resolve to the Opportunity ID after Opportunity import is complete.
- PeopleContact1:1
- CompaniesAccount1:1
- DealsOpportunity1:1
- CasesCase1:1
- Deal StageOpportunity Stagetransformed
- TasksTask1:1
+ 6 more in the mapping below
How Highrise and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Highrise | Salesforce |
|---|---|---|
| Contact model | Single Party type for People and Companies in one table | Separate Account (organization) and Contact (person) with explicit relationship linking |
| Pipeline customization | Named stages (New, Contacted, Qualified, Won, Lost) with flat list | Record Types, Sales Processes, and unlimited stage definitions from Professional tier |
| Cases handling | Customer Cases export as plain text only | Salesforce Case object with Status, Priority, Origin, and Entitlement flows |
| Custom objects | Custom fields on People, Companies, and Deals only | Custom objects with lookup relationships from Professional tier ($80/user/mo) |
| Automation engine | No native automation; Zapier-dependent for any workflow logic | Salesforce Flow with record-triggered, scheduled, and screen variants from Professional |
| Pricing model | Flat-rate per account ($99-$299/month for 5-15 users) | Per-user at $25-$330/user/month depending on edition |
| Mobile parity | iOS app historically missing Deals management | Salesforce mobile app with full feature parity across iOS and Android |
What to watch for in a Highrise to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Deals and Cases export as plain text, not structured CSV
Highrise's built-in export outputs Deals and Cases as .txt files rather than structured CSV.
How we handle it
We parse the TXT output to extract field values, but this strips HTML formatting, loses inline image references, and provides no column mapping. Any Deals or Cases with complex embedded data (tables, links, structured text blocks) are flagged for manual verification before the final migration step. The customer must accept that rich Deal and Case content arrives as plain text in Salesforce.
Highrise API rate limits require conservative throttling
Highrise enforces tiered rate limits: 150 req/5s for most endpoints, 2 req/10s for email-based contact searches, and 10 req/10s for GET /recordings.xml.
How we handle it
Exceeding any limit returns a 503 with a Retry-After header. We throttle extraction jobs to the most restrictive limit and build exponential backoff into retry logic. Accounts with large contact bases that rely heavily on email searches have extended extraction timelines because we cannot parallelize those API calls.
No parent-account creation sequence produces orphaned contacts
Highrise People can exist with or without a linked Company (Party).
How we handle it
Salesforce requires an AccountId on every Contact that represents an organization contact. If we import People before the parent Companies are created and linked, Contacts arrive without AccountId and appear orphaned in Salesforce reports. We sequence the migration as: Accounts first, then Contacts, then Opportunities and Cases. The customer must confirm that all People who should have a Company association have one in Highrise before we begin extraction.
Highrise has no native automation, so there is nothing to migrate
Highrise has no native workflow, automation, or sequence engine.
How we handle it
Any automation the customer built lives outside Highrise—typically in Zapier, Make, or email filtering rules. We document every external automation trigger and action the customer identifies during discovery so they can rebuild them in Salesforce Flow or a dedicated sales engagement tool. We do not migrate Zapier Zaps because they require OAuth re-authentication and cannot be exported as transferable configuration. The customer receives a Zap inventory document as a rebuild guide.
Atom feeds return only the 25 most recent recordings
Highrise exposes Atom feeds at endpoints like /recordings.atom and /people/{id}/recordings.atom, returning the 25 most recent recordings per subject.
How we handle it
These feeds preserve metadata (date, author, type) useful for incremental captures during a phased migration window. However, they cannot serve as the sole source for full history because of the 25-record limit. We use the Atom feeds for delta captures only and rely on the full TXT export for the baseline recording history.
How the migration runs
Discovery and data audit
We audit the source Highrise account across all tiers (Free through Enterprise), extracting People, Companies, Deals, Cases, Tasks, and Recordings via the API and built-in export tools.
What this step covers
We identify the TXT parsing complexity for Deals and Cases, count custom field definitions, inventory all tags, and list any Zapier or Make automations the customer has built outside Highrise. We also extract the User roster and verify account-contact association ratios. The discovery output is a written migration scope with record counts per object, a schema design brief for the destination Salesforce org, and a flag list of any data requiring manual review before migration.
Schema design and Salesforce Sandbox setup
We design the destination schema in Salesforce.
What this step covers
This includes creating custom fields on Account, Contact, Opportunity, and Case that mirror Highrise's custom field definitions; configuring the Sales Process with stages derived from Highrise's deal stage names; setting up Record Types if the customer uses multiple deal pipelines; and provisioning any custom objects if the account uses Salesforce Professional or above. Schema is deployed into a Salesforce Sandbox (Full Copy or Partial Copy) for validation before any production migration step.
Sandbox migration and reconciliation
We run a full migration into the Sandbox using production-like data volume.
What this step covers
The customer's RevOps lead or Salesforce admin reconciles record counts (Accounts in, Contacts in, Opportunities in, Cases in, Tasks in, Notes in), spot-checks 25-50 random records against the Highrise source for field-level accuracy, and reviews the TXT-parsed Deal and Case content. Sign-off on the sandbox migration is required before production migration begins. Any mapping corrections, custom field type adjustments, or stage configuration changes happen at this stage.
Owner reconciliation and User provisioning
We extract every distinct Highrise User referenced on Deal, Case, and Task records and match by email against the Salesforce destination org's User table.
What this step covers
Any Highrise User without a matching Salesforce User is placed in a reconciliation queue. The customer's Salesforce admin provisions the missing Users (active status based on whether the original Highrise user is still active on the team). Migration cannot proceed past this step because OwnerId references on Opportunity and Case must resolve to a valid Salesforce User.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Highrise Companies), Contacts (with AccountId resolved from the Company mapping), Opportunities (from parsed Deal TXT with OwnerId and AccountId resolved), Cases (from parsed Case TXT with OwnerId resolved), Tasks, Notes and Emails (via Salesforce Bulk API 2.0 with parent-record resolution for WhoId and WhatId), Tags (applied as multi-select picklist values or Tag records).
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. TXT-parsed records that flagged for manual review are held until post-migration verification.
Cutover, delta sync, and Zap inventory handoff
We freeze writes to Highrise during cutover, run a final delta migration of any records modified during the migration window (captured via Highrise's updated_at timestamps), then mark Salesforce as the system of record.
What this step covers
We deliver the Zap inventory document (all external automations documented with trigger, actions, and recommended Salesforce Flow equivalent) to the customer's admin team. We support a one-week hypercare window for reconciliation issues raised by the sales team. We do not rebuild Zapier Zaps as Salesforce Flow within migration scope; that is a separate engagement or an internal admin task.
Post-migration data quality review
We run a post-migration data quality check comparing record counts and spot-field values between Highrise final state and Salesforce state.
What this step covers
We verify that all Contact records have either an AccountId or a null AccountId with a flag for manual account assignment. We confirm that all Opportunity records have an OwnerId, AccountId, and StageName. We flag any Case records that arrived with truncated content from the TXT parsing. The customer receives a final migration report with record counts, any remaining data gaps, and recommended cleanup actions for their Salesforce admin.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, TXT parsing complexity for Deals and Cases, and the number of custom fields requiring destination schema setup. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Highrise to Salesforce →Why teams move from Highrise to Salesforce
- Highrise stopped accepting new customers in August 2018 and is effectively in maintenance mode, leaving existing accounts on an aging platform with no development roadmap. Salesforce continues active development across Sales Cloud, Service Cloud, and the broader Platform, making it the only viable long-term destination for teams that have outgrown Highrise's feature ceiling. TrustRadius explicitly labels Highrise as discontinued, and G2 reviewers cite the stagnation as the primary reason for switching to platforms with active product development.
- Highrise has no native automation, advanced reporting, or pipeline analytics. Teams that move past basic contact tracking need Salesforce's Flow engine for process automation, standard and custom report types for multi-dimensional pipeline analysis, and Forecasting for territory-based revenue planning. G2 and Capterra reviews for Highrise consistently flag the absence of these features as the ceiling that forces a migration when teams scale beyond five to ten users.
- Salesforce's AppExchange has over 9,000 listings versus Highrise's limited native integrations and Zapier-dependent workaround model. Companies that need native CPQ, ERP connectors, contract lifecycle management, or revenue intelligence tools move to Salesforce because those integrations exist as first-party or AppExchange-certified packages rather than fragile multi-step Zapier chains. The integration depth is a structural advantage for teams with complex tech stacks.
- Highrise's flat-rate pricing makes sense at small scale but becomes limiting as teams grow into enterprise needs. Salesforce's per-user model at Professional ($80/user) unlocks unlimited record types, custom objects, advanced Flow, and full API access—capabilities that justify the per-seat cost for teams that have hit Highrise's feature ceiling. The price-per-feature ratio shifts decisively toward Salesforce once a team needs anything beyond basic pipeline tracking.
- The iOS app historically shipped without Deals functionality, forcing mobile users to the web interface for deal management. Salesforce's mobile app provides full feature parity across iOS and Android, including pipeline management, Opportunity editing, Task and Event creation, and Live Client Notifications. Mobile-first sales teams consistently cite the mobile parity gap as a friction point in their daily workflow that Salesforce resolves.
Questions, answered
Highrise to Salesforce migration questions
How long does a Highrise to Salesforce migration take?
Most migrations land between four and six weeks for accounts under 15,000 People, 3,000 Deals, and 500 Cases with no complex custom field sets. Accounts with large Cases histories (over 10,000 Cases), extensive custom field definitions, or multiple deal pipelines requiring Salesforce Record Type configuration move to eight to twelve weeks because of TXT parsing validation, custom schema deployment cycles, and the sandbox-to-production handoff process. The Highrise API rate limits (150 req/5s general, 2 req/10s for email searches) add extraction time for large contact databases.
Do my Highrise automations and Zapier Zaps migrate to Salesforce?
Highrise has no native automation engine, so there are no native Workflows or Sequences to migrate. Any automations the customer built outside Highrise—in Zapier, Make, or email filtering rules—do not transfer because Zapier Zaps require OAuth re-authentication and cannot be exported as transferable configuration. We deliver a written Zap inventory document that lists every external automation the customer identified during discovery, with its trigger, conditions, actions, and a recommended Salesforce Flow equivalent rebuild step. The customer's admin or a Salesforce partner rebuilds them post-migration.
Will I lose my Deal and Case history during migration?
Your Deal and Case records will transfer, but Highrise exports them as plain-text (.txt) files rather than structured CSV. We parse the TXT output to extract deal name, stage, value, responsible user, and linked contact, then reconstruct these as Salesforce Opportunity and Case records. HTML formatting, inline images, and structured text blocks within Deals and Cases will arrive as plain text. We flag any Deal or Case with complex content for manual verification before the final migration step, so you can decide whether to accept the plain-text version or manually re-enter the structured content in Salesforce.
Do Reports and Dashboards migrate from Highrise to Salesforce?
No. Highrise's built-in reporting is basic at best (basic pipeline and contact reports), and Salesforce's reporting engine uses a completely different data model, report types, and dashboard components. We do not migrate Reports or Dashboards as code. We deliver a written inventory of every Highrise report with its filters, groupings, and data sources, and the customer's Salesforce admin rebuilds them in Salesforce's report builder using the migrated data. Custom report types may be needed for non-standard object relationships and are scoped separately.
Can FlitStack AI migrate from Highrise to a Salesforce Sandbox first?
Yes. We always run the first full migration into a Salesforce Sandbox (Full Copy or Partial Copy) before touching production. The Sandbox migration uses production-like data volumes and serves as the validation gate. The customer's Salesforce admin and RevOps lead review the migrated data, sign off on field mapping accuracy and TXT-parsed content quality, and approve the migration before we proceed to production. Corrections to schema design, custom field definitions, or stage mapping are made in the Sandbox, not in production.
What happens to my Highrise account after migration?
We do not close or modify the Highrise account as part of the migration scope. The customer retains access to Highrise until they choose to cancel their subscription directly with Highrise. We recommend keeping Highrise in read-only mode for 30 days post-migration as a rollback reference while the Salesforce data is validated by the sales team. After the hypercare window closes and the customer confirms Salesforce data accuracy, the Highrise subscription can be canceled at the next billing cycle. We do not provide post-migration admin support or ongoing data stewardship.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → Twenty CRM to SalesforceMapping · history · rollbackBlackbaud to SalesforceMapping · history · rollbackActiveCampaign to SalesforceMapping · history · rollbackJobber to SalesforceMapping · history · rollbackSuiteCRM to SalesforceMapping · history · rollbackClose to SalesforceMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from Highrise to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote