- You are a small firm. Why would we hire you over a large integrator?
- Because the senior name on our proposal is the person in your repository. At a large firm it is not, and everybody involved knows it. Our founders have led these migrations themselves, a senior engineer leads every engagement we take, and anyone working to that lead has been vetted by a founder rather than assigned by a resourcing spreadsheet. We are the right choice when you want that experience applied directly, and the wrong choice when you need forty bodies next month — in which case we are happy to work behind an integrator who has them.
- Where is the work actually done?
- The practice is based in Fort Lauderdale, Florida, and every engagement is deliverable entirely within the United States — that is the default, and it is what we assume unless you tell us otherwise. One founder is in Poland, so where your agreements permit it we also have EU capacity behind us, which most clients find an advantage: GDPR applies directly, Article 28 processor terms and EU-enforceable IP assignment are the default, and the working day overlaps the US East Coast by three to five hours. Where your agreements restrict processing to the United States — common in healthcare, financial services and anything federal — we deliver US-only and price it separately. We will never quietly route your data somewhere your contract forbids.
- How do we know AI has not silently changed our business logic?
- Because we test it against the system it replaces. Row-level parity testing between the old pipeline and the new one is part of every conversion wave, and the results are yours. Nobody has to take the AI on faith, including us.
- What automation percentage do you achieve?
- We will not quote one before seeing your estate, and we would treat any firm that does with suspicion. Published figures for automated ETL converters cluster around 70% out of the box, and the remainder is the part that decides whether a migration lands. The assessment tells you what your specific number looks like.
- Should we move to IDMC, or off Informatica entirely?
- It depends on what your estate actually does, and the assessment is designed to answer exactly that. We have delivered both. IDMC is the shorter path and keeps the licensing relationship; Azure-native usually costs dramatically less to run but is a genuine rebuild. We will show you the numbers for both and we do not earn more from either answer.
- Do you support the estate after it is migrated, or hand it over and leave?
- Either, and it is your call. Most migrations end with a handover to a team that has never seen the system, which is how a clean cutover becomes a bad quarter. We offer a monthly managed-run retainer instead: scheduler and pipeline operations, failure triage with AI-assisted root-cause analysis against your estate’s own definitions, runbooks generated from the estate and kept current, and fixes shipped through the same versioned pipelines as the original build. It is scoped to US business hours — two people cannot honestly sell you 24/7 cover, and we would rather say so than find out together at three in the morning.
- How is anything you build versioned and released?
- Every artifact goes through Azure DevOps pipelines across environments — versioned, reviewed, reproducible, and rolled back if it misbehaves. The same discipline you would apply to application code, applied to integration code, which is still unusual in this corner of the industry. It is also what makes the managed-run offer possible: fixing something in production is the same reviewed, versioned path as building it in the first place.
- Your site shows numbers from a migration. Whose work was that, exactly?
- Zack’s. He led the data-integration workstream on the client’s own programme, in a lead architecture and engineering role, with a team of their developers and a business analyst — and before DataCode existed. DataCode as an entity has delivered no engagement yet, and if your supplier form asks for past performance performed by the supplier, that is the honest answer and we would rather give it now than have you find it in week ten. What the firm brings is the person who did that work and the method he used.
- Can we speak to that client?
- Not yet. We are seeking written naming and reference permission and we will tell you the day it lands. Until it does we will not name the client, publish their costs or describe their systems — and we would treat a vendor who did so about someone else as a warning about how they would treat us. What we can offer instead is a technical deep-dive: walk your architect through the migration mechanics, the parity approach and the cutover sequencing, on your estate, in as much depth as they want.
- What does a migration like that cost us in your time?
- We will not quote you a figure from someone else’s programme, and it is worth saying why rather than dodging it: that effort was not ring-fenced, so any hours number we gave you would be reconstructed rather than recorded, and we do not quote reconstructed numbers. What we do instead is size yours. The assessment produces a per-object effort model for your estate, classified by what converts, what converts partially, and what has no equivalent and has to be rebuilt. That third bucket is what destroys fixed-fee migrations, and it is invisible in an object count.
- Who actually does the work when an engagement is bigger than a couple of people?
- A senior engineer leads it and stays accountable for every artifact that reaches your environments — that does not change with the size of the engagement. Working to that lead are consultants trained into our delivery method and vetted personally by a founder, which is a deliberately different thing from being assigned by a resourcing spreadsheet: nobody joins because they were available. You get their names, in writing, before you sign, along with where they sit and what paperwork covers them.
- What do you not do?
- We do not do streaming-first architecture, infrastructure-as-code delivery, container platform work, or analytics-engineering transformation layers. We build the pipelines that feed those, and we will tell you when you need someone else rather than learning on your budget.
