Skip to content
Get a quote

SuperOffice CRM to Salesforce migration

We migrate Contacts, Companies, Sales, and Activities from SuperOffice CRM into Salesforce Sales Cloud with Companies sequenced first to satisfy the Account-Contact lookup chain, Activity history preserved through the Bulk API, and every SuperOffice object mapped to a typed Salesforce field before cutover.

Short answer

FlitStack AI migrates accounts, contacts, opportunities, opportunity stages and quotes from SuperOffice CRM 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-8 weeks.

By

Source SuperOffice CRM
DestinationSalesforce
AccountContactOpportunityOpportunity StageQuote
Mapped field by field · sample run · one-click rollback

What moves from SuperOffice CRM to Salesforce?

Moving from SuperOffice CRM to Salesforce Sales Cloud is a structural migration, not a record copy.

Read the full summary

SuperOffice uses one unified Contact and Company model where the Company-Contact link is the primary relationship; Salesforce separates Accounts (replacing Companies), Leads (for unqualified prospects), and Contacts (attached to Accounts). For most SuperOffice accounts with a mature B2B customer base, the migration lands all Contacts as Salesforce Contacts with the AccountId resolved from the Company mapping, and any raw unqualified prospects land as Salesforce Leads. We sequence Accounts first so that every Contact insert satisfies the required AccountId lookup. Activity history (calls, emails, appointments, tasks) cannot move through Salesforce's CSV loader at scale — we use the Bulk API 2.0 with chunking and parent-record resolution to preserve the full timeline. Selections, Documents, Quote Alternatives, and Project-Type links do not have native equivalents in Salesforce; we handle each as a documented transformation with post-migration handoff notes. SuperOffice Workflows, CRM scripts, and any on-premises add-ons do not migrate as code.

1:1

Company → Account

SuperOffice Company records map directly to Salesforce Account.

How it maps

The company name becomes the Account Name field and serves as the dedupe key during import. We sequence Account import first in all SuperOffice migrations because every Contact requires an AccountId lookup at insert time. The Company-Contact relationship is resolved by matching the SuperOffice contact.associate_id foreign key against the Account ID produced during import.

1:1

Contact → Contact

SuperOffice Contact records map to Salesforce Contact with AccountId resolved from the Company mapping.

How it maps

For SuperOffice installations with a large raw-prospect list that was never attached to a Company, we hold those records in a reconciliation queue and map them to Salesforce Lead with the source field set to 'SuperOffice Import'. Name, email, phone, postal address, and all userDefined custom fields migrate with type-mapped Salesforce field equivalents.

1:1

Sale (Deal) → Opportunity

SuperOffice Sale records map to Salesforce Opportunity.

How it maps

The sale.sale_type_id links to the SaleType list table and becomes the Salesforce Record Type and Sales Process. Sale stage maps to StageName, amount to Amount, close date to CloseDate, and sale_reason to a custom Loss Reason field. We configure the Sales Process and stage values in Salesforce Sandbox before migration to ensure the stage mapping is valid at insert time.

configuration

Sale Stage (SaleType) → Opportunity Stage

SuperOffice pipeline stages are tied to the SaleType list table.

How it maps

We export each SaleType as a stage configuration object (name, order, probability percentage, open/closed flag) and apply it as a Salesforce Sales Process with corresponding StageName values. Stage probability percentages round to the nearest Salesforce-allowed integer.

1:1

Quote → Quote

SuperOffice Quote maps to Salesforce Quote, which is available as a standard object from Salesforce Sales Cloud Professional.

How it maps

The Quote object links to the Opportunity via OpportunityId, preserves the QuoteNumber, expiration date, and billing/shipping address. Line items migrate as OpportunityLineItem records after Pricebook2 and Product2 records are created.

configuration

QuoteAlternative → Custom Field (JSON blob)

SuperOffice Quotes have one or more QuoteAlternative versions with independent line items, discount rates, and earning fields.

How it maps

Salesforce Quote has a single-level line item structure with no native Alternative concept. The primary QuoteAlternative becomes the live Salesforce Quote; secondary alternatives are serialized as a JSON structure and stored in a custom field quote_alternatives__c on the Quote. The post-migration handoff document lists each Quote with more than one alternative so the customer admin can decide whether to recreate them as separate Quotes.

What moves14 objects
SuperOffice CRMSalesforce
  • CompanyAccount1:1
  • ContactContact1:1
  • SaleOpportunity1:1
  • Sale StageOpportunity Stagetransformed
  • QuoteQuote1:1
  • QuoteAlternativeCustom Fieldtransformed

+ 8 more in the mapping below

How SuperOffice CRM 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.

DimensionSuperOffice CRMSalesforce
Contact vs Lead vs Account modelSingle Contact linked to Company as the primary relationshipSeparate Lead (unqualified), Contact (qualified, attached to Account) objects with explicit Convert action
Sales automation feature coverage85% of 246 sales force automation features supported100% of 246 sales force automation features supported with no gaps
Marketing automation depth67% feature coverage with 85 unrated features98% feature coverage from a dedicated marketing cloud layer
Reporting flexibilityStandard dashboards; custom reports require consultant involvementReport Builder with cross-object formulas, joined reports, and Einstein Analytics from Professional tier
Custom objectsStandard objects across all tiers; no formal custom object constructFull custom object (__c) support from Professional tier without setup fees
Document storage modelDocument archive linked via section-tab associationsContentDocument and ContentVersion objects with ContentWorkspace libraries
Quote structureQuote → QuoteAlternative → line items (multi-version per sale)Single-level Quote with one set of line items per Opportunity

What to watch for in a SuperOffice CRM to Salesforce migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Lead-Contact split requires pre-migration design

SuperOffice Contact records have no built-in qualification status; every Contact lives in the same object regardless of where it is in the buyer's journey.

How we handle it

Salesforce expects unqualified prospects as Leads and qualified buyers as Contacts attached to Accounts. We define the split rule during scoping — typically Contacts with a closed-won Sale become Contacts, and Contacts without any associated Sale become Leads — and apply it as the first transform before any record insert. Migrations that skip this step create orphaned Contacts with no AccountId or Leads that should have been Contacts, both of which require manual cleanup after cutover.

high

Quote Alternatives flatten to a single version in Salesforce

SuperOffice Quotes support multiple QuoteAlternative versions per sale, allowing sales teams to present different technology approaches, pricing tiers, or side-effect comparisons to the same buyer.

How we handle it

Salesforce Quote has a single-level structure with one set of line items per Opportunity. The primary QuoteAlternative maps directly to Salesforce Quote; additional alternatives serialize to a JSON custom field on the Quote. The post-migration handoff lists every Quote with multiple alternatives so the admin can decide whether to recreate them as separate Quotes, Salesforce Opportunity Products with a custom Alternative Name field, or a CPQ tool from AppExchange.

high

SuperOffice Workflows and CRM scripts do not migrate to Salesforce Flow

SuperOffice Workflows, CRM scripts, and any on-premises macros built for custom screens have no direct Salesforce Flow equivalent.

How we handle it

Salesforce Flow uses record-triggered, scheduled, and screen variants with different trigger models, action types, and governor limits. We do not migrate automations as code. We deliver a written inventory of every active SuperOffice Workflow and CRM script with its trigger conditions, actions, and recommended Salesforce Flow rebuild, and the customer's admin or a Salesforce partner reconstructs them post-migration.

medium

Activity history at scale exceeds CSV loader capacity

SuperOffice environments with multi-year engagement histories can contain hundreds of thousands of calls, tasks, and appointments.

How we handle it

Salesforce's Data Loader and Data Import Wizard cannot handle volumes above approximately 50,000 records per import run and do not support Task and Event object relationships (WhoId, WhatId) natively. We use the Salesforce Bulk API 2.0 with batch chunking, parent-record lookup resolution (WhoId to Contact or Lead ID, WhatId to Account or Opportunity ID), and exponential backoff on rate-limit responses. Activity timestamps preserve the original SuperOffice ActivityDate ordering on the Salesforce timeline.

medium

Duplicate email addresses in associate table block user migration

The SuperOffice Admin client enforces a unique-email constraint on User (associate) records.

How we handle it

Before migration, we scan the associate table for duplicate emails, resolve each conflict with the customer's admin (typically by disabling one account or assigning a secondary email), and require the duplicate list to be cleared before the User migration phase begins. Records without an email address also cannot map to a Salesforce User and are held in the reconciliation queue. This pre-migration cleanup step is the most common cause of migration delays in SuperOffice on-premises to cloud moves.

How the migration runs

  1. Discovery and pre-migration audit

    We audit the source SuperOffice installation across version (7.1 minimum required for Online Migration Tool compatibility), object inventory (Contacts, Companies, Sales, Projects, Quotes, Activities, Documents, Selections, Custom Properties), engagement volume per object, active Workflow count, active CRM script count, and associate table integrity (duplicate emails, inactive users, Travel user accounts).

    What this step covers

    We pair this with a Salesforce edition recommendation: Professional ($80/user) covers most SuperOffice migrations with no custom objects; Enterprise ($165/user) is required for record-triggered Flow at scale, advanced forecasting, or multi-currency; Unlimited ($330/user) only if 24x7 support and full API access for custom development are needed. The discovery output is a written migration scope and a data cleanliness report with remediation tasks.

  2. Destination schema design and Sandbox validation

    We design the destination schema in Salesforce.

    What this step covers

    This includes provisioning Project__c as a custom object (if the destination org does not have Salesforce Project Management), all custom fields from SuperOffice userDefined tables, Record Types and Sales Processes per SuperOffice pipeline, and QuoteAlternative handling (primary as Quote, secondary serialized). Schema is deployed into a Salesforce Full Copy Sandbox via metadata API for validation before any data moves. We also define the Lead-Contact split rule during this phase based on the customer's Contact-to-Sale association data.

  3. Sandbox migration and reconciliation

    We run a full migration into the Salesforce Sandbox using production-like data volume.

    What this step covers

    The customer's RevOps lead reconciles record counts (Accounts in, Contacts in, Leads in, Opportunities in, Projects in, Activities in, Quotes in), spot-checks 25-50 random records against the SuperOffice source, validates Activity association chains (Contact-to-Account, Task-to-WhoId), and reviews the Quote-Alternative JSON output for completeness. The admin signs off the schema and mapping before production migration begins. All corrections happen in Sandbox, not production.

  4. Owner and User reconciliation

    We extract every distinct SuperOffice associate referenced on Contact, Company, Sale, Activity, and Document records and match by email against the Salesforce destination org's User table.

    What this step covers

    Associates without a matching User go to a reconciliation queue. The customer's Salesforce admin provisions any missing Users and assigns the appropriate Profile and Permission Set (or flags the User as inactive if the original associate is no longer active in SuperOffice). Migration cannot proceed past this step because OwnerId references are required on most standard Opportunity and ContentDocument records.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from SuperOffice Companies), Contacts and Leads (with the split applied), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Projects__c, Product2 and Pricebook2 entries, OpportunityLineItem and Quote records, Activity history (Tasks and Events via Bulk API 2.0), Documents (ContentVersion via Bulk API), and Tags (as multi-select picklist values).

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins. Quote Alternatives are serialized after the primary Quote line items are committed.

  6. Cutover, validation, and Workflow rebuild handoff

    We freeze SuperOffice write access during cutover, run a final delta migration of any records modified during the migration window, then enable Salesforce as the system of record.

    What this step covers

    We deliver the Workflow and CRM script inventory document to the customer's admin team. We support a one-week hypercare window where we resolve any reconciliation issues raised by the sales team. We do not rebuild SuperOffice Workflows as Salesforce Flow inside the migration scope; that is a separate engagement or an internal admin task.

SuperOffice CRM Salesforce
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · SalesforceRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

4-8 weeksTypical, smaller accounts
12-20 weeksLarge or heavily customised accounts

A quote scales with record volume, custom object count, Project complexity, and document archive size. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for SuperOffice CRM to Salesforce →

Why teams move from SuperOffice CRM to Salesforce

  • Salesforce covers 100% of sales force automation features versus SuperOffice's 85%, with no unrated items. Feature gaps in opportunity tracking, sales forecasting, pipeline analysis, CPQ, and sales methodology enforcement are cited in comparative reviews as the point where growing B2B teams outgrow SuperOffice and move to Salesforce for deeper pipeline control without requiring consultant-configured workarounds.
  • SuperOffice's marketing automation covers just 67% of features with 85 unrated items, leaving large gaps in campaign management, lead scoring, and A/B testing. Companies running HubSpot alongside SuperOffice or planning to unify marketing and sales operations move to Salesforce's ecosystem because Marketing Cloud and Marketing Cloud Account Engagement integrate natively at the platform level rather than through third-party connectors.
  • SuperOffice's reporting is built around standard templates; custom reports beyond those templates require consultant involvement or manual workarounds. Enterprise revenue operations teams cite Salesforce's Report Builder with cross-object formulas, joined reports, and Einstein Analytics as the primary driver for switching when they need multi-dimensional pipeline analysis across territories, product lines, and non-standard attribution models that SuperOffice cannot support without external help.
  • SuperOffice's document archive and Quote-Alternative hierarchy reflect a data model that has no direct Salesforce equivalent. As teams scale, the inability to store multi-version quotes, map Projects to standard objects, or reconstruct dynamic Selections as filterable views forces admin workarounds that erode confidence in the CRM as a single source of truth. Salesforce's native ContentDocument model and custom object flexibility eliminate these workarounds at scale.
  • Performance degradation on large datasets during peak periods (quarter-end, marketing campaign response windows) forces SuperOffice users to split attention between the CRM and spreadsheets. Salesforce's cloud infrastructure handles larger data volumes natively, and the Bulk API 2.0 separates migration traffic from interactive usage so that cutover periods do not affect day-to-day operations for the migrating team.

Questions, answered

SuperOffice CRM to Salesforce migration questions

How long does a SuperOffice CRM to Salesforce migration take?

Straightforward migrations under 30,000 Contacts and 8,000 Sales with no custom objects land between four and eight weeks. Migrations with Projects, Quote-Alternative structures, large document archives, multiple Selections, or large engagement histories (over 500,000 activity records) move to twelve to twenty weeks because of Bulk API time, ContentDocument migration overhead, and the Project-type configuration phase. The pre-migration duplicate-email remediation on the associate table can add one to two weeks if the conflict list is large.

Do SuperOffice Workflows and CRM scripts migrate to Salesforce Flow?

No. SuperOffice Workflows, CRM scripts, and any macros built for custom screens have no direct Salesforce Flow equivalent because they use different trigger models, action types, and governor limits. We do not migrate them as code. We deliver a written inventory of every active SuperOffice Workflow and CRM script with its trigger conditions, actions, and a recommended Salesforce Flow rebuild. The customer's admin or a Salesforce partner reconstructs them post-migration. We do not migrate SuperOffice Sequences either; these require a sales engagement tool such as Salesloft, Outreach, or Sales Engagement within Salesforce.

Can we keep SuperOffice Service while moving Sales to Salesforce?

This is possible but requires a deliberate hybrid strategy. SuperOffice Service handles ticketing and customer service; Salesforce Sales Cloud does not include native service desk capabilities. If the customer moves both sales and service, Salesforce Service Cloud is the destination. If the customer moves only sales to Salesforce and retains SuperOffice for service, the two systems remain separate with no native bidirectional sync. We recommend a single CRM for long-term data consistency, but if the hybrid is necessary, we migrate the sales stack to Salesforce and deliver a SuperOffice Service export for the customer's service team to manually reconcile.

Do we lose historical activity data (calls, tasks, appointments)?

No. We migrate the full engagement history through the Salesforce Bulk API 2.0 with parent-record resolution. Calls land as Task with TaskSubtype=Call; standard tasks land as Task with Status, Priority, and ActivityDate preserved; appointments land as Event records with StartDateTime, EndDateTime, and Location. Activity timestamp ordering is preserved by setting ActivityDate and Event StartDateTime to the original SuperOffice timestamp. Activity associations to Contact, Company, and Sale are reconstructed using SuperOffice associate table IDs resolved to Salesforce IDs at migration time.

How are SuperOffice Selections handled in Salesforce?

SuperOffice Selections are named dynamic lists with filter criteria stored in the Selection_criteria table. Salesforce has no native dynamic list equivalent. We export each Selection as a static set of record IDs and apply the Selection name as a custom tag or multi-select picklist value on each record. The post-migration handoff document lists every Selection with its original filter criteria, record count, and the tag value applied so the customer's admin can rebuild them as Salesforce Reports with saved filters or as List Views.

What happens to our SuperOffice document archive during migration?

SuperOffice documents export as binary files with metadata (filename, created date, section-tab link). We migrate them as Salesforce ContentVersion records with the file body, title, and a ContentDocumentLink to the parent Contact, Account, or Opportunity based on the original section-tab assignment. Documents linked to SuperOffice records that were not migrated (inactive users, cancelled Projects) link to a custom Unresolved_Reference__c Account as a documented holding point. The customer's admin reviews these unresolved links during the hypercare window and redirects them to the correct records.

Get a quote

Moving from SuperOffice CRM 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