Migrate from SuiteDash to Salesforce Sales Cloud

SuiteDash Contact records map to Salesforce Contact if the contact has an associated Company in SuiteDash (becoming a Contact tied to a Salesforce Account). Contacts without a company association or with a 'lead' classification map to Salesforce Lead. We preserve the original SuiteDash contact ID in a custom field sd_contact_id__c on both Lead and Contact for reconciliation. Custom fields at the Contact scope map to identically named custom fields on both Lead and Contact so the data is not lost regardless of split outcome.

SuiteDash Company records with Public custom fields map to Salesforce Account. The Company name becomes Account Name, and Public-scoped custom fields map to Account custom fields. Account is created before any Contact import so the AccountId lookup is satisfied at insert time. We extract the Company domain and store it in Account Website for deduplication against existing Salesforce Accounts.

SuiteDash Company Private custom fields are visible only to the Primary Contact and are not exposed via Dynamic Data Placeholders. During scoping, we identify every Private-scoped Company field and decide with the customer whether each maps to a Salesforce custom field on Account (visible to all with field-level security restriction to the account owner) or to a private Note attached to the Account. Private fields that cannot be represented with an equivalent visibility boundary are flagged for manual review before migration.

SuiteDash Deals map to Salesforce Opportunity with the pipeline stage mapping to a Salesforce Sales Process or Record Type. We preserve the deal amount, close date, probability (if set), and owner. The sd_deal_id__c custom field holds the SuiteDash deal ID for post-migration reconciliation. Deals without an associated Company are flagged during scoping because Salesforce Opportunity requires an AccountId; these are assigned to a placeholder Account or held for manual Account assignment.

SuiteDash's configurable pipeline stages map to Salesforce Opportunity StageName values within a Salesforce Sales Process. We map stage order and probability percentages during scoping, deploy the Sales Process to the destination org's Setup before migration, and validate that every SuiteDash stage name has a Salesforce equivalent before the first Opportunity record is inserted.

SuiteDash Projects with custom fields and task hierarchies export as linked sets. We create a Salesforce custom object Project__c with custom fields mirroring the SuiteDash Project schema, and child Tasks linked via WhatId. If the destination org is Sales Cloud-only without a project management layer, Projects migrate as Project__c records with related Tasks and custom fields, and the customer configures the project visibility model post-migration.

SuiteDash Support Tickets map to Salesforce Case if Service Cloud is present in the destination org. Ticket status maps to Case Status, priority maps to Case Priority, and conversation threads migrate as EmailMessage records linked to the Case. Custom fields on SuiteDash tickets map to Case custom fields. If the destination org has no Service Cloud license, Cases are loaded into a custom object and the customer can enable Service Cloud separately.

SuiteDash Invoice records migrate as Salesforce custom object Invoice__c records with line items as child Invoice_Line_Item__c records. Historical paid invoices transfer as records only; active or pending invoices require the customer to freeze billing changes during cutover because payment processor state, partial payments, and tax edge cases do not port. Invoice Custom Fields are a separate schema from CRM Custom Fields and are discovered via SuiteDash's Invoice API endpoints during scoping, not via GET /contact/meta.

SuiteDash Staff records map to Salesforce User records by email match. Role assignments, staff-level custom fields, and the staff member's association with Deals, Projects, and Tickets transfer as the Salesforce OwnerId reference on the migrated records. Staff without a matching Salesforce User are placed in a reconciliation queue for the customer's admin to provision before the record import resumes. Inactive or archived SuiteDash staff map to Salesforce Users with IsActive=false.

SuiteDash Appointments map to Salesforce Event records with StartDateTime, EndDateTime, Location, and Description preserved. Attendees are linked via EventRelation records pointing to the resolved Contact or Lead. Bidirectional calendar sync settings (Google Calendar, Outlook) do not port; booking page configurations require manual reconfiguration in Salesforce Scheduling or a third-party booking tool.

SuiteDash engagement records (call logs, email history, meeting records, tasks, and notes) migrate to Salesforce Task, Event, EmailMessage, and Note objects. Calls map to Task with TaskSubtype=Call and CallDurationInSeconds preserved. Emails map to EmailMessage records linked to a Timeline Task. Meetings map to Event with EventRelation records for attendees. Activity ordering is preserved by setting ActivityDate to the original SuiteDash timestamp. Engagement migration uses Salesforce Bulk API 2.0 with batch chunking and parent-record lookup resolution (WhoId, WhatId) because record counts typically exceed CSV loader capacity.

SuiteDash freeform Tags on Contacts and Companies migrate to a multi-select picklist custom field on the target Salesforce object (Lead, Contact, Account). During scoping, we confirm whether the customer wants a single consolidated tag field or separate tag fields per entity. Tags used for segmentation logic are documented so the customer can rebuild equivalent segments in Salesforce Reports or List Views.

SuiteDash custom fields exist at six scopes and are discovered via GET /contact/meta for CRM fields and Invoice API endpoints for Invoice Custom Fields. We map each scope to the equivalent Salesforce field on the target object and configure field-level security to approximate the original visibility boundary. Company Private fields require special handling (see Company Private scope mapping). Invoice Custom Fields are discovered separately and mapped to Invoice__c custom fields. Fields with unsupported types (e.g., SuiteDash-specific Dynamic Data Placeholder types) are flagged for manual mapping before migration.

SuiteDash Organization-level custom fields and white-label settings (branding, logo, custom domain, role definitions) are account-scoped and do not have a direct Salesforce equivalent in Sales Cloud. We document the Organization settings as a written configuration checklist so the customer can reapply branding in Salesforce Experience Cloud (if licensed) and reconfigure role hierarchies in Salesforce Setup manually.

SuiteDash Automations use trigger-action sequences with internal Contact IDs, Company IDs, and Staff IDs that are not stable post-migration. We do not migrate Automations as code. We produce an Automation Audit Report listing every active automation with its trigger, conditions, actions, owner, and failure mode, plus a recommended Salesforce Flow equivalent for each. The customer's Salesforce admin or a certified Salesforce partner rebuilds automations post-migration.