Informatica Migration & Data Integration
Last reviewed by Tyler Eastridge
AceMQ plans and supports the move off Informatica PowerCenter to platforms it already supports: Airbyte and Apache NiFi for ingestion, Apache Airflow for scheduling, and Apache Spark or Databricks for transformation. AceMQ engineers lead each engagement and partner data-integration specialists do the platform work, under one AceMQ contract. The work covers inventory, target choice, parallel run, cutover and 24/7 support for the new stack. AceMQ is not an Informatica partner, does not support or patch PowerCenter, and does not rewrite mappings.
A senior engineer, not an SDR. No sales sequence attached.
Without a rewrite programme or a vendor-led replatformFor production incident cover, see AceMQ Open Data Stack 24/7 support.
Customers
Partners
The Problem
Eight problems that teams bring to AceMQ when a PowerCenter estate has to move, from a repository nobody has counted to schedules that live in two places and a parallel run with no definition of equal. If one describes your week, that is where the inventory starts.
The PowerCenter version in production has reached or is reaching the end of Informatica's support, and the next step is undecided
A renewal is due and the only alternative on the table comes from a vendor that sells it
The repository holds thousands of mappings and nobody knows how many still run
Schedules live partly in PowerCenter and partly in an enterprise scheduler, and the dependencies between them are in people's heads
Logic sits outside the mappings, in parameter files, connection objects and pre- and post-session commands
Mainframe or change-capture sources have no obvious replacement
A team wants to use Airbyte, NiFi, Spark or Databricks but cannot say what each replaces and what it does not
A parallel run is needed and nobody has defined what counts as the same output
A good fit if you run PowerCenter, have to decide what comes next, and want an independent written view plus a team that can run the destination platforms. Not a fit if you want mappings converted for you.
Not a fit for small teams with non-critical workloads. AceMQ is not a budget consultancy: we work with enterprises running business-critical and compliance-heavy Open Data Stack.
How it breaks, and the fix
A workflow runs its sessions in dependency order. When one session fails, the links after it decide what happens: the load waits, the target is not refreshed, and the morning reports show yesterday. How the workflow recovers decides how long that lasts.
One mapping fails, the load waits
Extract, two mappings, load and target, as in a PowerCenter workflow
The extract feeds both mappings, both finish, the load runs and the target is refreshed before the morning reports.
Mapping B fails. Mapping A's output is ready but blocked, the load is idle and the target keeps yesterday's data.
Mapping B is fixed and rerun, the load resumes and the target catches up. Whether that needed a manual restart is the question a migration has to answer.
Recovery rules are easy to lose in a move. A PowerCenter session can be set to fail and stop the workflow, fail and let it continue, resume from its last checkpoint, or restart, and a scheduler outside PowerCenter may rerun the whole thing. A replacement scheduler does none of this unless someone writes it down and builds it. The inventory records these settings for every workflow, and the parallel run tests them by failing a task on purpose before the cutover, not after.
Our Services
AceMQ runs five Informatica-related service lines: an estate inventory, target platform selection, pipeline migration planning, 24/7 support for the destination stack, and cutover and retirement. AceMQ does not support PowerCenter itself and does not rewrite mappings.
A counted list of what exists and what is still used, so the migration is sized from facts and the retirement list is as long as it can be.
A vendor-neutral written choice between staying, Informatica's cloud platform and an open data stack, with what each leaves out.
Wave plan, parallel-run design and cutover for the pipelines, scoped to platform and pipeline work and not to rewriting transformation logic.
Emergency response and recurring reviews for the platforms the pipelines land on.
The last mile: switching the schedules, switching off PowerCenter and recording what was kept.
Senior engineers on your account, a 15-minute emergency response, no ticket routing and no junior triage.
24/7 Support
AceMQ support covers the platforms your pipelines move to. You get an AceMQ engineer and a 15-minute first response when a pipeline platform is down or failing, 24/7, with 1-hour, 4-hour and next-day responses at lower severities. PowerCenter itself is supported by Informatica or by third-party providers, not by AceMQ.
P1 escalation path
A replay of one P1, from the first page to the written root-cause analysis
15-minute P1 response, 24/7.
A response time, not a resolution time.
P1 opened, on-call engineer paged
Phone, email or Slack reaches the on-call senior engineer directly, whether the incident is in RabbitMQ, Kafka, Redis, PostgreSQL or Kubernetes. No web form, no tier-1 queue.
Senior engineer on your bridge
A senior engineer who already knows your environment joins a live bridge, so nobody has to re-explain your topology.
Specialists across the stack join
When an incident crosses components, the engineers who know each one join. For RabbitMQ, the path runs to the core team.
Written root-cause analysis
Root cause, the fix applied and the prevention steps, delivered after every P1.
Beyond SLAs — the model behind senior-only, zero-cold-start expert access.
Tickets go to senior engineers briefed on your environment, not an anonymous queue. The proposal states who does the work.
Any ticket can be escalated to a live session with an engineer through calendar booking. No gatekeeping and no approval step.
Scheduled health checks on your deployment and alerts on risks in the versions you run, so problems surface before they reach production.
Release notes and lifecycle dates read against your environment, with an upgrade plan that fits your change windows.
How It Works
An AceMQ Informatica engagement runs in four stages: a scoping call with a quote within 1 hour, a read-only inventory, a written target and wave plan, then waves that run beside PowerCenter until the outputs match. Each stage ends in writing.
Quote within 1 hour
We start from the repository, not the roadmap. An AceMQ engineer asks for the PowerCenter version, number of workflows, source and target systems, the scheduler, where the repository database lives, and what has been decided about the target. A quote request is answered within 1 hour.
Scoped per estate
A read-only inventory of workflows, sessions, mappings, mapplets, parameter files, connections and schedules from the repository and the operating system. It records run history, so workflows that have not run for a year are listed for retirement, not migration.
Scoped per estate
A written plan that maps each group of workflows to a destination, names what has no equivalent, sets the order of waves, and defines what counts as the same output for the parallel run.
Per wave
Each wave runs in the new stack beside PowerCenter, outputs are compared, and the schedule moves when they match. AceMQ supports the new stack 24/7 from the first production wave, with a 15-minute P1 SLA.
A senior engineer, not an SDR. No sales sequence attached.
Moving off PowerCenter
PowerCenter is a data integration platform that bundles ingestion, transformation, scheduling and metadata in one product. An open stack splits them across tools, so the plan starts by deciding which tool takes which job, and who owns data quality and governance rules afterwards. Rewriting the transformation logic in each mapping is application work for your developers or a conversion specialist, and it is the largest part of any move.
Ingestion
Airbyte is built for ELT: it moves data from sources into a destination, including change data capture for databases, and leaves transformation to what runs after the load. Apache NiFi suits file, message and edge flows, with back-pressure and data provenance. Neither replaces a mapping's business logic.
Scheduling
A PowerCenter workflow is an ordered set of sessions with links and conditions, and Apache Airflow expresses the same shape as a graph of tasks with retries and alerts. This part is mechanical enough to plan from the inventory. Recovery rules, such as restarting from a failed session, need to be written down and rebuilt on purpose.
Transformation
The logic in mappings moves to Spark jobs or Databricks workflows, or into SQL in the destination. That is the rewrite we do not do. AceMQ sizes it from the inventory, builds the platform it runs on, and supports the platform once it runs.
Parallel run
Each wave runs in both places. We agree beforehand what counts as equal: row counts, sums on key columns, and how nulls, rounding, ordering and late-arriving data are treated. Differences are explained or fixed before the schedule moves and PowerCenter stops running that wave.
Typical engagements
Typical Informatica engagements from AceMQ: what the environment looks like, what AceMQ assesses or plans, and what the engagement delivers. Each card links to the full write-up.
Solutions
AceMQ covers Open Data Stack end to end. Projects: consulting and implementation, health checks and migrations. Ongoing cover in four tiers, from 24/7 support and incident management to proactive monitoring, managed Open Data Stack on your infrastructure and fully managed Open Data Stack on AceMQ infrastructure, plus end-of-life versions.
Projects
Fixed-scope work led by a senior engineer: architecture and new builds, a health check of what you run today, or a migration with a reversible cutover.
Support and managed services
Four tiers of ongoing cover once you are live. Each tier hands more of the day-to-day work to AceMQ, from a 15-minute emergency SLA to AceMQ hosting and running Open Data Stack for you.
Compare the four Open Data Stack support tiersSide by side
These are the three routes teams weigh at PowerCenter end of support. Informatica sells the first two, and AceMQ helps with the third and writes the comparison without selling any of them. Each row below answers one question about the choice.
| Question | Stay on PowerCenter | Move to Informatica's cloud platform | Move to an open data stack with AceMQ |
|---|---|---|---|
| Where does support come from? | Informatica. For 10.4, Informatica's blog says extended support is available at a premium cost. Third-party providers also exist. | Informatica, as a cloud service. | Each project's community, and AceMQ 24/7 for Airbyte, NiFi, Airflow, Spark and Databricks. |
| What has to be rebuilt? | Nothing, until the version leaves support again. | Mappings and workflows move with Informatica's tools and programme. Informatica describes the route; AceMQ does not implement it. | Ingestion, scheduling and transformation on separate tools. The logic in each mapping is rewritten. |
| What does AceMQ do? | Nothing on PowerCenter itself. AceMQ does not support or patch it. | Writes the options paper. AceMQ is not an Informatica partner and does not implement the cloud platform. | Inventory, target platform, wave plan, parallel run, cutover and 24/7 support of the new stack. |
| What is the main risk? | The next end-of-support date, and a shrinking pool of people who know PowerCenter. | Adopting a new vendor platform on the vendor's timetable. | Rewrite effort in transformation logic, and gaps where there is no like-for-like replacement, such as lineage and mainframe sources. |
| When does it fit? | The estate is small and stable and the support position is acceptable. | You want to stay with Informatica's tooling and accept its platform. | You want platforms you can run yourself or with any provider, and have developers for the rewrite. |
AceMQ gives no Informatica licensing advice. Read your Informatica agreement and Informatica's own lifecycle notice for your version before you choose.
One partner, not five
Open Data Stack rarely fails in isolation. AceMQ covers the full surrounding infrastructure — so one team owns the whole path instead of pointing at each other.
Guides, articles and comparisons
Guides from AceMQ engineers on the platforms an Informatica estate moves to, plus the AceMQ services around them: Airbyte, NiFi, Airflow, Spark, Databricks and data engineering.
FAQs
Five answers on Informatica from AceMQ: whether AceMQ supports PowerCenter, the options at end of support, what each open tool replaces, what AceMQ does not convert, and running both platforms side by side.
Still have questions about Open Data Stack? Email an Expert
No. AceMQ is not an Informatica partner or reseller, produces no Informatica patches and gives no Informatica licensing advice. Support for PowerCenter comes from Informatica or from third-party providers. AceMQ plans the move off it and supports the platforms the pipelines move to.
Informatica's download page lists PowerCenter 10.5.x end of support as 31 March 2026. For 10.4, Informatica's blog says general support ended on 31 March 2024 and extended support is available at a premium cost. The routes are to stay on extended support, to move to Informatica's cloud platform, which Informatica recommends, or to move to another platform. Other data integration alternatives include cloud services such as Azure Data Factory and AWS Glue, which AceMQ does not support. AceMQ writes the comparison and does not sell any of them.
Between them, the jobs PowerCenter does in one product. Airbyte and NiFi take extract and load, Airflow takes scheduling and dependencies, and Spark or Databricks take transformation. None of them reads a PowerCenter mapping, so the logic in each mapping has to be rebuilt.
No. Rewriting transformation logic is application development and is outside AceMQ's scope. AceMQ does the inventory, target choice, platform build, parallel-run design, cutover and ongoing support, and your developers or a conversion specialist rewrite the mappings.
Yes, and that is the safest way to move. Workflows move in waves and each wave runs in both places until the outputs match by rules agreed beforehand. PowerCenter stops running a wave only after that.
Yes. AceMQ works on Open Data Stack in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual contract that covers 24/7 support and proactive reviews. Many teams start ad hoc and move to an annual contract once the first engagement is done.
Every AceMQ proposal is tailored to your requirements: your Open Data Stack environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how Open Data Stack is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.
Let's talk
A senior AceMQ engineer reviews your Informatica estate, tells you what plan fits, and quotes it. Quote requests are answered within 1 hour.
Production incident right now?Email an Open Data Stack Architect
Send us a message and we'll follow up within 1 hour — or book a free 30-min consultation directly.
305-204-2607info@acemq.comPrefer to talk now? Call us directly or use the consultation tab to find a time that works.
