How long does a Pega Platform to Salesforce Sales Cloud migration take?

Most Pega-to-Salesforce migrations complete in 48–72 hours of clock time for under 50,000 total records across Data Objects. Larger setups with 500k+ records, multiple custom Data Objects, or operator lists requiring manual user provisioning extend to 7–14 days. The longest planning step is mapping Pega case hierarchies and Decision Table values to Salesforce Record Types and pick-lists before data extraction begins.

Will my Pega workflows, Decision Rules, and automation logic migrate to Salesforce Flow?

No. Pega workflows, Service Cases, Decision Rules, Routing Rules, and Skills-based assignment logic are application-layer rules that do not export from Pega. They must be rebuilt in Salesforce using Flow, Process Builder, or Apex. FlitStack migrates data only. We provide a Pega workflow audit export — a structured document listing every Pega rule, its trigger condition, and its action — to serve as a rebuild reference for your Salesforce admin or implementation partner.

What does a Pega work case become in Salesforce?

Each Pega work case becomes a Salesforce Opportunity. The Pega case ID is stored in Source_Case_ID__c for traceability and delta-run de-duplication. Case status maps to Opportunity StageName via value mapping per case type, with probability re-applied. Assignment history is preserved in custom datetime fields since Salesforce does not track case-assignment chains natively. Parent-child case hierarchies are represented via a Parent_Case_ID__c custom lookup field to maintain relationship continuity.

Can I migrate Pega custom Data Objects to Salesforce custom objects?

Yes. Pega custom Data Object classes migrate one-to-one to Salesforce custom objects with the __c suffix. Many-to-many relationship tables in Pega require Salesforce junction objects — custom objects with two Lookup fields — since standard Salesforce objects do not support many-to-many associations without junction objects. We include junction-object creation in the schema planning phase before data loads begin.

How are Pega Operators mapped to Salesforce Users if they don't have email addresses?

Pega Operators without populated email addresses cannot auto-resolve to Salesforce Users. We flag every unresolved operator during the discovery phase. Your options are: populate operator email addresses in Pega before extraction, pre-create Salesforce User records for those operators, or assign their records to a fallback User. Records landing on a fallback owner lose individual ownership attribution — this should be a conscious decision documented in the migration plan.

Does the migration affect my Pega Platform instance during cutover?

No. FlitStack uses scoped read-only API access on Pega — your team continues processing cases in Pega during migration. A delta-pickup window of 24–48 hours captures any records created or modified in Pega between the initial extraction and the go-live moment. After go-live, Pega transitions to read-only status. You control the window length based on how quickly your team can complete final case updates before Salesforce becomes the system of record.

What happens to Pega SLA deadlines and urgency scores?

Pega SLA timestamps migrate as custom datetime fields on the Salesforce Opportunity (e.g., SLA_Deadline__c). Pega urgency scores (0–100 scale) migrate to a custom Number field (Urgency_Score__c). SLA-breach automation must be rebuilt in Salesforce Flow with time-based triggers — Salesforce Sales Cloud has no native SLA monitoring object. We document the Pega SLA configuration in the migration deliverable so your Salesforce admin can reconstruct deadline logic in Flow.

Pega Platform to Salesforce Sales Cloud Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Pega Platform stores business data in customizable Data Objects organized around Pega's case-management and work-party model. Salesforce Sales Cloud uses a structured CRM schema anchored by Account, Contact, Lead, and Opportunity objects, with custom fields carrying the __c suffix and relationships enforced through lookups and junction objects. The fundamental architectural shift is from Pega's process-centric case threads to Salesforce's entity-centric relationship model. We extract Pega data via the Pega REST API and Data Set exports, map work objects to Salesforce Opportunities or custom objects depending on record type, and translate Pega assignments to Salesforce OwnerId lookups by email resolution. Pega's workflow rules, Decision Rules, and routing logic are application-layer artifacts that do not export — they require Salesforce Flow or Apex rebuilding. Case hierarchies with parent-child relationships need custom lookup fields or junction objects to represent multi-level nesting. Activity history including case assignments, status changes, and timestamps migrates as custom datetime fields on Opportunity records since Salesforce does not natively track case-assignment chains. The migration runs through Salesforce Bulk API to handle high record volumes efficiently, with field-level validation and a reconciliation diff before final commit to ensure data fidelity.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Pega Platform

What's pushing teams away

Annual licensing at enterprise tier plus 500-user minimum creates a high fixed cost that smaller teams cannot justify, especially when headcount fluctuates.
Steep learning curve and specialized certification requirements mean most business teams cannot modify workflows without certified Pega developers.
Version upgrades routinely deprecate rules and automation patterns, forcing costly remediation projects every 18–24 months.
Strict UI customization limits force teams to accept Pega's structural constraints, leading to subpar customer-facing experiences compared to modern platforms.
Support accessibility is tiered—smaller organizations report difficulty getting timely assistance from Pega's support organization.

Choosing

Salesforce Sales Cloud

What's pulling them in

The AppExchange marketplace with 5,000+ prebuilt apps gives enterprises integrations for nearly every business workflow without custom development.
Native Einstein AI for lead scoring, opportunity insights, and predictive forecasting adds intelligence without a separate platform purchase.
Territory management, multi-currency support, and advanced forecasting satisfy the needs of complex B2B sales organizations with structured revenue teams.
Slack, Tableau, and CPQ are deeply integrated into the core platform, keeping the sales stack unified for teams already in the Salesforce ecosystem.
Organizations with a large, established Salesforce implementation choose it because switching costs — integrations, custom code, trained admins — are prohibitive.

Object mapping

How Pega Platform objects map to Salesforce Sales Cloud

Each row shows how a Pega Platform object lands in Salesforce Sales Cloud, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Pega Platform

Data Object (Case/Work)

maps to

Salesforce Sales Cloud

Opportunity

1:1

Fully supported

Pega work objects translate to Salesforce Opportunities with stage mapping from Pega Status to Opportunity StageName using value-based mapping per case type. Each Pega case becomes one Opportunity record; parent-child case relationships require custom Parent_Case_ID__c lookup fields or junction objects in Salesforce to represent multi-level case hierarchies correctly.

Pega Platform

Data Object (Customer/Party)

maps to

Salesforce Sales Cloud

Account + Contact

many:1

Fully supported

Pega parties with individual identities map to Salesforce Contacts, while organizations map to Accounts. When a Pega party represents both an individual and an organization (e.g., a contact at a company), we create both Account and Contact records and link them via the AccountId field on the Contact for relationship traceability.

Pega Platform

Operator

maps to

Salesforce Sales Cloud

User

1:1

Fully supported

Pega Operators are resolved to Salesforce Users by email match against the User Email field. Unmatched operators are flagged before migration begins, requiring your team to either provision Salesforce users first or assign records to a fallback user. Operator Skills and Work Baskets require manual rebuild using Salesforce Queues and Criteria-Based Sharing rules.

Pega Platform

Assignment (Case Assignment)

maps to

Salesforce Sales Cloud

Opportunity OwnerId

1:1

Fully supported

Pega assignment history (who held the case and when) is preserved as custom datetime fields on the Opportunity since Salesforce does not track assignment chains natively. The final assignee becomes the Opportunity OwnerId, and prior assignee timestamps are stored in custom datetime fields for audit continuity.

Pega Platform

Data Transform (Status History)

maps to

Salesforce Sales Cloud

Custom datetime fields on Opportunity

1:1

Fully supported

Pega case status transitions are captured as a serialized JSON custom field (e.g., Status_History__c) because Salesforce lacks native audit logging for field-value changes without Field History Tracking enabled on each field individually.

Pega Platform

Custom Data Object

maps to

Salesforce Sales Cloud

Custom Object (__c)

1:1

Fully supported

Pega custom Data Object classes migrate one-to-one to Salesforce custom objects with the __c suffix. Relationship tables in Pega that model many-to-many associations require Salesforce junction objects — custom objects with two Lookup fields each — since standard Salesforce objects do not support many-to-many relationships without junction objects.

Pega Platform

Pega File Attachment

maps to

Salesforce Sales Cloud

Salesforce Files (ContentDocument)

1:1

Fully supported

Pega file attachments are downloaded from Pega storage and re-uploaded to Salesforce Files linked to the target Opportunity, Account, or Contact via ContentDocumentLink. Salesforce's 25MB per-file limit applies to ContentVersion uploads; files exceeding this are flagged for manual handling or chunked into multiple ContentVersion segments.

Pega Platform

Pega Note / Annotation

maps to

Salesforce Sales Cloud

Note / ContentNote

1:1

Fully supported

Pega notes and annotations migrate as Salesforce Notes (ContentNote). Rich-text formatting is preserved where the Pega note uses a supported HTML subset. Notes are linked to the parent record (Opportunity, Account, or Contact) via ContentDocumentLink to maintain association.

Pega Platform

Data Page (Reference Data)

maps to

Salesforce Sales Cloud

Custom Object or Custom Settings

1:1

Fully supported

Pega reference data pages containing lookups and pick-lists translate to Salesforce custom objects or Custom Settings depending on whether the data is org-wide configuration or record-specific. Pick-list values from Pega Decision Tables require value-by-value mapping to Salesforce picklist fields during schema planning.

Pega Platform

Pega SLA / Commitment

maps to

Salesforce Sales Cloud

Custom fields on Opportunity

1:1

Fully supported

Pega service-level commitments attached to cases migrate as custom datetime fields (e.g., SLA_Deadline__c) because Salesforce Sales Cloud lacks a native SLA tracking object without add-ons. Urgency scores migrate to a custom Number field; rebuilt SLA monitoring can use Salesforce Flow with time-based triggers for deadline evaluation.

Pega Platform	Salesforce Sales Cloud	Compatibility
Data Object (Case/Work)	Opportunity1:1	Fully supported
Data Object (Customer/Party)	Account + Contactmany:1	Fully supported
Operator	User1:1	Fully supported
Assignment (Case Assignment)	Opportunity OwnerId1:1	Fully supported
Data Transform (Status History)	Custom datetime fields on Opportunity1:1	Fully supported
Custom Data Object	Custom Object (__c)1:1	Fully supported
Pega File Attachment	Salesforce Files (ContentDocument)1:1	Fully supported
Pega Note / Annotation	Note / ContentNote1:1	Fully supported
Data Page (Reference Data)	Custom Object or Custom Settings1:1	Fully supported
Pega SLA / Commitment	Custom fields on Opportunity1:1	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Pega Platform gotchas

High

Version upgrades deprecate rules and break existing applications

High

Constellation UI migration requires explicit rule rewrites

Medium

Pega Robotics requires separate export tooling

Medium

Data Set exports require chunked reads for large volumes

Medium

Decision Rule logic does not port automatically to non-Pega destinations

Salesforce Sales Cloud gotchas

High

Workflow Rules and Process Builder are retired

High

Bulk API batch quota exhaustion during large imports

Medium

Storage overage billing is non-obvious

Medium

Account-Contact many-to-many relationship mapping

Low

Territory and team member import ordering dependencies

Pega Platform gotchas		Salesforce Sales Cloud gotchas
Severity	Issue	Severity	Issue
High	Version upgrades deprecate rules and break existing applications	High	Workflow Rules and Process Builder are retired
High	Constellation UI migration requires explicit rule rewrites	High	Bulk API batch quota exhaustion during large imports
Medium	Pega Robotics requires separate export tooling	Medium	Storage overage billing is non-obvious
Medium	Data Set exports require chunked reads for large volumes	Medium	Account-Contact many-to-many relationship mapping
Medium	Decision Rule logic does not port automatically to non-Pega destinations	Low	Territory and team member import ordering dependencies

Pair-specific challenges

Pega case threads do not map to a single Salesforce object natively

Pega's case model stores related work items as threads with parent-child relationships, SLA deadlines, and assignment chains. Salesforce Opportunities do not have a native thread concept — they are flat records with a stage and an owner. We map each Pega case to one Opportunity and store parent-case references in a custom lookup field (Parent_Case_ID__c). If your Pega deployment uses multi-level case hierarchies, the mapping to Opportunity and custom junction objects must be defined case-type by case-type before migration runs, or data will land with broken parent links in Salesforce.
Operator-to-User resolution breaks when Pega operators lack email addresses

Pega Operators are identified by pzPrincipalName and may not have email addresses populated, especially in on-premises deployments where operator IDs are Windows/SAML principal names. Salesforce OwnerId requires a valid User record. Before migration, your Pega admin must either populate operator email addresses in Pega or your Salesforce admin must pre-create User records for each operator without an email. We flag every operator that resolves to zero Salesforce users before migration begins, but records assigned to unresolved operators land on a fallback user — losing individual ownership attribution.
Pega SLA commitments require custom field reconstruction in Salesforce

Pega SLAs store deadline timestamps and businessCalendar references that control working-hours calculations. Salesforce Sales Cloud has no native SLA object — time-dependent commitments must be rebuilt as custom datetime fields (SLA_Deadline__c) plus Salesforce Flow processes that evaluate elapsed time against business hours. The Pega SLA urgency levels do not translate to Salesforce priority pick-lists without manual value mapping per case type, and automation of SLA-breach escalation must be coded in Flow or Apex.
Pega Decision Table values require value-by-value pick-list mapping

Pega Decision Tables store domain-specific pick-lists such as risk_rating, product_line, and region codes as controlled vocabularies. Salesforce pick-lists are org-wide or global value sets with restricted values. We cannot bulk-import Pega Decision Table values into Salesforce pick-lists — each distinct value must be mapped individually during the schema planning phase. If Pega uses hundreds of unique decision-table values across multiple custom properties, this mapping work can extend the planning timeline significantly and may require coordination with your Salesforce admin to configure global value sets.
Pega file attachments exceeding Salesforce's 25MB limit require chunking or manual re-upload

Pega's attachment storage handles large files without platform-level size caps. Salesforce Files enforce a 25MB per-file limit on ContentVersion uploads via API. We chunk files above this threshold into segments and re-assemble them in Salesforce as a single ContentDocument with multiple ContentVersion records. However, PDF thumbnails and inline previews are not generated for chunked uploads, and your team must manually verify file integrity post-migration for large attachments to confirm successful reassembly.

Migration approach

Six steps for a successful Pega Platform to Salesforce Sales Cloud data migration

Discover Pega data model and export via API

FlitStack connects to your Pega environment via REST API using service account credentials with read access. We enumerate all Data Object classes, their fields, and relationship rules. A Data Set export pulls records in CSV/JSON format. We profile field cardinality, null rates, and pick-list distributions to surface data-quality issues before schema planning begins. The Pega export runs against a staging copy of your Pega instance to avoid impacting production case processing.
Map Pega objects to Salesforce schema and resolve operators

We generate a schema mapping plan that assigns each Pega Data Object to a Salesforce standard or custom object. Operator IDs are resolved against your Salesforce user list by email; unmatched operators are reported with the option to pre-provision users or use a fallback owner. Custom fields are created in Salesforce Object Manager with appropriate types (Text, Number, DateTime, Picklist) before any data lands. Record Types are defined per Pega case type for page-layout scoping.
Run sample migration with field-level diff

A representative slice of 100–500 records migrates first, spanning the main Data Object types, operators, and file attachments. We generate a field-level diff between the Pega source and Salesforce destination, verifying case ID preservation, status-to-stage mapping, operator resolution, and file linkage. You review the diff before the full run commits. Any pick-list unmapped values are identified and corrected in this phase.
Execute full migration with delta-pickup window

The full record set loads via Salesforce Bulk API in batches. A delta-pickup window of 24–48 hours captures records modified in Pega during the migration window. Every operation is logged in an audit trail; one-click rollback reverts the org to pre-migration state if reconciliation fails. After rollback window closes, your team transitions to Salesforce as the system of record and Pega enters read-only status.
Validate record counts, relationships, and file integrity

Post-migration, we run reconciliation queries comparing Pega record counts against Salesforce record counts by object type and status. We verify that Account-Contact links resolve correctly, that Opportunity OwnerIds point to active Users, and that ContentDocumentLink records attach files to the correct parent records. A migration report with record counts, error logs, and skipped records is delivered for your IT team's sign-off.

Platform deep dives

Context on both ends of the pair

Pega Platform

Source

Strengths

Handles millions of cases per year with built-in queuing, escalation, and SLA tracking that scales without additional infrastructure.
Low-code Case Management lets business analysts configure workflows without deep developer involvement, improving time-to-production for rule changes.
AI-powered Next-Best-Action and predictive analytics are embedded directly into case processing without requiring a separate decisioning engine.
Rich integration layer supports REST, SOAP, JMS, and database connectors out of the box, reducing custom integration work for enterprise systems.
Strong regulatory compliance features including audit logging, approval workflows, and segregation of duties satisfy financial and healthcare governance requirements.

Weaknesses

500 named user minimum and 350,000 case annual minimum create prohibitive costs for organizations that do not operate at enterprise scale.
Separate licensing for Pega Robotics means not all platform capabilities are included in the base Pega Platform license, adding hidden cost complexity.
Strict UI customization constraints mean external-facing interfaces cannot match modern UX standards without significant workaround development.
Version upgrade cadence deprecates rules and automation patterns regularly, forcing customers into costly remediation projects to maintain compatibility.
Cloud pricing opacity and annual billing requirements make it difficult to predict total cost of ownership before committing.

Salesforce Sales Cloud

Destination

Strengths

Largest enterprise app ecosystem in CRM with 5,000+ AppExchange integrations covering nearly every vertical workflow.
Native Einstein AI delivers lead scoring, opportunity insights, and predictive forecasting without a third-party layer.
Advanced territory management, multi-currency, and flexible forecasting satisfy complex B2B revenue structures.
Deep platform extensibility: Custom Objects, Apex, Flow, and the Metadata API allow full schema customization.
Well-documented REST API, Bulk API, and Composite API with published rate limits for programmatic migration.

Weaknesses

Pricing model is layered and opaque in practice: per-seat fees plus storage overages, add-on subscriptions, and annual uplifts compound to 30–40% above sticker price.
Workflow Rules and Process Builder are deprecated, forcing all orgs onto Salesforce Flow — a migration task that catches many teams by surprise.
Steep administrative complexity: meaningful configuration requires a dedicated Salesforce admin or consultant.
API rate limits are edition-gated (100k/day base for Enterprise) and easily exhausted by large historical imports without throttling.
Data export is exportable via Data Loader but preserving relationship integrity across 30+ objects requires careful ETL sequencing.

	Pega Platform Source	Salesforce Sales Cloud Destination
Strengths	Handles millions of cases per year with built-in queuing, escalation, and SLA tracking that scales without additional infrastructure. Low-code Case Management lets business analysts configure workflows without deep developer involvement, improving time-to-production for rule changes. AI-powered Next-Best-Action and predictive analytics are embedded directly into case processing without requiring a separate decisioning engine. Rich integration layer supports REST, SOAP, JMS, and database connectors out of the box, reducing custom integration work for enterprise systems. Strong regulatory compliance features including audit logging, approval workflows, and segregation of duties satisfy financial and healthcare governance requirements.	Largest enterprise app ecosystem in CRM with 5,000+ AppExchange integrations covering nearly every vertical workflow. Native Einstein AI delivers lead scoring, opportunity insights, and predictive forecasting without a third-party layer. Advanced territory management, multi-currency, and flexible forecasting satisfy complex B2B revenue structures. Deep platform extensibility: Custom Objects, Apex, Flow, and the Metadata API allow full schema customization. Well-documented REST API, Bulk API, and Composite API with published rate limits for programmatic migration.
Weaknesses	500 named user minimum and 350,000 case annual minimum create prohibitive costs for organizations that do not operate at enterprise scale. Separate licensing for Pega Robotics means not all platform capabilities are included in the base Pega Platform license, adding hidden cost complexity. Strict UI customization constraints mean external-facing interfaces cannot match modern UX standards without significant workaround development. Version upgrade cadence deprecates rules and automation patterns regularly, forcing customers into costly remediation projects to maintain compatibility. Cloud pricing opacity and annual billing requirements make it difficult to predict total cost of ownership before committing.	Pricing model is layered and opaque in practice: per-seat fees plus storage overages, add-on subscriptions, and annual uplifts compound to 30–40% above sticker price. Workflow Rules and Process Builder are deprecated, forcing all orgs onto Salesforce Flow — a migration task that catches many teams by surprise. Steep administrative complexity: meaningful configuration requires a dedicated Salesforce admin or consultant. API rate limits are edition-gated (100k/day base for Enterprise) and easily exhausted by large historical imports without throttling. Data export is exportable via Data Loader but preserving relationship integrity across 30+ objects requires careful ETL sequencing.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Pega Platform to Salesforce Sales Cloud

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Pega Platform

Salesforce Sales Cloud

How Pega Platform objects map to Salesforce Sales Cloud

What specifically takes care here

Six steps for a successful Pega Platform to Salesforce Sales Cloud data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Pega Platform to Salesforce Sales Cloud migration cost

What are you migrating?

Frequently asked questions about Pega Platform to Salesforce Sales Cloud data migrations

Can't find your answer?

Related migrations to explore

Move from Pega Platform.
Land in Salesforce Sales Cloud, intact.

Migrate from Pega Platform to Salesforce Sales Cloud

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Pega Platform

Salesforce Sales Cloud

How Pega Platform objects map to Salesforce Sales Cloud

What specifically takes care here

Six steps for a successful Pega Platform to Salesforce Sales Cloud data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Pega Platform to Salesforce Sales Cloud migration cost

Frequently asked questions about Pega Platform to Salesforce Sales Cloud data migrations

Can't find your answer?

How long does a Pega Platform to Salesforce Sales Cloud migration take?

Will my Pega workflows, Decision Rules, and automation logic migrate to Salesforce Flow?

What does a Pega work case become in Salesforce?

Can I migrate Pega custom Data Objects to Salesforce custom objects?

How are Pega Operators mapped to Salesforce Users if they don't have email addresses?

Does the migration affect my Pega Platform instance during cutover?

What happens to Pega SLA deadlines and urgency scores?

Related migrations to explore

Move from Pega Platform. Land in Salesforce Sales Cloud, intact.

Move from Pega Platform.
Land in Salesforce Sales Cloud, intact.