Migrate from SuperOffice CRM to Salesforce Sales Cloud

SuperOffice Company records map directly to Salesforce Account. 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.

SuperOffice Contact records map to Salesforce Contact with AccountId resolved from the Company mapping. 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.

SuperOffice Sale records map to Salesforce Opportunity. 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.

SuperOffice pipeline stages are tied to the SaleType list table. 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.

SuperOffice Quote maps to Salesforce Quote, which is available as a standard object from Salesforce Sales Cloud Professional. 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.

SuperOffice Quotes have one or more QuoteAlternative versions with independent line items, discount rates, and earning fields. 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.

SuperOffice Project records with type and status from ProjType and ProjStatus list tables map to a Salesforce custom object Project__c if the destination org does not have Salesforce Project Management (a separate license). We pre-create the Project__c schema including type and status custom picklist fields that mirror the SuperOffice list values. Project links to Account or Opportunity migrate as custom lookup fields on Project__c.

SuperOffice Activities (calls, tasks, appointments) linked to Contact, Company, or Sale map to Salesforce Task (for calls and tasks) and Event (for appointments). We preserve timestamps in ActivityDate/StartDateTime, duration, and completion status. Activity associations to other objects are reconstructed using the associate table's SuperOffice record IDs resolved to Salesforce IDs at migration time.

SuperOffice Users (associates) with an email address map to Salesforce User records by email match. Role information (module-level access rights) migrates as a custom Role__c text field on User because Salesforce's profile and permission set model does not map directly to SuperOffice's role structure. Users without an email address or with duplicate email addresses are held in a reconciliation queue for the admin to resolve before record migration resumes.

SuperOffice documents stored in the document archive export as binary blobs with metadata (filename, created date, author, section-tab assignment). We migrate them as Salesforce ContentVersion records (file body, title, version data) with a ContentDocumentLink to the parent record (Contact, Account, or Opportunity) based on the original section-tab link. If SuperOffice's document archive references a record that was not migrated, the document links to a custom Unresolved_Reference__c Account as a holding point.

SuperOffice userDefined table entries on Contact, Company, Sale, and Project migrate as Salesforce custom fields on the equivalent object. We pre-create all custom fields in the destination Salesforce org before data import, using type mapping (SuperOffice date to Salesforce Date, integer to Number, text to Text) and preserving picklist values as Salesforce picklist values where applicable. Dropdown list dependencies must be recreated as Salesforce picklist restricted values by the admin before migration.

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

SuperOffice tags applied across Contact, Company, Sale, and Project objects migrate to a Salesforce custom multi-select picklist field (Tags__c) on the corresponding object. We deduplicate the tag namespace and preserve all tag assignments per record. If the customer uses more than 500 distinct tags, we recommend a Salesforce custom object Tags__c with a junction object to avoid multi-select picklist length limits.

SuperOffice supports multiple named Sale pipelines with independent stage sets. Each SuperOffice pipeline maps to a Salesforce Opportunity Record Type with a corresponding Sales Process that whitelists the pipeline-specific stage values. Page Layouts are assigned per Record Type so that stage values remain scoped per pipeline. We configure all Record Types and Sales Processes in the destination Salesforce org before migrating any Opportunity records.