
Salesforce Service Cloud migration
Salesforce Service Cloud migration
Salesforce Service Cloud keeps each support request as a Case, with customer emails as EmailMessage records, internal discussion as case comments or Chatter feed items, and attachments as Files. We move that history from Zendesk into Service Cloud, or from Service Cloud into Zendesk, and scope other routes on a call.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.
- 1000+migrations
- 15 yearsof collective experience
SOC 2 Type IIGDPR compliantHIPAA compliant
Salesforce Service Cloud migration at a glance
- Who it is for
- Support and service operations teams moving case history into Salesforce Service Cloud or out of it, and the Salesforce partners running those projects.
- What moves
- Cases with their email messages, case comments, Chatter feed items and files, plus Accounts, Contacts, Users, queues, custom fields and Knowledge articles.
- What does not move as-is
- Flows, assignment rules, Omni-Channel routing, entitlement processes, macros, reports and dashboards. They are configuration, so we list each one for rebuilding.
- What sets the scope
- Case volume, the emails and feed posts on each Case, file count, Knowledge versions and languages, and the validation and duplicate rules that must pause.
What moves
What moves from Salesforce Service Cloud?
MigrateX moves Cases with their emails, case comments, Chatter posts and files, plus Accounts, Contacts, Users, queues and Knowledge articles.
- Cases
- Email messages
- Case comments
- Chatter feed items
- Files
- Accounts
- Contacts
- Knowledge articles
What does not move
What does not move from Salesforce Service Cloud as-is
Configuration, not data. We list each item in scope so your team can rebuild it in the target.
- Flows and Apex triggers
- What we do: Listed with what each does, then rebuilt as triggers and automations in the destination, or as flows when Service Cloud is the destination.
- Assignment rules and Omni-Channel routing
- What we do: We hand over the queues and rules in use, so routing is set up in the target before cutover.
- Entitlement processes and milestones
- What we do: Set up again: the SlaProcess object cannot be created through the API. Milestone results on closed Cases can move as fields.
Source: Salesforce developer documentation, checked 14 Nov 2026
- Macros and Quick Text
- What we do: Documented with their actions and text, then rebuilt in the target.
- Reports, dashboards and list views
- What we do: Rebuilt on the migrated fields. Original IDs and dates are kept in fields so old reports can be recreated.
- Case History
- What we do: Read-only in Salesforce. The final state of each Case moves; the change log can follow as an internal note on request.
Source: Salesforce developer documentation, checked 14 Nov 2026
- Email-to-Case addresses, email templates and portal pages
- What we do: Set up again. We list the routing addresses so mail switches over in one planned window.
What does a Salesforce Service Cloud migration have to handle?
A Salesforce Service Cloud migration has to choose a home for every comment, set original dates at insert time, get past the org's own validation and duplicate rules, load files against a daily cap, and prove the result in a sandbox. Each of these is decided with your admin before the free sample.
- Three homes for one conversation
- A help desk thread is one list; in Service Cloud it splits across EmailMessage, CaseComment and FeedItem. Moving in, public replies become email messages and internal notes become internal feed items. Moving out, we merge all three by time into one thread and keep each entry's visibility.
Source: Salesforce developer documentation, checked 14 Nov 2026
- Dates and authors are set on insert, or never
- Salesforce accepts original CreatedDate and CreatedById only when a record is created, with the Set Audit Fields upon Record Creation and Update Records with Inactive Owners permissions. Both go on the integration user before the first record is written.
Source: Salesforce Help, checked 14 Nov 2026
- The org's own rules fire on API loads
- Validation rules apply to records created through the API, a blocking duplicate rule rejects the insert, and an active auto-response rule makes SuppliedEmail required on new Cases. Your admin and our engineer agree which rules pause for the load.
Source: Salesforce Help, checked 14 Nov 2026
- Files are versions with links
- Each file is a ContentDocument with one or more ContentVersion records, shared to Cases through ContentDocumentLink. Loading in, FirstPublishLocationId creates the file and shares it with the Case in one transaction, against a cap of 200,000 new versions a day.
Source: Salesforce developer documentation, checked 14 Nov 2026
- A sandbox before production
- Developer and Developer Pro sandboxes copy configuration only and refresh daily. A Partial Copy sandbox takes a 5 GB sample of data every 5 days, and a Full sandbox copies everything every 29 days. The free sample runs in one of them.
Source: Salesforce Help, checked 14 Nov 2026
- Knowledge is licensed and versioned
- Lightning Knowledge is available in Essentials and Unlimited editions with Service Cloud, and for an additional cost in Professional, Enterprise, Performance and Developer editions. Articles keep draft, published and archived versions, so we agree which versions move.
Source: Salesforce Help, checked 14 Nov 2026
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationMigration paths
Where can I move to or from Salesforce Service Cloud?
Routes we run from and into Salesforce Service Cloud. Open a route to see what migrates, or ask us about one that is not listed yet.
From Salesforce Service Cloud
Into Salesforce Service Cloud
191 connectors, all live
Every connector is live, so Salesforce Service Cloud can be paired with any of them. Some of the help desk platforms:
- Freshdesk
- HubSpot Service Hub
- Intercom
- Zoho Desk
- Dynamics 365 Customer Service
- Help Scout
- Gorgias
- Kustomer
- Front
- HappyFox
Platform not listed?
We build new connectors in 2 to 3 days. Tell us what you run and we scope the route with you.
Timeline
Your Salesforce Service Cloud migration, step by step
Estimated total
About 10 business days
end to end
- MigrateXwe run it
- Youyour team acts
- Bothon a call together
Preparation
Day 1-2
Scoping call
Both0.5 dayA 30 minute call with the engineer who will run the migration, to agree the objects, date ranges and volumes in scope.
Connect both platforms
You0.5 dayYou create scoped API credentials on the source and the destination. Nothing is written until you sign off the mapping.
Field mapping review
Both1 dayWe walk through every field, status and group mapping with your team and note the ones that need a decision.
Migration
Day 3-7
Free sample migration of 100 records
MigrateX1 dayA sample of your real records is migrated end to end so you can see the result before the full run.
You review the sample
You1 dayYour team opens the migrated records and tells us what to adjust. We rerun the sample until it is right.
Full migration
MigrateX2-3 daysThe bulk pass runs in dependency order, paced to the destination rate limit. Your team keeps working normally.
Delta sync
MigrateX0.5 dayEverything created or changed during the bulk pass is synced at cutover so nothing falls between the two systems.
Validation
Day 8-10
Validation report
MigrateX1 dayRecord counts per object and per status on both sides, plus every record that needed a default or a placeholder.
Spot checks and sign-off
You1-2 daysYour leads check a random sample and sign off. We stay available for two weeks after go-live.
An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.
See how it works in detailData model
Salesforce Service Cloud data model and limits
How Salesforce Service Cloud holds the records that move, and the vendor limits that set the pace of the migration.
How does Salesforce Service Cloud store support data?
Salesforce Service Cloud stores a support request as a Case and spreads its conversation over three objects: EmailMessage for emails, CaseComment for case comments and FeedItem for Chatter posts. Files sit apart as ContentVersion records, linked to the Case. A migration in either direction has to read or write all of them, in the right order.
| Object | What it holds | How it links |
|---|---|---|
| Case | One support request: subject, description, status, priority, origin (such as Email, Phone or Web) and owner. | Points to an Account and a Contact. Its Status controls IsClosed, which cannot be set directly. |
| EmailMessage | One email sent or received on the Case, with its HTML and text body, MessageDate and an Incoming flag. | ParentId points to the Case. Available when the org uses Email-to-Case or Enhanced Email. |
| CaseComment | A comment of up to 4,000 bytes, published to customers or not. | Child of one Case. IsPublished is the only field the API can change after insert. |
| FeedItem | A Chatter post on the Case feed, in rich text limited to p, a, b, code, i, u, s, ul, ol, li and img tags. | Visibility is AllUsers or InternalUsers. The original author and date can be set during migration. |
| ContentDocument and ContentVersion | A file (ContentDocument) and each of its versions (ContentVersion), including the binary data. | Shared to a Case, email or post through ContentDocumentLink, with its own Visibility setting. |
| User and queue | Agents, and queues, which are Group records whose Type is Queue. | Own Cases. QueueSobject records which objects a queue can hold. |
| KnowledgeArticleVersion | Knowledge articles in draft, published and archived versions, per language. Archived versions live in the article's __kav object. | Classified by data categories, of which Salesforce allows 100 by default. |
| Entitlement, SlaProcess and CaseMilestone | Support terms, the entitlement process (a timeline of milestone steps) and each Case's milestones. | SlaProcess supports query and describe, not create, so entitlement processes are set up in Setup. |
| CaseHistory | The field-by-field change log of each Case. | Read-only: Salesforce history objects can be queried but not created. |
Case
- What it holds
- One support request: subject, description, status, priority, origin (such as Email, Phone or Web) and owner.
- How it links
- Points to an Account and a Contact. Its Status controls IsClosed, which cannot be set directly.
EmailMessage
- What it holds
- One email sent or received on the Case, with its HTML and text body, MessageDate and an Incoming flag.
- How it links
- ParentId points to the Case. Available when the org uses Email-to-Case or Enhanced Email.
CaseComment
- What it holds
- A comment of up to 4,000 bytes, published to customers or not.
- How it links
- Child of one Case. IsPublished is the only field the API can change after insert.
FeedItem
- What it holds
- A Chatter post on the Case feed, in rich text limited to p, a, b, code, i, u, s, ul, ol, li and img tags.
- How it links
- Visibility is AllUsers or InternalUsers. The original author and date can be set during migration.
ContentDocument and ContentVersion
- What it holds
- A file (ContentDocument) and each of its versions (ContentVersion), including the binary data.
- How it links
- Shared to a Case, email or post through ContentDocumentLink, with its own Visibility setting.
User and queue
- What it holds
- Agents, and queues, which are Group records whose Type is Queue.
- How it links
- Own Cases. QueueSobject records which objects a queue can hold.
KnowledgeArticleVersion
- What it holds
- Knowledge articles in draft, published and archived versions, per language. Archived versions live in the article's __kav object.
- How it links
- Classified by data categories, of which Salesforce allows 100 by default.
Entitlement, SlaProcess and CaseMilestone
- What it holds
- Support terms, the entitlement process (a timeline of milestone steps) and each Case's milestones.
- How it links
- SlaProcess supports query and describe, not create, so entitlement processes are set up in Setup.
CaseHistory
- What it holds
- The field-by-field change log of each Case.
- How it links
- Read-only: Salesforce history objects can be queried but not created.
Salesforce Service Cloud objects that hold support data, as of November 2026. Source: Salesforce Object Reference and Knowledge Developer Guide.
Which Salesforce Service Cloud limits set the pace?
Salesforce limits are set per org and per rolling 24 hours, and a migration shares them with every integration already running. These are the allowances that decide how fast Cases, emails and files move into or out of Salesforce Service Cloud, and which native export and import options can carry a full support history.
| Limit | Allowance |
|---|---|
| Daily API allocation | Enterprise: 100,000 calls a rolling 24 hours plus 1,000 per Salesforce licence. Unlimited and Performance: 5,000 per licence. Bulk API calls count towards it. |
| Bulk API 2.0 loads | 150,000,000 records and 15,000 batches a rolling 24 hours. Up to 150 MB a job; Salesforce advises 100 MB because base64 adds about 50%. |
| Bulk API 2.0 exports | 10,000 query jobs and 1 TB of results a rolling 24 hours. |
| New file versions | 200,000 ContentVersion records per 24 hours on Enterprise, Unlimited and Performance; 2,500 on Developer Edition and trials. |
| File size through the REST API | Up to 2 GB per ContentVersion with a multipart request; 50 MB of text or 37.5 MB of base64 without one. |
| Case comment body | 4,000 bytes per CaseComment. |
| Data Export Service | Weekly on Enterprise, Performance and Unlimited, monthly on other editions. Zip files of about 512 MB, deleted 48 hours after the email. Chatter posts and comments cut at 1,000 characters. Source: Salesforce Help |
| Data Import Wizard and Data Loader | The wizard loads up to 50,000 records and does not handle Cases. Data Loader handles 5,000 to 5 million records, Cases included. Source: Salesforce Help |
| External ID fields | 25 per object by default, used to upsert records on the source system's ID. Source: Salesforce Help |
| Data categories | 100 by default; Salesforce support can raise it. Source: Salesforce Help |
Daily API allocation
- Allowance
- Enterprise: 100,000 calls a rolling 24 hours plus 1,000 per Salesforce licence. Unlimited and Performance: 5,000 per licence. Bulk API calls count towards it.
Bulk API 2.0 loads
- Allowance
- 150,000,000 records and 15,000 batches a rolling 24 hours. Up to 150 MB a job; Salesforce advises 100 MB because base64 adds about 50%.
Bulk API 2.0 exports
- Allowance
- 10,000 query jobs and 1 TB of results a rolling 24 hours.
New file versions
- Allowance
- 200,000 ContentVersion records per 24 hours on Enterprise, Unlimited and Performance; 2,500 on Developer Edition and trials.
File size through the REST API
- Allowance
- Up to 2 GB per ContentVersion with a multipart request; 50 MB of text or 37.5 MB of base64 without one.
Case comment body
- Allowance
- 4,000 bytes per CaseComment.
Data Export Service
- Allowance
- Weekly on Enterprise, Performance and Unlimited, monthly on other editions. Zip files of about 512 MB, deleted 48 hours after the email. Chatter posts and comments cut at 1,000 characters.
Source: Salesforce Help
Data Import Wizard and Data Loader
- Allowance
- The wizard loads up to 50,000 records and does not handle Cases. Data Loader handles 5,000 to 5 million records, Cases included.
Source: Salesforce Help
External ID fields
- Allowance
- 25 per object by default, used to upsert records on the source system's ID.
Source: Salesforce Help
Data categories
- Allowance
- 100 by default; Salesforce support can raise it.
Source: Salesforce Help
Salesforce limits that shape a Service Cloud migration, as of 14 November 2026. Source: Salesforce Help and Salesforce developer documentation, linked per row.
Facts checked 14 Nov 2026. Sources: Salesforce developer documentation and Salesforce Help.
Salesforce Service Cloud migration questions
Still unsure? Ask us on the scoping call.
What does a Salesforce Service Cloud migration cost?
The cost of a Salesforce Service Cloud migration follows the Cases in scope and what hangs off them: email messages, case comments, Chatter feed items and files. Knowledge versions and languages, record types and custom objects add scope. You see 100 of your records migrated free of charge first, and a fixed quote follows within 24 hours.
How long does a Salesforce Service Cloud migration take?
The default plan is about 10 business days end to end. On Salesforce the pace is set by your org's daily API allocation, which it shares with every integration it runs, and, when Service Cloud is the destination, by the 200,000 new file versions it accepts in 24 hours. The free sample measures the pace on your own data.
How do I export cases with their emails, comments and files from Service Cloud?
Through the API. MigrateX reads each Case with its EmailMessage, CaseComment and FeedItem records, finds its files through ContentDocumentLink and downloads each ContentVersion. Bulk API 2.0 handles the large tables. The Data Export Service runs once a week at most and cuts Chatter posts at 1,000 characters, so it works as a backup, not as a migration source.
Do original created dates and case owners carry over?
Into Service Cloud, yes, when the integration user has Set Audit Fields upon Record Creation and Update Records with Inactive Owners before the first load, because Salesforce accepts original dates and creators only when a record is created. Out of Service Cloud, Case dates and owners move wherever the destination accepts them on import.
Do validation rules, duplicate rules and flows get in the way of the load?
They can. Salesforce validation rules apply to records created through the API, and a duplicate rule set to block rejects the insert. Before the production load, your admin and our engineer list every rule, flow and auto-response rule on Case, Contact and Account, agree which ones pause, and switch them back on after the delta sync.
Can we test the migration in a Salesforce sandbox first?
Yes, and we recommend it. A Developer or Developer Pro sandbox copies your configuration but no data, which suits the free 100-record sample. A Full sandbox copies all production data but can only be refreshed every 29 days, so book it early if you want a full rehearsal before the production load.
Does Salesforce Knowledge move with its article versions?
The latest published version of each article moves with its translations, and drafts move as drafts. Salesforce keeps archived versions in the article's Knowledge object, so moving those is a choice we make with you. Moving into Service Cloud, check your licence: Lightning Knowledge is available in Essentials and Unlimited editions with Service Cloud, and for an additional cost in Professional, Enterprise, Performance and Developer editions.
What access do you need to our Salesforce org?
A dedicated integration user with API access and permission on the objects in scope, read-only when Service Cloud is the source. We never ask for a System Administrator login. MigrateX is SOC 2 Type II, GDPR and HIPAA compliant, a DPA and BAA are available, and each migration runs in its own isolated environment.
Guides
Guides for a Salesforce Service Cloud migration

Start with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.





