Skip to content
Get a quote

Migrate to Salesforce Service Cloud

Salesforce Service Cloud is the platform-as-helpdesk destination whose migration difficulty is driven by Case + EmailMessage threading, Knowledge versioned articles, Entitlement-driven SLA, and the Apex/Flow stack that fires on every imported row.

Short answer

FlitStack AI migrates tickets, threads, and customer histories into Salesforce Service Cloud from 250+ helpdesks, including Zendesk, Freshdesk. Every field is mapped to Salesforce Service Cloud's objects, history and associations come across, the Salesforce Service Cloud setup is configured alongside, and the whole migration stays reversible in one click.

By

From Any source
DestinationSalesforce Service Cloud
ZendeskFreshdesk
250+ sources mapped into Salesforce Service Cloud

Systems we move into Salesforce Service Cloud

The helpdesks teams most often move from. Each page shows what moves, the field mapping and what to watch for.

What Salesforce Service Cloud supports, and where its import tools stop

  • Deep Salesforce ecosystem integration with Sales Cloud, Marketing Cloud, and custom Apex apps creates a single pane of glass for enterprise customer data and cross-functional workflows.
  • Omnichannel case routing — email, chat, phone, social, and messaging — unified under one case object means agents do not lose context when customers switch channels mid-interaction.
  • AI for customer service (Einstein AI / Agentforce) offers automated case classification, suggested replies, and chatbot routing that reduces Tier-1 ticket volume without manual rule authoring.
  • Entitlement and milestone tracking enforces SLA compliance natively, automatically calculating breach windows and surfacing violations to supervisors in dashboards.
Bulk APIOAuth 2.0, Connected App, or API key via Salesforce REST/SOAP endpoints
Rate limits100,000 API requests/day on Enterprise (rolling 24-hour window); lower limits on Professional and Starter editions. Concurrent API limits cap simultaneous long-running requests separately.
ObjectSupportNote
CasesfullCases are the primary ticket object in Service Cloud, supporting multiple Record Types and custom fields. We map the full case lifecycle including Origin, Status, Priority, and Record Type. Standard fields transfer cleanly; custom Case fields require explicit value-mapping between source and destination schemas.
ContactsfullContacts are standard CRM objects with a rich relationship to Accounts and Cases. We preserve the Contact-to-Account relationship and any custom contact properties. Multi-address records require field-level normalization.
AccountsfullAccounts represent organizations and support hierarchical structures (parent Account). We map Account hierarchy and standard fields. Custom Account fields require value-mapping. Industry and Type picklist dependencies are handled explicitly.
Case CommentsmappedCase Comments are child records of Cases, supporting both public and private comments. We migrate comments as a related list, preserving the IsPublished flag. Rich-text formatting may require sanitization depending on destination.
Case HistorymappedCase History tracks field-level changes (audit trail). We migrate history as a snapshot linked to the parent Case. Not all destination CRMs have an equivalent audit trail object, so we offer selective migration of status and owner-change events.
Case Team MembersmappedCase Team Members assign roles to Users on individual Cases. We map team roles and member assignments. If the destination does not have a case team concept, we convert assignments to a custom Case field or linked User record.
Case MilestonesmappedCase Milestones track SLA entitlement time Remaining and Completion dates. Milestone objects are tied to Entitlement and Milestone Type. We preserve milestone timestamps and remaining time, flagging any breached milestones for customer review.
EntitlementsmappedEntitlements define SLA terms (response time, resolution time) and are linked to Contacts and Accounts. We migrate entitlement records and their association to Cases. Entitlement process and milestone type mapping requires configuration-level review.
Knowledge ArticlesmappedKnowledge Articles store structured self-service content linked to Cases via Case Article. We migrate article versions, categories, and URL names. Article publishing states (Draft, Published, Archived) are preserved as a custom field in the destination.
Email MessagesmappedEmail Messages are threaded under Cases via the parent Case ID. We map message body, subject, from/to addresses, and HTML body. Attachments are extracted separately and linked via foreign key. Plain-text normalization may be needed for destination rendering.
SolutionsmappedSolutions are reusable knowledge articles attached to Cases. We migrate Solution titles, body content, and attachment links. If the destination has a different KB model, Solutions may be merged into Knowledge Article equivalents.
AssetsmappedAssets represent products purchased by an Account, often linked to Cases. We map Asset name, status, install date, and product relationship. Asset-to-Case linkage is preserved via custom mapping if the destination lacks a native Asset object.
ProductsmappedProducts define the product catalog and are linked to Assets and Cases. We migrate product names, codes, families, and descriptions. Pricebook entries require explicit mapping to destination pricebook structure.
UsersmappedUsers represent agents and admins in Service Cloud. We map user profiles, roles, and active status. In migrations, agent Users are typically mapped to new user IDs in the destination system via an explicit owner-redirect table.
TagsnoneTag definitions (Salesforce Topics for Cases) are lightweight taxonomy objects with no standard export path and limited migration value. We skip Tags and recommend rebuilding taxonomy in the destination using the Case subject and custom fields.

The Salesforce Service Cloud migration guide

Why teams migrate to Salesforce Service Cloud

The four shapes a Service Cloud migration takes, and what makes the platform harder — or easier — than the category average.

Salesforce, Inc. was founded by former Oracle executive Marc Benioff in March 1999 and is headquartered in San Francisco, California1. For fiscal year 2026 the company reported $41.5 billion in annual revenue, and Service Cloud sits inside a broader stack that includes Sales Cloud, Marketing Cloud, Revenue Cloud, Tableau, Slack and the Agentforce AI layer1.

The typical Service Cloud customer is a mid-market or enterprise support organisation — 50 to 10,000+ agents — that needs case management, Knowledge, Entitlements + Milestones for SLA, Omni-Channel routing and an extensibility model through Apex, Flow and Validation Rules. Compared with Zendesk or Freshdesk, Service Cloud positions on configurability, the Sales Cloud + Service Cloud single record, and a deeper automation surface; compared with HubSpot Service Hub, it positions on Knowledge versioning, multi-channel routing maturity and the AppExchange.

The shapes of migration that actually land on Service Cloud fall into four patterns. First, competitor exits from Zendesk, Freshdesk, Help Scout, Intercom or Kayako when teams outgrow the source platform or need the single Account view shared with Sales Cloud. Second, legacy consolidation from Desk.com, Parature, on-prem ticketing systems or shared inboxes where the source schema is loose and the project is really a re-architecture.

Third, multi-org consolidation, where two or more Salesforce orgs from past M&A activity are merged into one — typically the hardest shape because both sides carry incompatible Record Types, Sharing Rules and Apex Triggers on the Case object. Fourth, Sales+Service unification, where a company already on Sales Cloud bolts Service Cloud onto the same org and migrates an external helpdesk in.

What makes migrating to Service Cloud harder than the category average is the automation that runs on insert. Validation Rules, Apex Triggers, Workflow Rules, Process Builder and Flow all evaluate every imported Case, CaseComment and EmailMessage, and a Trigger that auto-assigns owner blows the SOQL governor limit on the 51st row of a 200-row batch22. Most migration teams disable automation during the load and re-enable it post-cutover with a regression test plan.

The second difficulty is Lightning Knowledge, which uses a versioned article model with its own publish workflow — articles are inserted as draft Knowledge__kav rows, published, then re-versioned. Standard bulk import patterns that work for Cases do not translate to Knowledge.

What makes it easier than the average is the External ID field type — a first-class upsert mechanism on every object, capped at 25 external IDs per object, that lets you match Cases, Contacts and Accounts by a value from the source system rather than by Salesforce's 18-character Record ID3. Combined with the platform's job-based async loader, the platform rewards teams who plan their External IDs and load order before writing a single row.

Apex Triggers, Flows, Macros, Quick Actions, Entitlement Processes and Reports do not import — they are rebuilt from documentation. Teams that scope for that work up front finish on time; teams that assume parity do not.

The destination's automation layer fires on every imported Case, CaseComment and EmailMessage unless you actively quiet it — and re-enabling without regression is how teams break support on day five.

The Salesforce Service Cloud data model you need to map into

Case, CaseComment, EmailMessage, Knowledge__kav, Entitlement, Record Types, and the External ID upsert mechanism — the destination schema decoded.

Service Cloud's data model is built on the same Salesforce platform as Sales Cloud — Standard Objects plus Custom Objects plus a relationship model of Lookups, Master-Detail and Junction Objects. The objects that distinguish Service Cloud are Case at the centre, CaseComment for ticket notes, EmailMessage for inbound and outbound email threading, Knowledge__kav for Lightning Knowledge articles, Entitlement and ServiceContract for SLA, and the routing objects PendingServiceRouting and AgentWork that power Omni-Channel.

Before you can map a field, you need to know which Standard Object the row belongs on, which Record Type applies inside that object, which required fields the Page Layout enforces, and which field you will use as the External ID for upsert. The table below summarises the objects you will touch in a Service Cloud migration.

ObjectWhat it storesRequiredTier
AccountCompanies that submit cases (or households on Person Accounts)Name (or Last Name on Person Accounts)All editions
ContactIndividual requesters tied to an AccountLast Name, Account ID (unless Individual model)All editions
CaseSupport tickets — the central objectStatus, Origin; Subject and ContactId on most layoutsAll editions
CaseCommentInternal notes and public replies on a CaseParentId (Case); IsPublished flag for public visibilityAll editions
EmailMessageInbound and outbound email threads attached to a CaseParentId (Case); FromAddress, ToAddress, Status, MessageDateAll editions
Knowledge__kav (Article Version)Lightning Knowledge versioned articlesTitle, UrlName; PublishStatus + Language drive lifecycleService Cloud editions with Knowledge enabled
Entitlement + ServiceContractSLA contracts that drive Milestone timers on CasesName, AccountId, Type, StartDate, EndDate, BusinessHoursEnterprise+ (Service Cloud)
Macro / QuickTextAgent productivity templates and canned responsesName, Instructions (Macro) / Message (QuickText)All Service Cloud editions
LiveChatTranscript / MessagingSessionChat / Messaging for In-App and Web session recordsStatus, StartTime; Contact/Case associationsService Cloud Digital Engagement add-on
Custom ObjectsCustomer-defined record types (e.g. Asset extensions)Defined per object; deployed schema before loadEnterprise+ for unlimited; lower editions capped

Salesforce assigns an 18-character Record ID to every record on insert — you cannot set Record IDs on import. The migration pattern is to use External ID fields: up to 25 custom fields per object (auto-number, email, number or text) flagged as External ID and used as the upsert match key3. Mark them Unique and case-sensitive on Case, Contact, Account, EmailMessage and Knowledge__kav to prevent silent duplicate merges.

Relationships come in three shapes. Lookup is a loose one-to-many — deleting the parent does not cascade. Master-Detail is tightly coupled, where the child inherits ownership and sharing from the master and is deleted with it. CaseComment, EmailMessage and CaseFeed all sit in Master-Detail-like behaviour under Case. Junction Object is a custom object with two Master-Detail relationships used to model many-to-many.

Field typeLimitNotes
Text / Text AreaText 255 chars; Long Text Area 131,072 chars; Rich Text 131,072CaseComment.CommentBody capped at 4,000 chars21
Number / Currency / Percent18 digits total; up to 18 decimal placesCurrency respects multi-currency org settings
Date / Date-TimeDate-Time stored in UTC; ISO-8601 in loaderWrong format silently imports null on Data Import Wizard
Picklist (single / multi-select)1,000 active values; 2,000 inactive on single-selectRestrict picklist enforces strict ENUM — typo = rejection
Formula / Roll-Up SummaryFormula 3,900 char compiled; Roll-Up needs Master-DetailDoes not import — recomputed by platform after load
Lookup / Master-Detail40 lookups per object; 2 Master-Detail max per objectMaster-Detail cascades delete; Lookup does not
External ID fieldsUp to 25 per objectPrimary upsert mechanism via loader and Data Import Wizard3
Custom fields per object500 on Enterprise; 800 on UnlimitedHard cap; External Objects for overflow

Record Types add a second axis on Case: one Case object can have multiple Record Types — for example Tier 1 Support, Tier 2 Support, Field Service, Billing — each with its own Page Layout, picklist value subset, support process, and required-fields list. A Case inserted with the wrong Record Type displays the wrong fields to the agent on day one, and the value RecordTypeId on every imported Case row decides which one it lands on.

Note that Field Service (formerly Field Service Lightning) is a separate Salesforce product layered on top of Service Cloud — it adds WorkOrder, ServiceAppointment and ResourceAbsence objects for dispatch and mobile work. If your source is a field-service platform, plan for Field Service licensing separately from Service Cloud. Big Objects (the platform's archive tier) default to 1 million records and are not used for active migration loads11.

Pre-migration prep — the work before you touch Service Cloud

What must be true on the source, the destination, and across the team before the first Case row is loaded.

The single best predictor of a clean Service Cloud migration is how much work you do on the source side before the first load job is submitted. Practitioners consistently report that field-mismatch breakage is not really about the fields — it is about the Validation Rules, Apex Triggers and Flows that fire on every imported Case and reject anything legacy data does not perfectly match22.

Disable Validation Rules and Triggers during the load, then re-enable and run regression tests against a sample of migrated Cases — most teams skip the regression step and pay for it on day five.

Treat the source export as raw material shaped to Service Cloud's expected formats — email validated, phone normalised to international format, ticket status values converted to the destination's exact case-sensitive picklist values, dates rewritten to ISO-8601, agent emails resolved to Salesforce User IDs, ticket priority and channel re-mapped to Case.Priority and Case.Origin.

Source-side prep

  • Audit and dedup the source helpdesk before export — Cloudingo, DemandTools and Plauti Duplicate Check catch fuzzy-match duplicates that Salesforce's built-in Matching Rule and Duplicate Rule would silently merge during Account or Contact insert25.
  • Stamp a stable External ID on every Case, Contact, Account, KB article and EmailMessage in the source export — the legacy primary key, a UUID or composite key — and create custom External ID + Unique + case-sensitive fields on each destination object to land them3.
  • Convert ticket status, priority and channel values to the exact destination picklist case — restricted picklists reject any typo, casing difference or trailing space with bad value for restricted picklist field. Build a transform table per picklist per Record Type.
  • Resolve agents by exporting your destination User list (User.Id, Username, FederationIdentifier) and joining to the source agent column. Rows whose OwnerId cannot be resolved fall to the integration user, silently breaking owner-based assignment and Omni-Channel routing.
  • Decide what is in scope for historical email threads and attachments. EmailMessage rows can be inserted with backdated MessageDate, but each Case with 50 message threads is a 50× multiplier on storage and daily load allocation.

Destination-side prep

  • Create a Full Sandbox (or Partial Copy on lower editions) from Setup → Sandboxes — a Full Sandbox copies production data and metadata for end-to-end dry-runs and the refresh interval is 29 days17.
  • Provision agents and supervisors first through your identity provider (Okta or Microsoft Entra ID), assign Permission Sets and Profiles, and confirm the Service Cloud User permission is checked — Omni-Channel and Macros require it.
  • Deploy every Case Record Type, Page Layout, Support Process, custom field and picklist value via a deployment tool before importing. Cases targeting a Record Type or Status value that does not yet exist on the destination are rejected.
  • Disable Validation Rules, Workflow Rules, Process Builder Flows and Apex Triggers on Case, CaseComment, EmailMessage and Account during the load (or wrap them in a Bypass__c Custom Setting skip flag). Re-enable post-cutover with a regression test plan22.
  • Pre-build Entitlement Processes, Milestones, Service Contracts and Business Hours before importing Cases — a Case linked to a missing EntitlementId silently runs no SLA timer, breaking your downstream SLA dashboards.

People prep

Cutover works only when humans cooperate. Lock down a source-helpdesk freeze window — typically 24 to 72 hours — and communicate it to every channel that touches support. Train agents on Service Console daily workflows, Case management, Macros and Omni-Channel before go-live, not after. A clean Zendesk-to-Service-Cloud migration under 25,000 Cases often lands in six weeks; a multi-org consolidation runs eight to sixteen weeks27.

Import mechanisms: Data Import Wizard and Data Loader

Multiple mechanisms in, each with different limits, object support, and async behaviour. Picking the wrong one stalls mid-migration at scale.

Service Cloud exposes the same load paths as the rest of the Salesforce platform, and the right one depends on dataset size and object mix. Data Import Wizard covers small loads on a handful of objects but does not support Case, CaseComment or EmailMessage. Data Loader and Workbench cover the medium tier. Helpdesk-specific migration tools sit on top of all of them.

Data Import Wizard

The native UI tool lives at Setup → Data Import Wizard and supports a limited set of objects: Leads, Accounts, Contacts, Campaign Members, Solutions, Person Accounts and Custom Objects. The record limit is 50,000 per import, files must be CSV with UTF-8 encoding, and dates must use the org's locale format. For Service Cloud the Wizard is useful for prerequisite Account and Contact loads — Case is unsupported.

Data Loader and Workbench

Data Loader is the desktop app (Windows/macOS) that ships from Salesforce. It supports every Standard and Custom Object including Case, CaseComment and EmailMessage, runs Insert / Update / Upsert / Delete / Hard Delete / Export, and supports both interactive and CLI modes with scheduled jobs. Workbench is the browser equivalent — useful for one-off jobs without local install.

Large-volume async loading

For large-volume work, Data Loader can be configured to use the platform's async load mode, where Salesforce auto-chunks server-side — you do not size batches yourself. The same async path is what helpdesk-specific migration tools use under the hood for very large ticket loads.

Per-call limits compound on top: Apex Triggers firing on imported Cases consume governor limits — 100 SOQL queries and 150 DML statements per transaction — which is why bypassing Triggers during the load matters27. The Salesforce Knowledge import path is separate: articles are inserted as draft Knowledge__kav rows, published via KbManagement.PublishingService.publishArticle, then re-versioned, and tools that work cleanly for Cases do not translate to Knowledge.

Third-party staging and helpdesk-specific tools

Dataloader.io (web Data Loader from MuleSoft), Skyvia, Talend, Informatica Cloud, Jitterbit and MuleSoft Anypoint all handle general Salesforce object loads. For Service Cloud specifically, helpdesk migration vendors like Help Desk Migration / Relokia and Import2 ship pre-built source connectors for Zendesk, Freshdesk, Help Scout, Intercom and Kayako that handle ticket → Case + thread → EmailMessage decomposition out of the box. Most enterprise migrations end up on MuleSoft or Informatica when source data is on-prem.

Mapping your data into Salesforce Service Cloud

The longest section — because Case threading, Knowledge versioning, Macros rebuild and Entitlement-driven SLA is where every Service Cloud migration that fails actually breaks.

Mapping is where every Service Cloud migration earns its scars. The schema decisions you make in your mapping spreadsheet determine whether Case dashboards work on day two, whether Entitlement-driven SLA timers fire correctly on day five, and whether your agents trust the data on day thirty.

Work object by object, top to bottom of the load order: Users first (done in prep), then Accounts, then Contacts, then Cases, then CaseComments and EmailMessages against their parent Case External ID, then Knowledge articles via the publish workflow, then Macros and QuickText rebuilt from documentation. Load order matters because every child row needs a parent External ID that already exists.

Account and Contact

Common source → Service Cloud Account / Contact mapping
SourceDestinationNote
organisation / companyAccount.Name + Legacy_Account_ID__c (External ID)Required; map by domain on dedup25
requester first/last nameContact.FirstName / LastNameLastName required; resolve to existing Contact via Email match
requester emailContact.Email + Legacy_Contact_ID__c (External ID)Drives Email-to-Case auto-match and Standard Contact Matching Rule25
organisation domainAccount.Website + custom Domain__cUsed by Email-to-Case lookup to auto-link new emails to Account
user role (admin/end-user)Profile or Permission Set on UserEnd-users on source map to Contacts; only agents become Users

Case — the ticket itself

Recreate every Case Support Process, Status value, Priority and Origin in Service Cloud before importing Cases. Each Status has a IsClosed Boolean that drives reporting and Entitlement Milestone completion. Cases that target a Status not present in the assigned Record Type's Support Process are rejected with bad value for restricted picklist field. Map source ticket statuses to destination Status values explicitly per Record Type.

Common source → Service Cloud Case mapping
SourceDestinationNote
ticket_idLegacy_Case_ID__c (External ID, Unique)Primary upsert key — required for CaseComment / EmailMessage parent lookup
subject / titleSubjectRequired on most Page Layouts
description / first message bodyDescriptionLong Text Area; preserve plain-text fallback for HTML bodies
statusStatusRestricted picklist per Support Process per Record Type
priorityPriorityRestricted picklist; map source values to Low/Medium/High/Critical
channel (email/chat/web/phone)OriginRestricted picklist; aligns with Email-to-Case and Web-to-Case generated values
ticket type / record typeRecordTypeIdDrives Page Layout + Support Process — set explicitly
assigneeOwnerIdDrives Omni-Channel routing + Role Hierarchy sharing
requesterContactId + AccountIdResolve via Contact External ID lookup; AccountId derives from Contact
created_at / updated_atCreatedDate / LastModifiedDate (requires Create Audit Fields)Otherwise stamped to load day — preserve in Legacy_Created_Date__c

Case history — CaseComment + EmailMessage threads

Service Cloud splits ticket conversation across two objects. CaseComment holds internal notes and short public replies — CommentBody is capped at 4,000 characters, IsPublished controls whether the customer sees the comment in the portal21. EmailMessage holds full inbound and outbound email threads attached to a Case via ParentId, with Incoming Boolean, FromAddress, ToAddress, Subject, TextBody, HtmlBody, MessageDate and Status (Sent/Received/Draft).

The migration pattern for source threads is: classify each thread entry as either CaseComment (short internal note, agent annotation) or EmailMessage (actual email exchange), load them with ParentId referencing the Case External ID and MessageDate backdated, then attach files via the ContentVersion + ContentDocumentLink pattern below. EmailMessage thread ordering inside the Case Feed is driven by MessageDate — get it wrong and the customer-visible thread reads out of order.

Lightning Knowledge — versioned articles

Lightning Knowledge uses a versioned model: each article is a KnowledgeArticleVersion (Knowledge__kav) row with many versions in Draft, Online or Archived states. Only one Draft and one Online version can exist per article at a time, and parallel inserts are not allowed. The pattern is: insert version one as Draft, publish via KbManagement.PublishingService.publishArticle, then re-insert subsequent versions sequentially.

Map source KB title → Title, slug → UrlName, body → a Rich Text custom field, categories → Data Categories, and tags → keyword fields. Standard CSV import via Data Loader does not work for Knowledge — use the dedicated Knowledge publish workflow or a migration tool that wraps it. Multilingual KB articles add another axis: each Language is a separate Knowledge__kav chain with its own version history.

Macros, Quick Actions and Email Templates

Source canned responses, automation rules and email templates do not import — they are rebuilt. Service Cloud Macros run a sequence of Quick Actions on a Case and live in Macro + MacroInstruction records; Email Templates live in EmailTemplate. Source rules from Zendesk Triggers, Freshdesk Automations or Help Scout Workflows are rebuilt as Flows, Case Assignment Rules or Apex Triggers — the Freshdesk practitioner thread captures a 240-rule rebuild collapsed cleanly via Custom Metadata Types39.

Entitlements, Milestones and SLA history

SLA in Service Cloud runs through Entitlement Management. The chain is: ServiceContract (customer agreement) → Entitlement (specific support coverage on an Account or Asset) → Entitlement Process (with one or more MilestoneType definitions for response time, escalation, resolution) → BusinessHours (working calendar). A Case links to an Entitlement via EntitlementId, and the Entitlement Process clocks Milestones automatically.

Source SLA definitions (Zendesk SLA policies, Freshdesk SLAs) are rebuilt as Entitlement Processes — they do not import. Historical SLA breach data is captured by populating custom datetime fields like Legacy_First_Response_At__c and Legacy_SLA_Breached__c from the source export so that historical SLA reports continue to work.

CSAT history

Salesforce delivers CSAT via Salesforce Feedback Management or via the Survey object, which stores Question + Response rows linked to a Case. Source CSAT scores (Zendesk Satisfaction, Freshdesk CSAT, Intercom Conversation Rating) do not import into the Survey object cleanly — the practical pattern is to land them in a Legacy_CSAT_Score__c numeric custom field plus a Legacy_CSAT_Comment__c text field on the Case, then build a new Survey for go-forward measurement.

Multi-channel — Email-to-Case, Voice, Chat, Messaging

Service Cloud's multi-channel surface is configured after the data load, but routing and threading rules need design during mapping. Email-to-Case creates Cases from inbound email and threads replies via a thread identifier in the subject or References header. Service Cloud Voice (with Amazon Connect or partner telephony) creates VoiceCall records routed through Omni-Channel. Chat uses LiveChatTranscript; Messaging for In-App and Web uses MessagingSession.

For migrated tickets that started on chat or social, the cleanest pattern is to land the transcript on the Case as a single CaseComment or EmailMessage row with Origin = Chat (or Social) — full LiveChatTranscript record reconstruction is rarely worth the effort. Omni-Channel routing configuration (queues, skills, presence statuses) is rebuilt against the migrated Case Record Types post-load.

Files and attachments

Service Cloud has two file frameworks: the legacy Attachment object (25 MB cap per file, no metadata customisation) and the modern Files framework built on ContentVersion + ContentDocument + ContentDocumentLink (10 GB cap per file in Lightning Experience, full metadata support). New migrations should land on Files. The migration pattern: insert a ContentVersion with the binary as VersionData (base64) and Title, capture the returned ContentDocumentId, then link to the parent Case via a ContentDocumentLink row.

For large attachment estates (TBs of ticket attachments), most teams keep originals in S3 or Azure Blob and store a deep link in a custom URL field on the Case — only the most-recent or most-referenced subset inlines. Inline image references inside EmailMessage HTML bodies need to be rewritten to point at the new ContentDocumentLink URLs or they break the rendered email view.

Audit trail, ownership and original timestamps

By default Salesforce stamps CreatedDate, CreatedById, LastModifiedDate and LastModifiedById on insert and they are read-only. To preserve original audit trail on Case, CaseComment and EmailMessage, file a support case requesting Create Audit Fields permission so those four fields can be set during insert. Toggle the permission off after cutover. Field History Tracking captures 20 fields per object by default; Field Audit Trail extends to 60 fields with 10-year retention.

The pitfalls that derail Service Cloud migrations

Specific failure modes — ranked by impact, each tied to the exact Service Cloud mechanism that breaks.

Validation and cutover

What to verify after the loader finishes Cases, in what order — and how to fail safely when Triggers ate a chunk.

Validation is the bridge between the loader returning success and agents being allowed in. Service Cloud data-migration practitioners recommend a three-stage validation: a test load of 10 percent of Cases in a Full Sandbox with department-rep spot-checks, the full production load with real-time monitoring of partial-success counts, and a 30-day post-migration data-quality audit using DemandTools or Cloudingo to surface the merges that Matching Rules did silently34.

Build a reconciliation queries spreadsheet that compares source and Service Cloud on each of the counts below. Anything outside a 0.5 percent variance gets investigated before agent login access opens.

  • Total Cases inserted vs source helpdesk — SELECT COUNT() FROM Case WHERE Legacy_Case_ID__c != null ensures you only count migrated rows.
  • Total Cases per Status per Record Type plus Cases per Priority and per Origin — a non-trivial variance signals a picklist-mapping error or a Trigger that re-stamped Status on insert.
  • Total CaseComments per Case spot-check — pick 30 high-volume Cases and verify the public-vs-internal mix matches source, catching CaseComment.IsPublished mis-flagging.
  • Total EmailMessages per Case + MessageDate ordering — confirm thread order reads correctly in the Case Feed on a sample of 20 long-thread Cases.
  • Knowledge articles per Data Category + PublishStatus vs source KB — confirm version history depth and Published state matches.
  • OwnerId distribution — SELECT OwnerId, COUNT(Id) FROM Case GROUP BY OwnerId and confirm no Case landed on the integration user that should not have.
  • Entitlement linkage — SELECT COUNT() FROM Case WHERE EntitlementId = null AND AccountId IN (SELECT AccountId FROM Entitlement) should be near zero on Cases that should have SLA coverage.
  • External ID uniqueness — SELECT Legacy_Case_ID__c, COUNT(Id) FROM Case GROUP BY Legacy_Case_ID__c HAVING COUNT(Id) > 1 should return zero rows.

On top of reconciliation, run a manual spot-check: pick 30 random Cases across Record Types and verify each field against the source UI. Pick five high-value Cases and trace the full graph — Account, Contact, CaseComments, EmailMessages, attachments, Entitlement. If three or more of the 30 show non-trivial discrepancy, halt the load, fix the root cause (almost always a Trigger or Validation Rule), and re-import affected rows by Legacy_Case_ID__c via Data Loader upsert.

Service Cloud's native Recycle Bin holds deleted records for 15 days and can be used for small-scale undo from the UI34. Undoing an Import under Setup is available only for Data Import Wizard imports launched within the last 24 hours and only deletes records the import created34. For Data Loader there is no built-in undo — you delete by Legacy_Import_Batch_ID__c custom field and re-import from the cleaned source.

The rollback strategy practitioners actually use: full org backup via Salesforce Data Export (Setup → Data Export) or a third-party backup tool like Odaseva or OwnBackup before the migration starts, plus stamping every imported row with an Import_Batch_ID__c custom text field, so catastrophe means a SOQL delete by batch ID followed by re-import from clean source34.

Cutover sequencing: (1) source helpdesk goes read-only; (2) final delta export captures every Case, CaseComment, EmailMessage and KB version changed during sandbox-test; (3) delta upsert via Data Loader using Legacy_ID External IDs; (4) reconciliation queries run; (5) Email-to-Case routing, Omni-Channel queues, Entitlements and Validation Rules re-enabled with regression pass; (6) agents get login and a 48-hour hyper-care window; (7) source decommission 30 to 90 days out, never same day.

Migration partners and tools

Summit and Crest Salesforce Partners, ETL vendors, helpdesk migration specialists — what each is good for and how to choose.

The Salesforce Partner Program tiers consulting firms by Navigator certifications, Customer Satisfaction (CSAT) scores and Salesforce-credentialed engineer count. The named tiers were historically Global Strategic, Summit, Crest and Ridge; Salesforce announced a 2026 consolidation to two tiers (Select and Summit) rolling out through FY27. 70 percent of Salesforce implementations are delivered through Partners rather than direct, and most non-trivial Service Cloud migrations end up with one.

Deloitte Digital, Accenture, Capgemini, IBM and Slalom dominate the global Strategic tier for enterprise multi-cloud rollouts. For mid-market Service Cloud migration projects specifically, Summit-tier partners with explicit helpdesk-exit practices (Service Cloud from Zendesk, from Freshdesk, from Help Scout, from Intercom) tend to ship cleaner than generalist implementation shops. Salesforce also runs Professional Services in-house — typically the most expensive option but the one with deepest product-team access.

On the helpdesk-migration tooling side, Help Desk Migration / Relokia and Import2 are the two most-named specialist vendors, both shipping pre-built connectors for Zendesk, Freshdesk, Help Scout, Intercom, Kayako and Kustomer that handle ticket-to-Case + thread-to-EmailMessage decomposition. For general ETL, MuleSoft is the Salesforce-owned default for on-prem integration, Informatica Cloud is common in regulated industries, and Fivetran, Airbyte, Stitch and Workato cover the warehouse-first stack. Cloudingo and DemandTools handle Account + Contact dedup.

Managed-migration cost ranges vary widely. A clean Zendesk- or Freshdesk-to-Service-Cloud move under 25,000 Cases, standard Email-to-Case and one Record Type, typically lands in the $20,000–$60,000 range. A multi-org consolidation with Case history, Knowledge re-versioning, Macro and Entitlement rebuild, Omni-Channel skill design and Apex/Flow rebuild runs $60,000–$500,000+, driven by Case count, channel count and integration scope.

For teams that want to outsource the migration end-to-end, FlitStack specialises in Salesforce Service Cloud migrations and handles External ID schema design, Case + CaseComment + EmailMessage thread decomposition, Lightning Knowledge versioned-article load, Macro and Entitlement rebuild scoping, Trigger bypass setup, and the reconciliation work in Sections 5 and 7. Pricing is fixed-fee, based on Case count and source platform, with separate line items for Knowledge depth, Apex/Flow rebuild and historical SLA scope.

This is one of several legitimate paths — the right choice for any given team depends on whether they want a Summit Partner with a wider services footprint, Salesforce Professional Services with deepest product-team access, a helpdesk-migration specialist focused on the load itself, or an ETL-first approach via MuleSoft. [Explore FlitStack →](/contact)

Salesforce Service Cloud migration checklist

An eight-phase, task-by-task punch list for moving Cases, CaseComments, EmailMessages, Knowledge articles, and multi-channel history into Salesforce Service Cloud. Typical timeline: 6–16 weeks.

0. Decide & Plan10 tasks
  • Define migration scope by Service Cloud object. Document explicitly which standard objects are in scope (Account, Contact, Case, CaseComment, EmailMessage, ContentVersion, Knowledge__kav, Entitlement, ServiceContract, LiveChatTranscript, MessagingSession, OmniChannel routing config) and which custom objects from the source map to which destination object.If skipped: Scope ambiguity surfaces mid-cutover as missing channels or article history, forcing emergency re-imports against governor limits.
  • Define ticket-history scope and cut-off date. Decide how many years of closed Cases and their CaseComment / EmailMessage threads move over. Decide whether chat transcripts, voice call logs, and in-app messaging sessions are in or out. Decide whether attachments are in or out.If skipped: An unbounded historical scope inflates File Storage, breaks the cutover window, and forces a paid storage add-on at short notice.
  • Identify the Salesforce edition and storage profile. Confirm Enterprise vs. Unlimited Service Cloud licensing, check current Data Storage and File Storage allocations against projected post-migration usage, and confirm Knowledge license counts for read and author seats.If skipped: Hitting storage caps mid-load aborts bulk load jobs and stalls Knowledge article publication.
  • Decide channel scope in writing. List which channels the destination will accept on day one: Email-to-Case, Web-to-Case, Service Cloud Voice on Amazon Connect or a partner telephony adapter, Chat via LiveChatTranscript, Messaging for In-App and Web via MessagingSession, Social Customer Service. Out-of-scope channels do not migrate transcripts.If skipped: Quietly migrating a channel whose runtime is not configured leaves transcripts orphaned in the destination.
  • Document legal and residency constraints. Confirm whether the org must run on Hyperforce in an EU region for GDPR, capture SOC2/HIPAA evidence requirements, and document any data-retention policies that change at cutover.If skipped: Residency violations discovered after go-live require a Hyperforce region migration and DPA renegotiation.
  • Assign a single accountable DRI and a stakeholder map. Name one decision-maker for scope changes, plus a RACI covering Support Operations, Support Leadership, IT, Telephony, Security, and Legal.
  • Define written success criteria. Specify the exact conditions that must hold before sign-off: per-object record-count parity, aggregate open-case count match, sample-record field-by-field accuracy at Y%, Knowledge article publication counts, and zero open critical UAT defects.If skipped: Without falsifiable criteria, the sponsor declares the project done while critical history gaps persist.
  • Set the cutover window and source-system freeze date. Pick a specific date and time, the freeze hour for source-system writes, and the planned read-only date for the legacy system.
  • Document out-of-scope items explicitly. List the data, automations, integrations, and channels that will not move, so they are not raised as defects later.
  • Estimate load throughput and storage consumption against the cutover window. Project record volume by object, factor in test runs and re-loads, and confirm the org fits within available storage and load throughput budgets. Knowledge article load is sequential because every version must be published in order.If skipped: Cumulative consumption from sandbox tests, Knowledge re-versioning, and reloads can exhaust the budget hours before cutover finishes.
1. Pre-Migration Prep30 tasks
  • Export baseline record counts per source object. Capture counts for every object in scope (Tickets/Cases, public comments, internal notes, emails, KB articles, attachments, chat transcripts, voice call logs). This becomes the reconciliation reference for Phase 6.If skipped: Without a baseline, you cannot prove anything was lost.
  • Run dedup on source Contacts using email as the match key. Resolve all duplicate Contacts before export. Document which surviving record wins on conflict.If skipped: Duplicate Contacts split case history across multiple records and break email-to-case matching post-cutover.
  • Run dedup on source companies using normalized name + domain. Resolve company-level duplicates and reparent child Contacts and Cases to the surviving Account.If skipped: Duplicate parent Accounts split SLA reporting and break support-team rollups after cutover.
  • Standardize email casing, phone formats, and ISO country codes. Lowercase emails, convert phone numbers to E.164, map country names to ISO-3166-1 alpha-2.If skipped: Validation Rules on Country reject non-ISO values, blocking row-level Case and Contact inserts.
  • Resolve source records missing fields required on the Salesforce side. Account.Name, Contact.LastName, Case.Subject, Case.Status, Case.Origin are required on insert. Knowledge__kav requires Title and UrlName.If skipped: Missing required fields fail per row and pollute error logs with thousands of rejections.
  • Identify orphaned cases, comments, and attachments in the source. Flag records whose parent Contact, Account, or Case will not be migrated so they are dropped or re-parented before export.
  • Audit source automation: macros, triggers, automation rules, SLA policies. Inventory every automation rule, macro, canned response, and SLA policy in the source. These do not transfer and must be rebuilt as Macros, Quick Actions, Email Templates, and Entitlement Processes in the destination.If skipped: Skipping the inventory leaves agents without the daily workflow they depended on in the source.
  • Capture source Knowledge article inventory with version history. Pull every published article plus its full version history. Lightning Knowledge requires sequential version replay; you cannot insert v1, v2, v3 in parallel.If skipped: Losing version lineage means the published article history disappears and any rollback path is gone.
  • Provision the production Salesforce org and at least one Full or Partial Copy Sandbox. A Full Sandbox refreshes from production data; a Partial Copy includes a sampled subset. Developer sandboxes hold metadata only and are insufficient for volume testing of Case and Knowledge data.If skipped: Testing volume in a Developer sandbox understates throughput and lets governor-limit and storage issues surface in production.
  • Configure org-level settings: currency, fiscal year, locale, timezone, business hours. Business Hours drive Milestone clocks on Entitlements; getting them wrong shifts SLA timing across every migrated case. Set Business Hours per support region before any Entitlement is created.If skipped: Wrong Business Hours assign every milestone to the default 24/7 calendar and misreport SLA attainment.
  • Enable Lightning Knowledge in Setup. Lightning Knowledge replaces Classic Knowledge and uses the Knowledge__kav versioned model. Enabling is one-way; confirm it matches the destination Knowledge strategy before flipping the switch.If skipped: Loading articles before Lightning Knowledge is enabled creates Classic Knowledge records that cannot be converted without rework.
  • Create users in advance with Service Cloud Profiles, Roles, and Permission Sets. Owner IDs on imported Cases must already exist. Use Permission Sets for Knowledge author, Service Cloud agent, and Omni-Channel routing rather than cloning Profiles per user.If skipped: Loads fail at row level when OwnerId references a user that was not created or is deactivated.
  • Grant the migration user the 'Set Audit Fields upon Record Creation' permission. Without this permission, the platform overwrites Case.CreatedDate, CaseComment.CreatedDate, and EmailMessage.MessageDate with the load timestamp.If skipped: Historical case timestamps are silently replaced and cannot be re-applied after the fact.
  • Create all custom fields, including a Legacy_Case_Id__c External ID on Case. Mark one custom field as External ID and Unique on Case, Contact, Account, Knowledge__kav, EmailMessage, and CaseComment so bulk upserts can match by source primary key. Up to 25 External ID fields are allowed per object.If skipped: Without an External ID, retries duplicate every record, and Case/CaseComment/EmailMessage threading cannot be wired up by source ID.
  • Create custom fields to land SLA and CSAT history. Add Legacy_First_Response_At__c, Legacy_Resolution_At__c, Legacy_SLA_Status__c, and Legacy_CSAT_Score__c on Case. Milestone clocks do not retro-fire on backdated cases, so historical SLA outcomes must land in custom fields.If skipped: Without these fields, every migrated closed case looks SLA-blank and historical CSAT scores are lost.
  • Configure Record Types and Page Layouts for Case. Model each source case type (incident, request, problem, change) as a separate Record Type so the assigned Page Layout and picklist subset can match the source semantics.If skipped: A single Record Type forces every migrated case onto one layout and one StageName picklist, hiding type-specific fields.
  • Restrict picklist values to the canonical set that will receive imported data. On restricted picklists (Case.Status, Case.Origin, Case.Priority, Case.Reason), the bulk loader rejects values that are not in the defined value set. Pre-load the entire source domain or expand the set before import.If skipped: Restricted picklist ENUM rejections cancel entire batches with cryptic STRING_TOO_LONG-style errors.
  • Build Entitlements, Entitlement Processes, MilestoneTypes, and ServiceContract templates. Service Cloud SLA runs through Entitlement + ServiceContract + MilestoneType records tied to Business Hours. Stand these up before Case load so each case can reference an Entitlement.If skipped: Loading Cases before Entitlements exist leaves every case without an SLA reference and breaks Omni-Channel routing that keys on Entitlement.
  • Configure Email-to-Case and Web-to-Case channels. Set up routing addresses, verified domains, and the email service that will accept new email after cutover. Email-to-Case identifies thread parents via ParentId on EmailMessage. Re-create source web-form field mappings so submitted cases land with the correct Record Type, Origin, Priority, and Owner via assignment rule.If skipped: An unconfigured Email-to-Case service drops every customer reply that arrives after go-live.
  • Configure Service Cloud Voice with Amazon Connect or a partner telephony adapter. Service Cloud Voice integrates Amazon Connect natively or via a partner telephony adapter through Open CTI. Decide which model is in scope and provision call-recording storage and the contact center.If skipped: Voice configured after Case load leaves migrated call records unattached to the cases they belong to.
  • Configure Chat (LiveChatTranscript) and Messaging for In-App and Web (MessagingSession). Live chat transcripts land on LiveChatTranscript; Messaging for In-App and Web sessions land on MessagingSession. Each channel needs a deployment / Messaging Channel record before transcripts can be imported.If skipped: Importing transcripts without a deployment record leaves them orphaned and not visible on the agent console.
  • Configure Omni-Channel routing, queues, and skill-based assignment. Define Service Channels (Case, LiveChatTranscript, MessagingSession), Routing Configurations, Queues, and Skill records so post-cutover assignment matches the source policy.If skipped: Omni-Channel configured after agents start using the org floods unrouted work to the default queue.
  • Rebuild source macros, canned responses, and email templates. Build Salesforce Macros and Quick Actions for repeat agent sequences; build Lightning Email Templates for canned responses. Test merge fields against migrated Case and Contact data.If skipped: Agents lose the keystroke shortcuts and templated replies they had in the source, eroding adoption in week one.
  • Deactivate or soften Validation Rules, Workflow Rules, Flows, and Apex Triggers on insert. Validation Rules and Triggers fire on every bulk insert. Insert a bypass condition keyed off a custom checkbox or the migration user to skip them during load.If skipped: Active rules can reject 100% of rows or fire auto-acknowledgement emails to thousands of customers.
  • Pause every integration on the destination side until cutover completes. Disable Marketing Cloud sync, Slack, Outbound Messages, and external system integrations so test loads do not spam customers or partners.If skipped: An active integration during sandbox or production load broadcasts thousands of false notifications.
  • Configure Duplicate Rules and Matching Rules in 'Report only' mode for the load window. Set rules to log duplicates without blocking. Re-enable blocking mode after Phase 6 reconciliation.
  • Communicate the freeze window to all source-system users. Send the exact freeze timestamp, the read-only date, and the destination go-live time at least two weeks in advance.
  • Schedule role-based Service Cloud training for agents, supervisors, and Knowledge authors. Cover Lightning Service Console, Case feed, Omni-Channel acceptance, Knowledge article search and insertion, and Macros usage.
  • Designate first-responder admins for the first 72 hours after cutover. Name primary, secondary, and escalation contacts and publish a triage SLA.If skipped: Without a triage roster, user-reported defects sit unowned and erode trust in the new platform.
  • Brief telephony and chat vendors on the cutover. Confirm with the Service Cloud Voice and Messaging providers that channels are ready and contact flows are tested.
2. Source Export17 tasks
  • Export Accounts (or source companies) with every standard and custom field as UTF-8 CSV. Include the source primary key column so it can populate Account.Legacy_Id__c as External ID.If skipped: Missing the source primary key forces fuzzy matching downstream and reintroduces duplicates.
  • Export Contacts (or source end-users) with every field. Include the source Account-FK column so the loader can wire Contact.AccountId via External ID.
  • Export Cases (or source tickets) with every standard and custom field as UTF-8 CSV. Capture Status, Origin, Priority, Reason, OwnerId-equivalent, AccountId-equivalent, ContactId-equivalent, source primary key, original CreatedDate, ClosedDate, first-response timestamp, resolution timestamp, SLA status, and CSAT score.If skipped: Missing Subject, Status, or Origin blocks Case insert because these are required.
  • Export public ticket comments as a separate CaseComment CSV. Each row maps to a CaseComment with CommentBody (4,000 char limit), IsPublished=true for public replies, and ParentId pointing to the parent Case External ID. Preserve original CreatedDate and CreatedById equivalents.If skipped: Truncated CommentBody silently drops the tail of long agent replies.
  • Export internal notes as a separate CaseComment CSV with IsPublished=false. Mark these as internal so they never become customer-visible on the destination feed.
  • Export email correspondence as a separate EmailMessage CSV. Each row maps to EmailMessage with ParentId pointing at the Case External ID, MessageDate carrying the original send timestamp, HtmlBody and TextBody, Incoming flag, FromAddress, ToAddress, CcAddress, BccAddress, and Subject. Sort by MessageDate so thread order is preserved on load.If skipped: Missing MessageDate causes EmailMessages to sort by load time on the case feed, scrambling the thread.
  • Export inline image and attachment metadata referenced inside email HTML. Capture each Content-ID so the loader can rewrite cid: references to ContentVersion download URLs after binaries land.If skipped: Unrewritten cid: links render as broken images in the migrated case feed.
  • Export Knowledge articles with full version history per article. For every article, pull every version in sequence. Lightning Knowledge stores articles as Knowledge__kav records that require sequential insertion through Salesforce's Knowledge load path.If skipped: Missing intermediate versions breaks the rebuild because version N cannot be inserted without version N-1.
  • Export article-to-category and article-to-data-category-group mappings. These drive Knowledge navigation and visibility filters; without them, articles publish without categorization.
  • Export attachment binaries plus a metadata sidecar. The sidecar maps each file to its parent Case, Contact, or Knowledge__kav source key and captures original filename, file size, and upload timestamp.
  • Export Chat transcripts as a LiveChatTranscript CSV. Capture transcript body, start time, end time, agent identifier, visitor identifier, and parent Case source key where one was created.
  • Export Messaging sessions as a MessagingSession CSV. Capture the message thread, channel identifier, end-user identifier, status, and timestamps.
  • Export Service Cloud Voice call logs. Capture call recording URL, call start and end timestamps, agent identifier, caller phone number, and parent Case source key. Confirm call-recording retention with the telephony vendor before export.
  • Export the user list with role hierarchy and Profile assignments. Capture email, alias, ProfileName, RoleName, manager, and active status so Salesforce users can be mapped to source agents.
  • Export source SLA policy definitions, business hours, and holiday calendars. These become the source side of the Entitlement + MilestoneType + BusinessHours rebuild in Phase 3.
  • Capture screenshots and exports of source automations, reports, and dashboards. These do not transfer; the screenshots seed the rebuild list in Phase 7.
  • Record the exact UTC timestamp of every export. This defines the delta window for the Phase 5 final pull.If skipped: Without timestamps, the delta cannot be computed and last-minute source edits are lost.
3. Transform & Map29 tasks
  • Build a master field-mapping spreadsheet covering every source field. For each row capture: source field, destination object, destination field name, destination data type, transformation rule, required-on-insert flag, picklist constraint, and disposition (load / drop / concat to Description).If skipped: Undocumented mappings cause silent drops and unreproducible loads.
  • Choose the upsert key per object and document it. Standard practice: External ID on every object — Case.Legacy_Case_Id__c, Contact.Legacy_Id__c, Account.Legacy_Id__c, Knowledge__kav.Legacy_Article_Id__c, EmailMessage.Legacy_Message_Id__c, CaseComment.Legacy_Comment_Id__c.If skipped: Using a mutable column as upsert key creates duplicates on every re-run.
  • Resolve every picklist value mismatch between source and destination. Map source ticket-status values to Case.Status, source origin tags to Case.Origin, source priority tiers to Case.Priority, source close-reason to Case.Reason. Confirm every source value maps to a destination value or to a documented 'Other' bucket.If skipped: Unmapped picklist values trigger ENUM rejection on restricted picklists.
  • Decide handling for source fields with no destination equivalent. Options: drop, concat into Case.Description, or create a new custom field. Document one decision per field.
  • Map source agent IDs to Salesforce User IDs. Use a bridging CSV that joins source-agent email to Salesforce User.Username; for orphaned agents assign to a single 'Data Migration' user.If skipped: Unmapped agents default to the migration user and break Omni-Channel agent-workload reporting.
  • Convert all date and datetime values to ISO-8601 with explicit timezone. Salesforce expects YYYY-MM-DDThh:mm:ss.000+0000 for datetimes and YYYY-MM-DD for dates. Localize via the org timezone confirmed in Phase 1.If skipped: Mismatched timezones shift case ClosedDate by a day and break SLA-attainment reporting.
  • Truncate or split source fields that exceed Service Cloud character limits. Case.Subject is 255, Case.Description is 32k, CaseComment.CommentBody is 4,000, EmailMessage.Subject is 255. Build a truncation log so over-length values are preserved in a sidecar.If skipped: Silent CommentBody truncation removes the tail of long agent replies and chops apart customer questions.
  • Re-encode every CSV as UTF-8 without BOM. European spreadsheet exports default to UTF-8 with BOM or to UTF-16. The bulk loader parses UTF-8 without BOM.If skipped: BOM headers turn the first column name into garbage and break field mapping on the first row.
  • Escape commas, quotes, and newlines inside CaseComment and EmailMessage bodies. Wrap values in double quotes; escape inner double quotes by doubling them. Test with a sample that contains all three.If skipped: Unescaped newlines split one logical comment into two, misaligning every subsequent column.
  • Rewrite cid: inline image references in EmailMessage HTML bodies. After ContentVersion binaries land, replace each cid:<content-id> in HtmlBody with the destination ContentDocument download URL. Do this in a second pass after attachments load.If skipped: Skipping the rewrite leaves every inline image broken on the migrated case feed.
  • Validate that every record has a non-null value in every required field. Run a column-by-column null check against the required-field list compiled in Phase 1b.
  • Decide and implement the strategy for original CreatedDate on every object. With 'Set Audit Fields upon Record Creation' enabled, populate Case.CreatedDate, CaseComment.CreatedDate, EmailMessage.CreatedDate at load. CaseHistory is system-generated and read-only; original CaseHistory entries cannot be recreated.If skipped: Losing original timestamps breaks aging reports, first-response metrics, and chronological case-feed ordering.
  • Decide and implement the strategy for case ownership at load time. Choose: best-match by email to existing User, fallback to a single 'Data Migration' user, or hold ownership transfers until UAT sign-off.
  • Decide and implement the strategy for ContentVersion attachments. Either re-upload binaries into ContentVersion, or store as external links in a custom URL field. Re-upload preserves search; external links save File Storage. Standard attachments cap at 25 MB; ContentVersion files cap at 10 GB.If skipped: Re-uploading without staging the binaries first exhausts File Storage and stalls the load.
  • Pre-build the load-order dependency graph. Users → Accounts → Contacts → Knowledge__kav (versioned, sequential) → Entitlements → Cases → CaseComments → EmailMessages → ContentVersion → LiveChatTranscript / MessagingSession / call records → cid: link rewrite pass.If skipped: Loading children before parents leaves dangling foreign keys and forces a full re-run.
  • Reassemble Case threads: Case + CaseComment (public/internal) + EmailMessage with ParentId. For each source ticket, group the parent ticket, every public comment, every internal note, and every email into a single thread keyed off the Case External ID. CaseComment.ParentId and EmailMessage.ParentId both reference the Case External ID. Sort EmailMessages by MessageDate so the timeline view is chronological.If skipped: Missed ParentId wiring leaves comments and emails orphaned, with no parent Case in the agent console.
  • Set EmailMessage.Incoming correctly per row. Incoming=true for customer-to-agent direction, false for agent-to-customer. Without it, Email-to-Case threading post-cutover misreads direction and breaks auto-acknowledgement rules.
  • Stage Knowledge article load via Knowledge__kav versioned model. Lightning Knowledge requires sequential version insertion. Only one draft version can exist at a time and only one version can be published at a time. Load v1 → publish → create draft v2 → publish v2 → repeat per article. Tools that work for Accounts will not translate to Knowledge.If skipped: Parallel version inserts are rejected; tools that fail this constraint break midway through the load.
  • Use PublishingService.publishArticle to move each Knowledge version from draft to published. Call PublishingService.publishArticle programmatically per article version, in order. Capture the success/failure log per article so re-runs can resume from the last successful version.If skipped: Manual publish via UI does not scale beyond a few dozen articles and will not complete inside the cutover window.
  • Map source data categories to Salesforce Data Categories and assign them per article. Data Categories drive Knowledge navigation and visibility; assign on every Knowledge__kav version before publish.
  • Backfill historical SLA outcomes into Legacy_First_Response_At__c and Legacy_Resolution_At__c. Milestone clocks do NOT retro-fire on backdated cases. Active Entitlement Processes only start tracking from the moment a case is associated with an Entitlement post-load. Historical SLA state must land in custom fields, not in MilestoneInstance.If skipped: Expecting Milestones to retro-fire on a closed migrated case leaves every historical SLA outcome unrepresented.
  • Backfill historical CSAT scores into Legacy_CSAT_Score__c on Case. Service Cloud's native CSAT/NPS objects do not accept backdated entries via standard load paths; land the score on the custom field and surface it in reports.If skipped: Without the custom field, historical CSAT trend reporting starts at zero on go-live.
  • Rebuild source automation rules as Salesforce Flow, Assignment Rules, and Auto-Response Rules. Email-to-Case Assignment Rules route by From-address, subject pattern, or custom field. Auto-Response Rules send the first reply. Flow handles field updates that Assignment Rules cannot.
  • Rebuild source macros as Salesforce Macros plus Quick Actions on Case Page Layout. Bind Macros to Lightning Service Console keyboard shortcuts where the source had hotkeys.
  • Map LiveChatTranscript fields and bind to Chat deployments. Transcript body, agent, visitor, start/end time, related Case via Case External ID. Confirm the Chat deployment record exists before transcript load.
  • Map MessagingSession fields and bind to the Messaging Channel record. Messaging for In-App and Web sessions reference a Messaging Channel; pre-populate channel records per source channel.
  • Map Service Cloud Voice call records and recording URLs to Case via External ID. Confirm the call recording storage path (Amazon Connect S3 bucket or the partner telephony adapter's storage) is reachable from Salesforce for playback.If skipped: Recordings hosted on an expired source telephony tenant become unreachable the moment the source contract lapses.
  • Map Omni-Channel queue and skill assignments per Case Record Type. Each Service Channel (Case, LiveChatTranscript, MessagingSession) needs a Routing Configuration; tie migrated records to the queue that matches the source ownership.
  • Translate source SLA policies into Entitlement Processes with MilestoneTypes against Business Hours. Each ServiceContract holds Entitlements; each Entitlement Process holds ordered MilestoneTypes (First Response, Resolution, Escalation). Apply Business Hours from Phase 1b.If skipped: Skipping Business Hours assignment runs every milestone as 24/7 and over-reports SLA breach.
4. Sandbox Test Migration19 tasks
  • Refresh the Full or Partial Copy Sandbox immediately before the test run. A stale sandbox lacks the latest metadata changes from Phase 1b and will not reflect production load behavior.If skipped: Testing against stale metadata hides field-level-security and Validation Rule defects.
  • Load a 1–5% representative sample of each object via Data Loader. Data Loader auto-chunks into batches. Use Workbench for ad-hoc small loads. Load Knowledge__kav via the dedicated Knowledge load path.
  • Spot-check 10 random sandbox Cases field-by-field against source. Verify Subject, Status, Origin, Priority, custom fields, Owner, AccountId, ContactId, CreatedDate.If skipped: Sampling fewer than 10 misses encoding and transformation bugs that affect 1% of rows.
  • Test CaseComment thread reassembly on a sample of 25 Cases. Confirm public comments (IsPublished=true) and internal notes (IsPublished=false) are visible in the correct sections of the agent console and ordered by CreatedDate.If skipped: A misset IsPublished flag exposes internal notes to customers in the Experience Cloud portal.
  • Test EmailMessage threading and ordering on a sample of 25 Cases. Confirm every email lands with ParentId resolved, MessageDate populated, and the case feed renders the thread top-to-bottom in source order.If skipped: Out-of-order EmailMessages scramble customer dialogue and confuse triage agents post-cutover.
  • Test cid: inline image rewriting on EmailMessage HTML bodies. Open 10 sample emails in the case feed and confirm every embedded image renders.If skipped: Broken inline images surface as user-reported defects in week one.
  • Run a Knowledge article version replay against the sandbox. Load one article with at least three historical versions and confirm each draft → published transition succeeded via PublishingService.publishArticle. Verify only one version is published at the end.If skipped: Version replay misordering breaks the published article history irreversibly.
  • Test Entitlement assignment on a sample of open and closed Cases. Confirm open cases attach to the right Entitlement and trigger MilestoneInstance creation; confirm closed cases carry Legacy_First_Response_At__c and Legacy_Resolution_At__c without firing milestone clocks.If skipped: If active Entitlement Processes start re-clocking historical cases, every closed case shows as breached.
  • Specifically test long strings, special characters, NULL, and Unicode emoji. Load a fixture row that exercises maximum-length CommentBody, embedded quotes, embedded newlines, leading/trailing whitespace, NULL, and 4-byte UTF-8 characters in EmailMessage bodies.If skipped: Unicode astral characters silently truncate and corrupt customer names and message text.
  • Test relationship preservation via External ID lookups. Confirm Case.AccountId, Case.ContactId, CaseComment.ParentId, EmailMessage.ParentId, and ContentVersion-to-parent links all wire to the correct record.If skipped: Lookup-by-external-ID failures point comments and emails at the wrong case and corrupt the entire thread hierarchy.
  • Confirm the 'Set Audit Fields' strategy actually preserved CreatedDate. Inspect a sample of sandbox Cases and CaseComments via SOQL to verify CreatedDate matches the source timestamp, not the load timestamp.
  • Run a Validation Rule and Apex Trigger fire-pattern audit during the test load. Use the Bulk Data Load Jobs setup page to confirm rules fired or were bypassed as designed; review any per-row errors emitted by Triggers.If skipped: A Trigger firing on insert can exceed the 150 DML statement governor limit and abort a batch partway.
  • Test ContentVersion attachment upload and email cid: rewrite pass. Confirm files arrive, parent-record links resolve, File Storage consumption matches projection, and cid: references in EmailMessage HtmlBody now point at ContentDocument URLs.
  • Test Chat, Messaging, and Voice channels end-to-end. Trigger a test chat, a test in-app message, and a test inbound call into the sandbox. Confirm LiveChatTranscript, MessagingSession, and call records land and route through Omni-Channel.
  • Run a full-volume rehearsal in the Full Sandbox. Load every record at production volume. Time each step end-to-end. Knowledge version replay is the slowest object — measure articles per hour.If skipped: Skipping volume rehearsal hides Knowledge load throughput issues that only appear at full scale.
  • Extrapolate sandbox timing to the production window. Multiply by 1.5x for safety margin. If the projection exceeds the cutover window, re-plan before Phase 5.
  • Have 2–3 Support Operations domain experts spot-check the sandbox data. Pick known recent cases and a sample of Knowledge articles; ask the expert whether everything looks right at the record and thread level.
  • Document every defect with the failing row, the rule that rejected it, and the fix. Maintain a defect ledger; close each defect before sign-off.
  • Obtain written sandbox sign-off before scheduling production cutover. Sponsor + support-ops lead must sign.If skipped: Proceeding to production without sign-off transfers all sandbox defects into the live org.
5. Production Cutover20 tasks
  • Confirm the source-system freeze is in effect. Query source audit logs to verify no writes in the last 60 minutes before pulling the final export.If skipped: Writes after the freeze produce a silent delta that never reaches the destination.
  • Pull the final source export with timestamps. Capture the delta from the Phase 2 baseline plus any rows whose source CreatedDate or LastModifiedDate falls in the gap window.
  • Disable Workflow Rules, Process Builder flows, Flows, and active Triggers on Case insert. Either deactivate at the rule level or route every load through the bypass-condition pattern created in Phase 1b. Pay specific attention to auto-acknowledgement email rules.If skipped: Active auto-response rules send thousands of false acknowledgement emails to customers during the load.
  • Disable Duplicate Rule blocking; leave matching in 'Report' mode. Re-enable blocking after Phase 6 reconciliation finishes.
  • Disable Entitlement Processes on Case insert. If an Entitlement Process is active on insert, every backdated migrated case will fire milestone clocks. Activate Entitlement Processes only after all closed cases are loaded.If skipped: Active Entitlement Processes during load create false MilestoneInstance breach records on every historical case.
  • Load Users first, then Accounts, then Contacts. Use upsert keyed on the External ID field per object so reruns are idempotent.If skipped: Loading Contacts before their parent Accounts orphans the children and forces a delete-and-reload.
  • Load Knowledge articles via sequential version replay. For every article, insert v1 as draft → publish → create draft v2 → publish → repeat. Use PublishingService.publishArticle per version. This is the slowest object; start it early in the window.If skipped: Parallel version inserts fail; running them serially is the only supported pattern.
  • Load Entitlements, ServiceContracts, and link to Account. Required before Cases land so each Case can reference the right Entitlement.
  • Load Cases via upsert, keyed on Legacy_Case_Id__c. Populate Legacy_First_Response_At__c, Legacy_Resolution_At__c, Legacy_SLA_Status__c, Legacy_CSAT_Score__c at this step.
  • Load CaseComments (public and internal). ParentId references Case.Legacy_Case_Id__c via External ID. Maintain IsPublished flag per row.If skipped: A misset IsPublished flag exposes internal notes to customers in any Experience Cloud portal.
  • Load EmailMessages, sorted by MessageDate. ParentId references Case External ID. Incoming flag set per row. MessageDate carries the original timestamp.
  • Load ContentVersion binaries and link to parent Case, Contact, or Knowledge__kav. These consume the most File Storage; monitor consumption per batch.
  • Run the cid: inline image rewrite pass on EmailMessage HtmlBody. Now that ContentVersion records exist, update each HtmlBody to point at the destination ContentDocument download URL.If skipped: Skipping this pass leaves every inline image broken on the migrated case feed.
  • Load LiveChatTranscript, MessagingSession, and Service Cloud Voice call records. Each references the parent Case via External ID. Confirm Chat deployment and Messaging Channel records exist.
  • Capture bulk load job IDs, row counts, and error files for every load step. Persist these to a runbook log; they are evidence for audit and the basis for Phase 6 reconciliation.If skipped: Without job IDs, error rows cannot be retrieved from the Bulk Data Load Jobs page after the retention window expires.
  • Cross-check destination row count vs. source row count after every load. Variance above 0 must be investigated before moving to the next object.If skipped: Continuing past a variance compounds errors and makes root-cause analysis impossible.
  • On any partial failure, stop and diagnose before re-running. Idempotent External ID upserts let you fix the transform and re-run the same file without duplicates.
  • Re-enable Validation Rules, Triggers, Workflow Rules, Flows, Entitlement Processes, and Duplicate Rule blocking. Verify each is back to its production state before opening the org to agents.
  • Activate Email-to-Case, Web-to-Case, Service Cloud Voice, Chat, and Messaging deployments. These were paused in Phase 1b; bring them online now so new customer traffic lands correctly.
  • Run a smoke test as 3 representative user Profiles. Log in as a Service Agent, a Supervisor, and an Admin; confirm Case console, Omni-Channel acceptance, Knowledge search, and Macros behave as designed.
6. Validate22 tasks
  • Compare per-object record counts: source vs. Salesforce. Run SOQL count queries against Account, Contact, Case, CaseComment (split by IsPublished), EmailMessage, Knowledge__kav, ContentVersion, LiveChatTranscript, MessagingSession, call records. Investigate any non-zero delta.If skipped: Even a single-record gap can mask a Validation Rule that quietly dropped a class of rows.
  • Compare open case count: source vs. SELECT COUNT() FROM Case WHERE IsClosed=false. Tolerance should be zero. Any drift indicates a closed-status mapping defect.If skipped: Open-case drift erodes support-leader trust on day one of go-live.
  • Compare closed case count by month: source vs. Case grouped by ClosedDate. Reconcile by fiscal period to catch ClosedDate timezone shifts.
  • Compare published Knowledge article count: source vs. Knowledge__kav WHERE PublishStatus='Online'. Confirm only one version per article is in Online state.If skipped: Multiple online versions per article confuse search and indicate the version replay was misordered.
  • Spot-check 25–50 randomly selected Cases field-by-field across source and destination. Stratify the sample by Record Type, Status, and Channel so every case type is represented.
  • Verify all custom field values on a sample of 50 Cases. Check Legacy_First_Response_At__c, Legacy_Resolution_At__c, Legacy_SLA_Status__c, Legacy_CSAT_Score__c, plus any business-custom fields.
  • Verify Case-to-Account and Case-to-Contact parent relationships on a sample of 100 Cases. Query Case.AccountId.Name and Case.Contact.Email and confirm both match source.If skipped: External ID lookup misses leave Cases on the wrong Contact, breaking customer search and triage.
  • Verify CaseComment thread reassembly on a sample of 50 Cases. Confirm comment count per Case matches source, ordering by CreatedDate matches source, and IsPublished flags match.If skipped: Wrong IsPublished exposes internal notes to customers and erodes trust permanently.
  • Verify EmailMessage thread reassembly and chronological order on a sample of 50 Cases. Confirm message count per Case matches source, MessageDate ordering renders top-to-bottom correctly, and Incoming flag values match.
  • Verify Knowledge__kav version history per article on a sample of 25 articles. Query for all versions of each article; confirm version count matches source and only one is in Online state.
  • Verify ContentVersion files are accessible and linked to the right Case, Contact, or Article. Open 10 sample files from the Files Related list per parent object type.If skipped: Broken file links surface as user-reported defects in week one and are expensive to retro-fix at scale.
  • Verify cid: inline images render in EmailMessage HtmlBody on a sample of 25 emails. Open the email in the Case feed and confirm every embedded image loads.
  • Verify LiveChatTranscript, MessagingSession, and call records resolve to the parent Case. Sample 10 of each and confirm the related list on the Case shows the transcript or recording.
  • Confirm original CreatedDate is preserved on a 50-record sample of Cases and CaseComments. Query Case.CreatedDate and CaseComment.CreatedDate via SOQL and compare to the source.
  • Confirm EmailMessage.MessageDate preserves the original send timestamp on a 50-message sample. MessageDate drives chronological case-feed ordering; if it was overwritten, the entire thread sorts wrong.
  • Run a GDPR data-residency audit against the Hyperforce region setting. Confirm the org's instance is in the expected EU region for any EU-resident personal data; verify backup region matches.If skipped: Residency violations discovered later require a Hyperforce region migration and DPA renegotiation.
  • Capture Setup Audit Trail and Login History snapshots for the cutover window. Export both to long-term storage as SOC2 / compliance evidence.
  • Confirm Field History Tracking is enabled on the agreed list of Case fields. Standard Field History Tracking retains 18 months and tracks 20 fields per object; document any gaps against the compliance requirement.
  • Run UAT with 3–5 power agents, supervisors, and Knowledge authors. Provide a scripted workflow covering accept a case from Omni-Channel, reply via Email-to-Case, insert a Knowledge article into a reply, run a Macro, and close a case.If skipped: Skipping UAT defers defect discovery to agents on day one when the support load is already peaked.
  • Document every UAT defect with severity and ownership. Triage critical defects before sign-off; defer cosmetic defects to Phase 7.
  • Have UAT users sign off in writing. Capture sign-off in the same defect ledger used in Phase 4.
  • Obtain written sign-off from the migration sponsor before Phase 7. Sponsor must confirm: counts reconcile, sample-record accuracy meets the Phase 0 criteria, UAT critical defects are closed.If skipped: Skipping formal sign-off leaves scope-of-completion ambiguous and reopens the project months later.
7. Post-Migration Cleanup13 tasks
  • Announce go-live to all agents with login URL and the first-responder contact. Include a one-page quick-start covering the Lightning Service Console, Omni-Channel acceptance, and Knowledge search.
  • Run role-segmented training sessions for agents, supervisors, and Knowledge authors. Cover Case feed, Macros and Quick Actions, Knowledge insertion into email, Omni-Channel routing, and Voice/Chat/Messaging accept flow.
  • Set the source system to read-only on the announced date. Block writes but keep reads available for the documented retention period.If skipped: Leaving the source writable encourages agents to keep working in the old system, fracturing the source of truth.
  • Rebuild reports and dashboards in Salesforce. Reports do not transfer; use the Phase 2 screenshots as a build list. Prioritize: SLA attainment, CSAT trend, agent workload, case backlog by Status, first-response time.
  • Activate Entitlement Processes for new cases going forward. Confirm new cases created post-cutover attach to the right Entitlement and fire milestone clocks. Historical cases continue to use the Legacy_* custom fields and do not retro-fire.If skipped: Skipping activation leaves new cases without SLA tracking on day one.
  • Rebuild remaining automations: Flows, Assignment Rules, Auto-Response Rules, Approval Processes. These do not transfer; reconstruct from the Phase 2 capture. Test each against migrated cases before activation.If skipped: Activating untested Flows on top of migrated data can mass-update or mass-email customers.
  • Re-establish integrations: telephony, BI tools, knowledge sync, ticket-bot connectors. Re-authenticate, point at production, and run a smoke test per integration.
  • Re-enable Duplicate Rules in blocking mode. Confirm matching keys still resolve to a single record per entity and that the Duplicate Job report runs clean.
  • Configure Sharing Rules, Role Hierarchy, and Permission Set assignments per support role. Confirm record visibility for each Profile against the agreed access matrix; pay specific attention to Knowledge visibility via Data Categories.If skipped: Over-permissive Sharing Rules expose case data to the wrong team; under-permissive rules block agents from their own queues.
  • Schedule a 30-day post-migration retrospective with the project team. Capture what went well, what surprised the team, and what to change for the next migration.
  • Document the source-system decommission date. Typically 90 days after cutover, after the final retention window. Confirm with Legal and Finance.
  • Archive source-system exports and bulk load job logs to long-term storage. Encrypt at rest, restrict access, and document retention per the policies captured in Phase 0.If skipped: Without retained exports, a forensic question six months in cannot be answered.
  • Close the migration project formally with a final status report. Include: tasks completed, deferred items, final defect count, sign-off list, and a recommended day-30 checklist for the support operations team.

Questions, answered

Migrating to Salesforce Service Cloud: questions

How long does migration to Salesforce Service Cloud take?

A clean helpdesk migration under 25,000 Cases on one Record Type with Email-to-Case runs four to six weeks end-to-end. A multi-channel project with Knowledge re-versioning, Macro rebuild, Entitlement design and Apex regression runs eight to sixteen weeks, including sandbox dry-runs, validation, training and 48-hour hyper-care.

Can I migrate from Zendesk to Salesforce Service Cloud?

Yes — Zendesk is the most common Service Cloud migration source. Zendesk Organizations map to Accounts, Users to Contacts, Tickets to Cases, ticket comments to CaseComment plus EmailMessage. Zendesk Triggers, Automations and SLA policies do not transfer and must be rebuilt as Flows, Process Builder and Entitlement Processes.

Can I migrate from Freshdesk to Salesforce Service Cloud?

Yes. Freshdesk Companies map to Accounts, Contacts to Contacts, Tickets to Cases with conversations decomposed into CaseComment plus EmailMessage on Case `ParentId`. Freshdesk Automations rebuild as Flows or Case Assignment Rules — the practitioner thread for 240-rule rebuild scenarios suggests Custom Metadata Types collapse the rule count cleanly.

Does Service Cloud preserve original CreatedDate on Cases during import?

Only if you file a support case requesting the org-wide Create Audit Fields permission before the migration. With it enabled, CreatedDate, CreatedById, LastModifiedDate and LastModifiedById can be set explicitly on Case, CaseComment and EmailMessage. Without it, every imported row stamps to load day — preserve in Legacy_Created_Date__c fields.

What's the difference between Data Import Wizard and Data Loader for Service Cloud?

Data Import Wizard is a UI tool capped at 50,000 records per import and supports only Leads, Accounts, Contacts, Campaign Members, Solutions, Person Accounts and Custom Objects — Case is unsupported. Data Loader is a desktop client that supports every Standard and Custom Object including Case, CaseComment and EmailMessage.

Can I migrate Knowledge base articles to Service Cloud?

Yes, but Lightning Knowledge uses a versioned model — articles insert as draft Knowledge__kav rows, publish via the Knowledge publish workflow, then re-version sequentially. Standard import tooling that works for Cases does not work for Knowledge. Plan KB migration as a separate workstream using the dedicated publish workflow or a migration tool that wraps it.

What happens to ticket conversation threads and SLA history during migration?

Conversation threads split across CaseComment (short internal notes, public replies) and EmailMessage (full email threads ordered by MessageDate). SLA history is not auto-preserved — Entitlement Milestone clocks do not retro-fire on backdated Cases, so populate Legacy_First_Response_At__c and Legacy_SLA_Breached__c custom datetime fields and rebuild SLA dashboards against those for historical reporting.

Get a quote

Moving to Salesforce Service Cloud?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Salesforce Service Cloud setup with you, then send a quote.

Get a quote