Question
HCL Tech
PL
Last activity: 30 Apr 2025 21:32 EDT
Email migration
Hi Team,
What are the limitations in Pega for email listener and cases?
Can it handle milions of emails migration and convertion to Pega cases?
HCL Tech
PL
Is there any estimating tool we could use to understand the load?
https://academy.pega.com/module/estimating-hardware-requirements/v1
HCA Healthcare
US
@MariuszZ17436180 Pega's email listener can handle large volumes of emails, but performance may degrade when processing millions. To manage this, it's recommended to use a distributed setup with load balancing and batch processing to handle concurrent emails efficiently. Custom parsing activities may be needed to extract relevant information from email content and attachments. For large migrations, using Pega's agent rules and queue-based architecture can help process emails in bulk, reducing system load. Attachments can be stored and linked to cases, ensuring they’re included in the migration. Additionally, ensuring database and system scalability, along with proper error handling and monitoring, is key to successfully migrating and converting emails into Pega cases.
HCL Tech
PL
@SairohithThank you for scalable approach suggestions!
What about having milions of Cases in Pega are there any guidelines? (I've never seen project with more then 100k cases)
Is there server scalling tool?
Is Pega providing any official numbers (e.g email per minute per node) ?
The only numbers I found were in Pega Docs stating 50 emails triggered per 30sec is doable.
Some information on extra processing time is also available:
- large attachments (>10MB) there might be extra processing time due to partial fetch mechanics Pega Docs2
- email throttling Pega Docs3
HCA Healthcare
US
@MariuszZ17436180 Yes, Pega can handle millions of cases, but it requires proper planning and optimization. To manage large volumes, you should use case archiving for resolved cases, optimize your database indexing, and avoid heavy report queries on live case tables. For scaling, Pega supports containerized deployments using Kubernetes, which allows automatic scaling of nodes based on demand. Although Pega doesn’t provide a fixed limit on emails per node, documentation mentions that a listener can handle around 50 emails every 30 seconds under ideal conditions. Processing time may increase with large attachments (over 10MB) due to partial fetch logic. Email throttling is also built-in to prevent overloading the system or mail server. Monitoring with PDC helps you proactively manage performance and scaling.