Peeklogic helped a global mobility company replace its legacy Informatica middleware with Workato while keeping existing enterprise-client integrations largely unchanged.
The new architecture connected Salesforce with external mobility management systems through standardized Workato workflows, while a custom AWS layer handled complex document processing and large-file requirements.
Project Overview
Industry
Global Mobility / Relocation Services
Client
Global Mobility Company
Project Type
Informatica-to-Workato migration and Salesforce integration modernization
Technologies Used
Salesforce, Workato, AWS, Amazon S3, REST APIs, Apex, Salesforce REST API, Salesforce Files, JSON, OAuth
Key Result
A standardized Workato-based integration architecture that replaced legacy Informatica middleware, minimized changes for existing enterprise clients, improved integration management, and created a reusable foundation for future systems and client onboarding.
Challenge
The client operated a Salesforce-based mobility platform connected with external systems used by enterprise customers. These integrations exchanged assignment, relocation, service, milestone, and document information.
The existing architecture relied on Informatica as the middleware layer. As the environment grew, maintaining and extending the integrations became more complex.
The client needed to modernize the integration layer without forcing enterprise customers to redesign their existing integrations.
Key challenges included:
- Legacy Informatica middleware requiring modernization
- Different data models, identifiers, terminology, and service structures across systems
- Fragmented integration patterns
- Risk of duplicate data and inconsistent records
- Secure bi-directional API communication requirements
- Complex document synchronization and file-size constraints
- Limited error handling, retries, and monitoring
- Increasing data volumes and future client integrations
A major requirement was backward compatibility. Existing clients should continue using the same payload structures and business processes wherever possible.
Ideally, the only required client-side change would be switching to a new API endpoint.
Document processing added another challenge. The legacy integration embedded encoded documents directly into JSON requests together with transactional data. This created large payloads, higher memory usage, timeout risks, file-size limitations, and difficult error recovery.
The migration therefore had to modernize the architecture internally while minimizing external changes.
Solution
Peeklogic replaced Informatica with Workato as the main integration and orchestration layer between Salesforce and external client systems.
Existing inbound and outbound processes were rebuilt in Workato with standardized patterns for API communication, data transformation, validation, routing, error handling, retries, and monitoring.
For inbound integrations, Workato receives external requests, maps the incoming data model to the required Salesforce structure, and creates or updates the corresponding Salesforce records.
For outbound integrations, Salesforce data is transformed into the format required by the external system before being sent through the API.
The document workflow required a different approach. Instead of passing large encoded files through Workato together with transactional data, Peeklogic introduced a custom AWS processing layer.
This allowed the architecture to separate business data from large files while preserving the existing client-facing API behavior.
The resulting architecture assigned clear responsibilities:
- Salesforce: operational platform and system of record for business processes
- Workato: API orchestration, integration workflows, transformation, validation, routing, and error handling
- AWS: large-file processing, transformation, storage, and retrieval
Key Features
1. Informatica to Workato Migration
Peeklogic rebuilt the existing inbound and outbound integration processes in Workato.
The new workflows covered:
- API communication
- Salesforce operations
- Data mapping and transformation
- Validation and business rules
- Integration routing
- Error handling and retry logic
- Monitoring
This created a more standardized integration foundation that can be reused as additional systems and enterprise clients are connected.
2. Backward-Compatible Integration Architecture
The migration was designed to preserve existing client behavior and payload structures wherever possible.
Enterprise customers did not need to rebuild established business processes or redesign their integrations simply because the middleware platform changed.
This reduced the amount of client-side work required during migration and lowered transition risk.
3. Custom AWS File Processing
The legacy architecture embedded encoded documents directly within JSON requests.
Because this approach created payload-size and file-processing limitations, Peeklogic built a custom AWS layer that:
- Accepts the existing request structure
- Identifies embedded file content
- Extracts encoded binary data
- Converts it into an actual file
- Processes and stores documents through AWS
- Separates files from transactional business data
- Connects transferred documents with the correct Salesforce records
Workato can therefore process the business payload without carrying the entire binary file through the integration workflow.
4. Security, Monitoring & Error Management
The new integration foundation introduced standardized controls for secure and reliable communication.
These included:
- API authentication and authorization
- OAuth-based communication
- IP-based access controls where required
- Data and payload validation
- Structured error handling
- Retry mechanisms
- Integration logging and monitoring
- Failure alerts
This gave the support team better visibility into integration health and made troubleshooting and recovery more structured.
5. Controlled Migration & Cutover
The transition from Informatica followed a staged migration process rather than a single replacement event.
The project covered analysis, architecture, development, testing, client validation, production cutover, and post-launch stabilization.
Critical integrations were validated before the legacy middleware was retired.
The Implementation Process
The migration followed a structured sequence:
- Current-state integration analysis
- Target architecture design
- Workato integration foundation
- Inbound integration migration
- Outbound integration migration
- System Integration Testing (SIT)
- User Acceptance Testing (UAT)
- Production endpoint cutover
- Hypercare and post-launch stabilization
Testing included end-to-end scenarios, API payload validation, large-file processing, integration failure handling, and production-readiness checks.
The controlled approach allowed Peeklogic to modernize the internal integration stack while reducing disruption to existing enterprise-client processes.
Results & Benefits
The project replaced the legacy Informatica middleware with a modern Workato-based integration architecture while maintaining continuity for existing enterprise clients.
Key outcomes included:
- Workato became the primary integration and orchestration layer
- Existing client behavior and payload structures were preserved wherever possible
- Inbound and outbound Salesforce integrations were standardized
- Data mapping, validation, routing, and error handling became more consistent
- Custom AWS processing solved large-document and payload-size constraints
- Transactional data and binary files were separated
- Monitoring, logging, alerts, and retry mechanisms improved operational visibility
- Reusable integration patterns created a stronger foundation for future systems
- The architecture was designed to support higher transaction volumes and additional client onboarding
- The new integration model created a foundation for reducing long-term platform and operational costs
Business Value
Replacing middleware in an enterprise environment is not only a technical migration. Existing customers may already depend on established APIs, payloads, document flows, and business processes.
For this project, forcing every enterprise client to change its integration would have increased migration effort and risk.
Peeklogic instead modernized the internal architecture while preserving the external contract wherever possible.
Workato now handles integration orchestration and Salesforce communication, while AWS manages document-heavy processing separately. This reduces the coupling between business data, integration logic, and file handling.
The client also gained a more reusable integration foundation for connecting additional external systems and onboarding future enterprise customers without recreating every integration pattern from scratch.
Conclusion
Peeklogic delivered an Informatica-to-Workato migration that modernized the client’s Salesforce integration architecture without requiring a disruptive redesign for existing enterprise clients.
The solution combined Workato orchestration with custom AWS file processing, standardized API patterns, monitoring, error handling, and a controlled migration process.
The resulting architecture provides a stronger foundation for additional integrations, increasing transaction volumes, document-heavy workflows, and future enterprise-client onboarding.