Extract via the Samanage REST API, transform to Salesforce's Case-based data model, load in dependency order using Bulk API 2.0, and run a delta sync at cutover. Budget 3–8 weeks depending on scope.
Migrating from SolarWinds Service Desk (SWSD) to Salesforce Service Cloud requires a full data model conversion, not a simple lift-and-shift, as no native migration path exists between the two platforms. SWSD is built on the Samanage REST API using a flat, ITIL-centric model with shallow nesting, while Salesforce organizes support data across a deep relational object graph of Account, Contact, Case, EmailMessage, ContentDocumentLink, and ContentVersion records. Every parent-child relationship must be explicitly reconstructed using external ID matching, and SWSD's incident-comment-attachment structure must be decomposed into Salesforce's Case plus CaseComment or EmailMessage plus ContentVersion hierarchy. Automation rules, SLA policies, and workflow triggers have no migration path and must be fully rebuilt in Salesforce Flow, Entitlements, and Milestones.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Quick answer
This migration is medium complexity for incident-only moves (2–3 weeks) and high complexity when CMDB, change management, and knowledge base are in scope (4–8+ weeks). The hardest part is not the data transfer — it's the data model conversion. SWSD's incident-comment-attachment model must be decomposed into Salesforce's Case + CaseComment/EmailMessage + ContentVersion structure, with all parent-child relationships rebuilt using external ID matching. Automation rules, SLA policies, and workflow triggers cannot be migrated — they must be rebuilt in Salesforce Flow, Entitlements, and Milestones. Use Bulk API 2.0 for record loading (supporting up to 100 million records per 24-hour period), and always rely on External IDs for relationship mapping to avoid needing Salesforce 18-character ID lookups at load time.
Case vs. CSIM Incident decision
If your SWSD instance was primarily used for external customer support or general HR/Facilities ticketing, the Case object is the better fit — it natively integrates with Salesforce Entitlements, Milestones, and Omni-Channel routing. If you require strict ITIL object separation with native Incident, Problem, and ChangeRequest objects, evaluate CSIM (available on Service Cloud licenses from API v57.0 onward). The practical tradeoff: CSIM objects have less AppExchange ecosystem coverage and fewer native integrations than Case as of 2025. Most migrations land on Cases with Record Types for ITIL differentiation.
Incremental extraction
Use the updated_at filter to pull only records modified after your last extraction run. This is essential for the delta sync before cutover: GET /incidents.json?per_page=200&updated_at_gte=2026-07-01T00:00:00Z
CreatedDate preservation
By default, Salesforce sets CreatedDate to the timestamp of record insertion, not the original record creation date. To preserve original creation dates, you must enable "Set Audit Fields upon Record Creation" in Setup → User Interface. This is a per-profile permission that must be activated before the data load begins. If you forget this step, every migrated record will reflect the migration date rather than its original date — and correcting this requires a complete data reload. Confirm this permission is active before running any load job.
Picklist value mismatches
SWSD allows freeform text values in some fields (category, state). Salesforce picklist fields reject values not defined in the picklist configuration — records with unmapped values will either fail insertion or silently null the field depending on your API error handling settings. Build a complete value mapping table before your first load attempt. Pay particular attention to SWSD custom states such as "Pending Vendor," "Awaiting Parts," or "Escalated" — none of these exist in the Salesforce default Status picklist and must be added to the picklist definition in Setup before loading.
HTML content sanitization
SWSD article bodies frequently contain HTML. Salesforce Knowledge Rich Text fields support a subset of HTML tags — unsupported tags (<script>, <iframe>, <style>, custom CSS classes) are silently stripped on save, which can break article formatting. Run a sanitization pass using an HTML parser (Python's bleach library or equivalent) to strip unsupported tags and convert inline styles to Salesforce-compatible equivalents before loading. Test a representative 50-article sample against your org before running the full knowledge migration.
ContentVersion constraint
Binary file uploads cannot use Bulk API. Each attachment must be uploaded individually via the REST API. For 10,000 attachments averaging 500KB each, budget 3–5 hours of upload time at typical API throughput. This is frequently the longest phase of the entire migration and is commonly underestimated by 2–3x.
Salesforce file storage costs
Salesforce file storage is allocated at 10GB per org plus 2GB per full user license, with additional storage purchased at approximately $5 per GB per month (pricing as of 2025). Audit your SWSD attachment inventory before migrating. Filter out attachments under 10KB, common image types used as email signatures (logo.png, signature.jpg, banner images), and files older than your data retention policy. For a dataset with 500GB of attachments, storage costs alone can exceed $2,500/month if migrated without filtering.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Establish why you are moving, what "done" means, and who signs off.
Objective A written scope with agreed success criteria, a named owner per workstream, and a budget approved by finance.
Keep these open
-
Pull the real numbers out of SolarWinds Service Desk
Export counts for tickets (open and closed separately), contacts, organisations, attachments, macros, triggers, automations, views and SLA policies. Note the oldest ticket date — history depth drives the whole timeline. Estimating from memory is the single most common cause of a blown migration window.
Data Profiler Get real record counts instead of estimating from memory -
Decide what history actually moves
Agree a cut-off with the support lead: all history, last 24 months, or open tickets plus a read-only archive. Every extra year of closed tickets adds API time and cost without adding much agent value. Get this in writing — it is the decision people relitigate mid-cutover.
A "move everything" default is what turns a two-week migration into a two-month one.
COI & ROI Calculator Build the 36-month business case you will need for sign-off -
Confirm Salesforce Service Cloud can hold your support model
Walk your current workflow through Salesforce Service Cloud: multi-brand, business hours, SLA targets, CSAT, side conversations, public vs internal notes, and any channel you depend on (voice, chat, WhatsApp, social). List anything with no native equivalent — those are project risks, not configuration details.
-
Build the business case
Model licence delta, migration effort, agent retraining, and the cost of staying put (Cost of Inaction). Executives approve a number, not a plan, and you will be asked for it again at the go/no-go.
Helpdesk Migration Planner Turn ticket volume into a dated SolarWinds Service Desk → Salesforce Service Cloud timeline -
Name owners and set the go/no-go date
One named owner each for data, configuration, integrations, and agent enablement, plus a decision-maker who can call a rollback. Put the go/no-go meeting in calendars now, 48 hours before the freeze.
SolarWinds Service Desk → Salesforce Service Cloud specifics
- CRM unification
- Organizations already running Salesforce Sales Cloud want support data in the same org. Having Cases, Accounts, Contacts, and Opportunities in one platform eliminates cross-system syncing and gives agents full customer context without switching tools. A customer issue logged by Sales can transition to an IT incident without webhook integrations.
- Advanced case routing
- SWSD supports basic assignment rules. Salesforce Omni-Channel provides skills-based routing, capacity-based assignment, and presence-aware distribution across channels (email, chat, phone, messaging).
- Entitlement and SLA management
- SWSD has SLA management, but Salesforce Entitlements and Milestones offer multi-tier SLA structures with per-customer and per-product entitlement rules — critical for B2B support organizations managing different contractual SLAs per account.
- Automation depth
- Salesforce Flow supports complex branching, subflows, scheduled paths, and platform events — substantially beyond SWSD's trigger-action rule model. Einstein for Service adds case classification, recommended replies, and knowledge suggestions natively without additional configuration.
- Custom object extensibility
- While SWSD allows custom fields, Salesforce allows entirely custom relational objects with their own page layouts, validation rules, and API access — making it easier to build bespoke asset tracking or compliance modules that integrate natively with Cases.
Don't move on until
- Record counts confirmed for tickets, contacts, organisations and macros
- Success criteria signed off by the support lead
- Freeze window provisionally booked with the business
02 Data Audit Find out what is actually in the data before you try to move it.
Objective A profiled, cleaned export with every quality defect either fixed at source or explicitly accepted.
Keep these open
-
Take a full SolarWinds Service Desk export and profile it
Export to CSV or JSON and profile every file: row counts, null rates per column, distinct values, and type consistency. Compare row counts against the API totals from Discovery — a gap here means your export is silently truncated, usually by pagination.
Data Profiler Profile the SolarWinds Service Desk export for nulls, outliers and type drift -
Validate file structure before anyone writes a transform
Check delimiters, quoting, encoding (expect UTF-8, watch for BOMs and Latin-1), duplicate headers, and embedded newlines in ticket bodies. Ticket descriptions with raw newlines and commas break naive CSV parsers and silently shift columns.
A single unescaped quote in one ticket body can shift every subsequent column without any error.
CSV Validator Catch broken headers and ragged rows in the raw export -
Inventory PII and set retention
Scan for emails, phone numbers, payment card fragments, national IDs and anything else regulated in ticket bodies and custom fields — support tickets are where customers paste things they should not. Decide what gets migrated, masked, or dropped, and record the legal basis.
Ticket bodies and attachments routinely contain card and ID data that never appears in a structured field.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Quantify duplicates, orphans and dead references
Count duplicate contacts (same email, different casing), tickets whose requester no longer exists, organisations with no members, and attachments whose parent ticket is gone. Fix these in SolarWinds Service Desk where you can — migrating them just moves the mess.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Clean and normalise the export
Trim whitespace, drop empty rows and columns, normalise casing on emails and tags, and standardise every timestamp to UTC ISO 8601. Timezone drift is invisible at load time and shows up weeks later as SLA reports nobody can reconcile.
-
Produce a masked copy for sandbox work
Generate a realistic but fake version of the export for testing and for any vendor who needs sample data. Loading real customer PII into a sandbox is a breach in most jurisdictions, and sandboxes are rarely covered by your DPA.
PII Masker Generate a safe copy for sandbox and vendor testing
Don't move on until
- Export parses cleanly with no ragged rows or encoding errors
- PII inventory complete and retention decisions recorded
- Duplicate and orphan records quantified and triaged
03 Field Mapping Turn two schemas into one signed-off mapping spec.
Objective A reviewed field-level mapping covering every object, with an explicit decision for every field that has no target.
Keep these open
-
Generate the first-pass SolarWinds Service Desk → Salesforce Service Cloud field map
Start from an automated match on both schemas, then review every row by hand. Automated matching gets the obvious 70% right and is confidently wrong on the rest — especially anything named "type", "status" or "custom_field_1".
Schema Mapper Opens pre-loaded with the SolarWinds Service Desk → Salesforce Service Cloud field pair -
Map status, priority and channel values, not just field names
Enumerate every value in each picklist on both sides and map them explicitly. Value-level mismatches are the defect class that survives all the way to production because the field itself mapped fine — a ticket that should be "Pending" arriving as "Open" reopens SLA clocks.
Statuses with no target equivalent (on-hold, pending-customer) need a policy decision, not a best guess.
-
Decide how custom fields land
Create the target custom fields first, matching type exactly (a dropdown mapped to free text can never be mapped back). Where Salesforce Service Cloud has no equivalent, decide between a new custom field, a tag, or a note appended to the ticket body — and record which.
-
Resolve identity and threading
Decide how source IDs are preserved — most platforms will not let you set the primary key, so keep the original ID in a custom field. Without it, reconciliation becomes fuzzy matching and every future support question about an old ticket is unanswerable.
Losing the original ticket ID makes reconciliation and rollback effectively impossible.
-
Plan attachments, inline images and threading order
Confirm size limits, allowed MIME types, and whether inline images survive as attachments or need rehosting. Decide the comment ordering and author attribution rules: comments loaded out of order, or all attributed to the API user, destroy the conversation history agents rely on.
-
Freeze and sign off the mapping spec
Version the spec, walk the support lead through it row by row, and get explicit sign-off. Any change after this point goes through change control — mid-flight mapping edits are how partial loads happen.
Don't move on until
- Every source field is mapped, deliberately dropped, or parked in a custom field
- Status, priority and channel value maps agreed with the support lead
- Mapping spec version-controlled and signed off
04 Test Migration Prove the pipeline on a small, representative slice.
Objective A pilot load into a Salesforce Service Cloud sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Salesforce Service Cloud sandbox that matches production config
Create the custom fields, groups, brands, business hours and SLA policies first. A pilot into a default sandbox tests nothing, because the failures you care about are all configuration mismatches.
-
Pick a deliberately nasty pilot sample
Take 500-1000 records chosen for difficulty, not convenience: the longest ticket threads, tickets with the most attachments, non-Latin character sets, merged and split tickets, deleted requesters, and every status value. A clean random sample proves only that easy records are easy.
-
Run the load with masked data and instrument everything
Log every API request and response with its source record ID. When 40 records fail out of 10,000 you need to know exactly which ones and why, without re-running the whole batch.
PII Masker Never load real customer PII into a sandbox -
Measure real throughput against the rate limit
Record achieved records-per-hour under Salesforce Service Cloud's actual rate limits, including retries and backoff. Extrapolate to the full volume: if the maths says the full load exceeds your freeze window, you fix that now, not on cutover night.
Published rate limits are ceilings, not throughput. Assume real-world rates are meaningfully lower once retries and backoff are counted.
-
Reconcile the pilot and triage every failure
Diff source against target on record counts and field-level values. Every discrepancy gets a root cause and a fix — "probably fine" at pilot scale becomes thousands of broken records at full scale.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Put real agents in front of the pilot data
Have two or three agents work sample tickets end to end in the sandbox. They find the things reconciliation cannot see: unreadable threading, missing context, macros that no longer make sense. Fix the mapping, then re-run.
Don't move on until
- Pilot batch reconciles to 100% on record counts
- Agents have reviewed sample tickets and confirmed they are workable
- Measured throughput extrapolates to a viable full-load window
05 Cutover Execute the switch inside a controlled, reversible window.
Objective All in-scope data live in Salesforce Service Cloud, agents working in the new system, and a rollback path that stayed available throughout.
Keep these open
-
Pre-load history before the freeze
Load closed tickets and contacts days or weeks ahead while SolarWinds Service Desk stays live. Only open tickets and the final delta need to move inside the freeze — this is the single biggest lever on window length.
Helpdesk Migration Planner Size the freeze window from Salesforce Service Cloud's real API limits -
Publish the runbook with times, owners and abort criteria
A timed sequence: freeze start, final export, delta load, channel switch, smoke test, go/no-go, agent switch. Name who does each step and the explicit condition that triggers a rollback. Decide the abort criteria before the night, when nobody wants to be the one to call it.
-
Freeze SolarWinds Service Desk and take the final delta
Stop new ticket creation, let agents finish in-flight replies, then export everything changed since the pre-load. Announce the freeze to the whole business, not just support — someone always tries to raise a ticket during it.
Tickets created during an unenforced freeze land in the old system and are the most common source of permanently lost data.
-
Load the delta and open tickets
Run the delta load, then reconcile counts before touching any channel. Do not repoint email until the delta has verified — an inbound ticket arriving mid-load is far harder to untangle than a few extra minutes of freeze.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint channels and verify with live traffic
Switch email forwarding and MX or connector settings, update chat widgets and web forms, and re-authorise integrations. Then send real test tickets through every channel and confirm each lands, routes and triggers the right automation.
Email forwarding changes can take up to a full DNS TTL to propagate — check the TTL days in advance and lower it if needed.
Cron Expression Builder Schedule the delta syncs that run through the freeze -
Run the go/no-go and switch the agents
Walk the exit criteria with the decision-maker, call it explicitly, then move agents over with a named person on hand for the first few hours. Keep SolarWinds Service Desk read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
Don't move on until
- Full historical load complete and counts matched
- Inbound channels repointed and verified with live test tickets
- Rollback decision point passed explicitly, not by default
06 Validation Prove the migration is complete, then close it out.
Objective Documented evidence that data, workflow and reporting all survived, and a signed acceptance.
Keep these open
-
Run the full reconciliation
Compare source and target on every object: total counts, counts by status, counts by group, attachment counts, and field-level spot checks on a random sample. Produce one report you can hand to an auditor.
Migration Validation Tool Reconcile SolarWinds Service Desk and Salesforce Service Cloud record-for-record -
Verify field completeness, not just record counts
Re-profile the loaded data and compare null rates per field against the source profile. Matching record counts with a field that silently arrived empty is the failure mode counts alone will never catch.
Data Profiler Prove field completeness held up through the load -
Rebuild reporting and compare against baselines
Recreate your core dashboards — volume, first response time, resolution time, CSAT — and compare to pre-migration figures for the same period. Explain every variance; a changed SLA calculation is a real finding, not a rounding error.
SLA and first-response metrics are usually recalculated from the loaded timestamps, so they will differ if any timestamp mapping was approximate.
-
Test the workflow layer end to end
Fire every trigger, automation, SLA escalation, macro and notification with a live ticket. Workflow does not migrate — it gets rebuilt — so it is untested until someone has actually watched it run.
-
Confirm compliance and produce the audit trail
Re-scan the loaded data for regulated fields, confirm retention and deletion policies are configured in Salesforce Service Cloud, and file the evidence with your PII decisions from the audit phase.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Sign off, then decommission on a schedule
Get written acceptance against the Discovery success criteria. Keep SolarWinds Service Desk read-only for an agreed period (30-90 days is typical), take a final archive export, and only then cancel. Diarise the decommission date so it does not quietly renew.
SolarWinds Service Desk → Salesforce Service Cloud specifics
- Count verification
- Total records per object in SWSD must match totals in Salesforce. Use the SOQL queries in the load section above.
- State mapping check
- Verify SWSD custom states (e.g., "Pending Vendor") mapped correctly to Salesforce Case Status picklist values.
- Comment content check
- Spot-check at least 50 records across different time periods. Verify comment content is not truncated, particularly if CaseComment was used for any content over 3,500 characters.
- Attachment accessibility
- Open attachments on older closed tickets to confirm files are accessible and not corrupted. Verify ContentDocumentLink.ShareType is set correctly.
- Timestamp verification
- Confirm CreatedDate values on migrated Cases reflect original SWSD creation dates, not the migration run date.
Don't move on until
- Full reconciliation report attached to the project record
- Reporting baselines match pre-migration figures within agreed tolerance
- Formal acceptance signed and archive retention scheduled
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
ITSM Service Cloud
| SolarWinds Service Desk field | Salesforce Service Cloud field | Notes |
|---|---|---|
| Incident | Case (or CSIM Incident) | Direct map. SWSD state machine → Case Status picklist. CSIM Incident object (API name: Incident) provides native ITIL object separation. |
| Problem | Case (RecordType: Problem) or CSIM Problem | CSIM Problem object (API name: Problem) links to Incidents via ProblemIncident junction. Without CSIM, use a RecordType. |
| Change | Case (RecordType: Change) or CSIM ChangeRequest | CSIM ChangeRequest object (API name: ChangeRequest). Approval workflows must be rebuilt in Salesforce Approval Processes or Flow. |
| Release | No native equivalent | Archive or use a custom object. |
| User (requester) | Contact | SWSD users who submit tickets map to Contacts linked to Accounts. |
| User (agent/technician) | User | Salesforce Users require licenses. Map agent roles to Profiles and Permission Sets. |
| Group | Queue | SWSD groups map to Salesforce Queues for case ownership and routing. |
| Category / Subcategory | Case picklist fields | Map to Type, Reason, or a custom Category__c picklist. |
| Comment (on incident) | CaseComment or EmailMessage | Critical decision point — see section below. |
| Attachment | ContentVersion + ContentDocumentLink | Salesforce Lightning file model. Files must be uploaded as ContentVersion, then linked via ContentDocumentLink. |
| Knowledge Article | KnowledgeArticleVersion | Requires Knowledge to be enabled. Category mappings differ significantly. |
| Asset | Asset | Salesforce has a native Asset object, but it's designed for customer-facing product tracking, not ITSM configuration management. |
| Configuration Item | Asset or custom object | SWSD CMDB CI types with deep hierarchies need custom objects in Salesforce. |
| SLA Policy | Entitlement + Milestone | Cannot be migrated. Must be rebuilt manually in Setup. |
| Automation Rule | Flow / Assignment Rule | Cannot be migrated. Must be rebuilt. |
| Service Catalog Item | No direct equivalent | Use custom objects or integrate with Experience Cloud for self-service. |
Incidents Cases
Incidents map directly to Salesforce Cases or CSIM Incident objects with a clear status picklist conversion, making this the most straightforward entity to migrate.
| SolarWinds Service Desk field | Salesforce Service Cloud field | Notes |
|---|---|---|
| id | SWSD_Incident_Id__c | External ID. Integer → Text. Max 255 chars in Salesforce. |
| name (title) | Subject | Direct map. Max 255 chars. Truncate if needed. |
| description | Description | Long Text Area. Max 32,000 chars. Strip or preserve HTML per org policy. |
| state | Status | Value mapping required. See picklist note below. |
| priority | Priority | Value mapping: Critical/High/Medium/Low → Salesforce standard picklist values. |
| assignee | OwnerId | Map to Salesforce User or Queue ID. Requires user provisioning before Case load. |
| requester | ContactId | Resolve to Contact via SWSD_User_Id__c external ID. |
| category | Type or Category__c | Custom picklist recommended for multi-level categories. |
| subcategory | Subcategory__c | Custom picklist. Define all values before load. |
| number | Legacy_Ticket_Number__c | Store SWSD ticket number in a custom field. Salesforce auto-generates its own CaseNumber. |
| created_at | CreatedDate | Requires "Set Audit Fields upon Record Creation" permission — see above. |
| updated_at | LastModifiedDate | Same audit field permission required. |
| due_at | Due_Date__c | Custom DateTime field. |
| site | AccountId | Map SWSD site → Salesforce Account via SWSD_Site_Id__c external ID. |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Incidents | low | Incidents map directly to Salesforce Cases or CSIM Incident objects with a clear status picklist conversion, making this the most straightforward entity to migrate. |
| Comments | high | The 4,000-character CaseComment limit and HTML stripping behavior create a high risk of silent data loss unless each comment is evaluated and routed to the appropriate EmailMessage or CaseComment object. |
| Attachments | medium | Attachments require a two-step load into Salesforce as ContentVersion records followed by ContentDocumentLink associations, adding complexity and a failure point if parent records are not yet loaded. |
| Knowledge Articles | high | Knowledge must be explicitly enabled in the Salesforce org and category mappings differ significantly between SWSD and KnowledgeArticleVersion, requiring manual category restructuring before articles can be loaded. |
| Problems and Changes | medium | Problems and Changes can land on Cases with Record Types or CSIM objects, but the chosen approach must be decided before migration begins as it affects relationship mapping and downstream Entitlement integration. |
| Users and Contacts | medium | SWSD requesters must map to Contacts and agents to licensed Salesforce Users, requiring deduplication logic for any individual who held both roles and license provisioning for all historical active agents. |
| Assets | medium | Salesforce's native Asset object is designed for customer-facing product tracking rather than ITSM configuration management, meaning SWSD asset records may require field-level remapping or a custom object to preserve semantic accuracy. |
| CMDB Configuration Items | high | SWSD CMDB CI types with deep hierarchical relationships have no native Salesforce equivalent, requiring custom object design and relationship rebuilding that must be completed before CI data can be loaded. |
| SLA Policies | high | SLA policies cannot be migrated and have no automated conversion path; all entitlement rules and milestones must be manually rebuilt in Salesforce Setup before go-live. |
| Groups and Queues | low | SWSD groups map cleanly to Salesforce Queues for case ownership and routing, with no significant structural conversion required beyond recreating group membership. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Data Model Structural Conversion
SWSD's flat REST-accessible object model must be decomposed and rebuilt into Salesforce's deep relational object graph, requiring explicit parent-child relationship reconstruction via external ID matching across every migrated record.
Comment and Attachment Mapping
SWSD incident comments must be evaluated for length and formatting to determine whether to load as CaseComment (4,000-character plain-text limit) or EmailMessage (131,072-character HTML limit), as using CaseComment for all content risks silent data truncation.
Automation and SLA Rebuilding
SWSD automation rules and SLA policies cannot be migrated and must be manually reconstructed as Salesforce Flow logic, Assignment Rules, Entitlements, and Milestones in the target org.
User and Requester Deduplication
SWSD users who acted as both requesters and agents require deduplication logic, as they must be created as both a Salesforce Contact and a User record and linked via the Contact field on the User object to prevent data fragmentation.
CMDB and Configuration Item Conversion
SWSD CMDB configuration items with deep hierarchical relationships have no direct Salesforce equivalent and require custom object design before migration can proceed.
API Extraction Rate and Pagination Constraints
The Samanage REST API enforces page-based pagination with a maximum of 200 records per page, no cursor support, and undocumented rate limits requiring empirical throttling to 2–3 requests per second with exponential backoff to avoid extraction failures.
What breaks
Known failure modes. Have a recovery plan for each before you cut over.
Loading records out of dependency order
Creating Cases before Contacts exist breaks the ContactId lookup and generates INVALID_CROSS_REFERENCE_KEY errors. Salesforce either rejects the record or nulls the relationship depending on your allOrNone setting. Always load in the sequence defined above.
Ignoring the 4,000-character CaseComment limit
SWSD comments longer than 4,000 characters are silently truncated. Validate comment lengths during extraction and route long comments to EmailMessage instead.
Forgetting audit field permissions before the load
Every record gets the migration run date as CreatedDate. You only discover this post-load, and correcting it requires re-running the entire migration from scratch.
Underestimating attachment upload time
Binary uploads to ContentVersion are single-threaded via REST API and cannot use Bulk API. Underestimating this phase by 2–3x is the most common timeline failure.
Unmapped picklist values causing silent nulls
SWSD allows freeform text in some fields. Build a complete value mapping table and define all custom picklist values in Salesforce Setup before loading. Use the Bulk API results file to identify rows where the field was accepted but silently nulled.
Duplicate Contact records from user-requester overlap
SWSD users who are both ticket requesters and agents need deduplication logic at extraction time. If you create both a Contact and a User record for the same person without linking them, case history will be fragmented.
Row lock errors on parallel batch jobs
Multiple parallel batches writing Cases to the same parent Account trigger UNABLE_TO_LOCK_ROW errors. Sort CSV by AccountId external ID column before upload.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can you migrate SolarWinds Service Desk data directly to Salesforce Service Cloud?
There is no direct migration tool. You extract data via the Samanage REST API (incidents, problems, changes, users, assets, knowledge articles), transform it to match Salesforce's object model (Cases, Contacts, Accounts, EmailMessages, ContentVersion), and load using Bulk API 2.0 or Data Loader. The load must follow a specific dependency order — Accounts and Contacts before Cases, Cases before Comments and Attachments.
How long does a SolarWinds Service Desk to Salesforce migration take?
For incident-only migrations under 100,000 records, expect 2–3 weeks including testing. Full migrations that include CMDB, change management, knowledge base, and 250,000+ records take 4–8+ weeks. Attachment uploads are often the longest phase because binary files cannot use Salesforce Bulk API.
Should I use CaseComment or EmailMessage for migrated SolarWinds comments?
Use EmailMessage for public-facing correspondence. CaseComment is plain text with a 4,000-character limit — it will silently truncate long comments. EmailMessage supports HTML (up to 131,072 characters) and preserves formatting, but requires Email-to-Case to be enabled. Use CaseComment only for short internal notes.
What SolarWinds Service Desk data cannot be migrated to Salesforce?
Automation rules, SLA policies, approval workflows, service catalog configurations, dashboard layouts, saved reports, and email notification templates cannot be exported from SWSD. All of these must be manually rebuilt in Salesforce using Flows, Entitlements, Milestones, Approval Processes, and Email Templates.
Can I migrate SolarWinds Service Desk CMDB data into Salesforce?
Yes, but Salesforce does not have a native CMDB. You must map SWSD Configuration Items to the Salesforce Asset object with custom record types and fields, or create custom objects for complex CI hierarchies. If you have 10+ CI types with multi-level dependencies, consider keeping CMDB in a dedicated tool with an integration layer to Salesforce.