On-Prem to Cloud Data Migration via Informatica
Challenges
Intertek’s critical datasets were spread across multiple on-prem databases, limiting analytics scalability and cloud accessibility. The initiative focused on modernising existing Informatica ETL workflows to enable governed, stable cloud-based analytics without replacing the existing toolset.
Outcome
100% response and resolution against SLA
Solution
Managed Services
Challenges
Solution
Technology Stack
Outcomes
Intertek’s data environment had grown complex over time with five critical on-prem databases across Singapore and Houston, increasing analytics demand and rising governance expectations. When the decision was made to initiate an On-Prem to Cloud Data Migration, the objective was clear to modernise without disruption. But existing Informatica investments, cross-region latency and strict compliance requirements meant this would require engineering precision, not a simple lift-and-shift. What followed was a disciplined Informatica ETL Modernisation effort executed within constraints. Secure agent architecture, embedded masking and controlled schema evolution became central to stabilising ingestion while enabling cloud scalability. This case study explores how that transformation was delivered.
Client Problem
When Intertek initiated its On-Prem to Cloud Data Migration, the objective was very clear. It was a strategic move to modernise core datasets, improve accessibility with scalable loud analytics without disrupting ongoing operations. However, the environment they were moving from was not simple and also lacked uniformity.
Business Context
Intertek operates across multiple regions, dealing with critical systems supporting testing, inspection, and certification workflows. Key business datasets were distributed across multiple on-prem databases. Their leadership eagerly needed Cloud accessibility for analytics scalability, strong governance controls and operational stability during transition. At the same time, Intertek had an active Informatica subscription. This clearly meant it was not a tool replacement project but an Informatica ETL Modernisation effort executed within a constrained ecosystem in place.
Technical Pain Points
Multi-region, multiple sources
Intertek has dealt with data that is from multiple regions and from different sources, including:
Four SQL Server databases in Singapore
One Oracle database in Houston
They had to follow different protocols, cross-region latency and varied infrastructure constraints, which introduced inherent extraction instability.
Keeping Informatica was the first constraint
Migration had to be delivered using Informatica IICS secure agent architecture. Introducing alternative ingestion tooling was not viable.
Sensitive data requirements
Intertek’s data included sensitive information, which required real-time masking of those fields before any cloud persistence. Along with this, governance had to be embedded right from the beginning, not patched later.
Frequent schema evolution
Their source systems evolved frequently. Schema updates disrupted ETL jobs, causing weekend patching cycles that created recurring downtime risk.
Operational Impact
Pipeline breakages from schema churn
Manual recovery cycles
Weekend operational coordination
SLA risk exposure
Intertek did not just need migration, they needed structural stability.
Root Cause Analysis
Before jumping directly into solving the challenges, Cloudaeon experts conducted an in-depth root cause analysis. One thing was clear for Intertek that the risk was architectural.
Cross-Region Topology & Latency
Singapore and Houston extractions introduced unavoidable network variance. Without disciplined placement of secure agents and deterministic restart semantics, reliability degraded into manual firefighting. The challenge here was not connectivity, it was a predictable behaviour under network variability.
Governance Before Landing
Intertek’s compliance requirements meant sensitive fields could not land unmasked, not even temporarily. A downstream masking strategy would expose data in logs or staging layers. A field-level data masking pipeline had to be embedded directly into ingestion stage.
Schema Volatility as Technical Debt
Frequent schema updates broke pipelines because mappings were not engineered for change tolerance. No versioning discipline. No structured rollout pattern. For Intertek, stabilising ingestion required operational engineering rather than reactive fixes.
Tool Constraint Amplification
Because Informatica had to be used, success depended on the correct utilisation of Informatica IICS secure agent architecture, which enabled:
Proper agent isolation
Controlled scheduling patterns
Log-based monitoring discipline
Explicit recovery workflows
Informatica was not solving complexity automatically. It had to be engineered correctly.
Solution Architecture
Cloudaeon implemented a secure, agent-based ingestion architecture designed specifically for Intertek’s cross-region environment.
Source Layer (On-Prem)
4 × SQL Server databases (Singapore)
1 × Oracle database (Houston)
Connectivity Layer
Dedicated VMs hosted Informatica Secure Agents, bridging on-prem sources to the cloud ingestion layer while adhering to enterprise security constraints. This architecture reduced unpredictable latency behaviour, ensured secure extraction and provided controlled retry and restart logic.
Ingestion Patterns
It was a balanced mix of:
Incremental loads
Full-load jobs
CDC pipelines
This eventually structured cross-region ETL and CDC migration approach ensures freshness while enabling controlled backfills and resilient recovery.
Governance-in-Flight
A purpose-built field-level data masking pipeline was embedded directly into Informatica IICS. Sensitive attributes were masked before cloud persistence, thereby ensuring compliance integrity.
Ops + Control Plane
Informatica scheduler + triggers for business-aligned orchestration
Log-based monitoring via Jumpbox (bastion host)
Structured triage and recovery protocols
Intertek’s ingestion platform shifted from reactive ETL to structured SLA-driven data platform operations.Shape
How We Delivered
We took a step-by-step engineering approach and solved one challenge at a time.
Pipeline Build and Hardening
Cloudaeon engineered and stabilised Intertek’s ETL pipelines within Informatica IICS secure agent architecture with:
CDC implemented selectively
Incremental + full-load strategies engineered for recovery resilience
Failure behaviour tested under operational scenarios.
We carried out a disciplined Informatica ETL Modernisation, which was an optimisation within constraints.
Secure Connectivity Implementation
Secure Agents were deployed on dedicated VMs. The agents were aligned with Intertek’s security policy and regional network realities, which were deliberately placed and performance-aware.
Governance Embedded into Ingestion
Sensitive fields were masked within ingestion flows, ensuring no exposure across staging layers. Governance was built right from the beginning and not added on later.
Scheduling, Monitoring and Recovery
Business-frequency job orchestration
Jumpbox-based log inspection
Faster triage cycles
The platform evolved into structured SLA-driven data platform operations.
Schema Evolution + Weekend Coordination
Frequent schema updates were managed through controlled change discipline:
Field additions incorporated without destabilisation
Pipeline logic updated without service interruption
Weekend patching coordinated to protect weekday analytics
For Intertek, ingestion stability became engineered, not reactive.
Future Tooling Advisory
While execution remained within Informatica, Cloudaeon also evaluated alternative ingestion platforms for long-term scalability and cost efficiency. We advised Intertek without disrupting delivery inside the mandated toolset.
Technology Stack
Informatica Intelligent Cloud Services (IICS)
Informatica Secure Agents on dedicated virtual machines
CDC pipelines + incremental loads + full-load jobs
Jumpbox (bastion host) for operational diagnosis
Source systems: SQL Server (Singapore) + Oracle (Houston)
Outcomes
Cloudaeon’s implementation made a huge difference for Intertek with:
100% response and resolution against SLA
100% data availability
Zero data loss
No service-impacting ingestion failures
Five complex source systems onboarded into stable BAU:
SMART
GSCC
GSCC Audit
iCare GTS
Interlink
The On-Prem to Cloud Data Migration for Intertek was completed without operational regression with long-term stability embedded into the architecture at every stage.
POD & Managed Ops Transition
Intertek appreciated Clouadeons technical capability, style of working and proactive recommendations for best practices. Eventually, this engagement evolved beyond implementation into ownership.
Solution
Secure-agent ingestion architecture, CDC/incremental patterns and governance-in-flight were established for Intertek.
POD (Change + Stability)
A dedicated engineering POD was deployed that managed:
Schema evolution
Pipeline enhancements
Weekend operational coordination
Stability preservation
Managed Ops
Intertek’s ingestion environment transitioned into steady-state SLA-driven data platform operations. This ensured that reliability did not degrade post-go-live. The operating model was clear:
Solutions → POD → Ops
Cloudaeon’s involvement started with specialised engineering, progressed to controlled change and continued with operational ownership. Shape
Conclusion
Intertek’s journey demonstrates that a successful On-Prem to Cloud Data Migration is not just about moving data, it is about engineering stability, governance and operational discipline into the foundation of the platform. Cloudaeon transformed a fragile ingestion process into a resilient and cross-region data backbone. If you are planning a complex migration constrained by existing tooling, multi-region topology or strict governance requirements, let’s talk. Our engineering-led approach ensures your migration is not only delivered, but built to operate reliably at scale.