DataCode

About

The two things an Informatica exit needs are almost never in the same person.

It needs someone who has actually led one — not scoped it, not overseen it — and it needs a delivery practice that uses AI properly rather than as a line in a proposal. The engineers with twenty years of enterprise integration behind them are mostly not working this way. The people fluent in AI-assisted delivery have mostly never opened a PowerCenter mapping. DataCode was founded to put both in one team, and to train consultants into the combination so the capability is reproducible rather than sitting in two heads.

The founders

The experience that makes an Informatica exit go well is concentrated in very few people, and at a large firm those people are on the proposal rather than in your repository. Here they set the standard, and they check it.

Zack Karmali

Founder — Data Integration & Cloud Modernization

Fort Lauderdale, Florida

Eighteen-plus years building and moving enterprise data platforms, with Informatica at the centre of the whole arc — PowerCenter from version 5.1 forward, and IDMC since it was IICS. Has led three enterprise-wide PowerCenter-to-IDMC migration programmes: Toyota North America, Intertape Polymer Group and F&G Annuities & Life. On one of those he leads the workstream retiring the whole on-premise estate — batch ETL, B2B exchange, managed file transfer, the synchronous web-services tier and change data capture — onto Azure Logic Apps, Service Bus, API Management, Integration Account and Key Vault, with over 250 production workflows live as measured in August 2026. He does that work in a lead role on the client’s own programme, leading a team of their developers and a business analyst. AI-assisted conversion is the working engineering practice, and Azure DevOps deploys every artifact. B. Information Systems, McGill University.

  • Informatica PowerCenter · IDMC / IICS · PowerExchange CDC
  • Azure Service Bus · Logic Apps · API Management · Integration Account · Data Factory
  • Microsoft Fabric · Synapse · Dataverse · Azure DevOps
  • AWS S3 · Redshift · Glue
  • SQL / PL-SQL · Python · Spark / PySpark · Kimball modelling · Control-M

Cezary Opacki

Founder — Data Integration & Legacy Platforms

Poland

Has led multiple enterprise IDMC migrations, retiring PowerCenter, B2B, MFT and DX estates onto IDMC and Azure — the same estate shape and the same destination as the programme Zack is running now. Brings the legacy-platform depth most data consultancies no longer have: AS/400 and IBM i, UNIX and Java alongside Python. Leads DataCode’s EU delivery capacity and vets the consultants working alongside it, so an engagement can scale past two people without losing the senior accountability that makes it worth hiring us.

  • Informatica PowerCenter · IDMC / IICS migration delivery
  • Retiring PowerCenter, B2B, MFT, DX, Web Services Hub and change-data-capture estates onto IDMC and Azure
  • AS/400 (IBM i) · UNIX
  • Java · Python
  • EU delivery leadership

A Florida practice, US-delivered by default

DataCode is based in Fort Lauderdale, Florida, and every engagement is deliverable entirely within the United States. Where your agreements permit it we also have EU delivery capacity behind us — and we tell you that before an agreement is signed rather than after, because plenty of enterprise agreements restrict processing outside the US and finding that out late is nobody’s idea of a good start.

US-based, and US-only whenever you need it

The practice is Florida-based and every engagement can be delivered US-only, with US data residency, for the agreements that require it — healthcare, financial services, anything federal. It is the default posture, not an accommodation we make reluctantly, and it is priced up front rather than discovered mid-project.

A senior engineer leads. Always.

One named senior engineer owns your engagement and is accountable for every artifact that reaches your environments — not a coordinator, not an account manager, and not someone you meet at kickoff and never again. Working to that lead: consultants trained into our method and personally vetted by a founder, named and under written agreement, disclosed to you before they start rather than discovered in a status call. The founders do not staff every engagement and we will not pretend they do. What they do is set the standard and check it themselves.

EU capacity where your contracts allow it

One founder is in Poland, an EU member state, so where you permit it GDPR applies directly, Article 28 processor terms and EU-enforceable IP assignment are the default rather than a negotiation, and the working day overlaps yours by three to five hours. It is a capability we offer, never something we route your data through quietly.

How we work with you

Comfortable behind an integrator

A large share of this work reaches us as a subcontract to a system integrator or staffing partner already holding the programme. We are set up for that paperwork and we are content to be invisible on the org chart.

We say what we do not do

There is a written list, and you get it during scoping. A consultancy that claims every technology on your slide is telling you something about its sales process rather than its engineering.

Start a conversation