Moving data flows into NiFi from other integration tools and scripts, and moving existing NiFi deployments between topologies and platforms.
Replacing Talend Open Studio or Talend Studio jobs with NiFi flows after Qlik retired the open-source edition: which job types map to NiFi, which belong in a batch transformation tool instead, rebuilding connections and running both in parallel.
Moving SSIS packages that copy files, call APIs and load databases into NiFi flows: mapping data flow tasks to record processors, connection managers to controller services, scheduling to NiFi run schedules and what to keep in SQL.
Moving flows from Cloudera Flow Management or Cloudera DataFlow to self-managed Apache NiFi 2: exporting versioned flows from NiFi Registry, replacing Cloudera-specific bundles, Cloudera Manager monitoring and the 2.x upgrade path.
Turning scattered cron jobs, shell scripts and Python loaders into managed NiFi flows: listing and fetching instead of polling scripts, back pressure instead of overloaded targets, provenance instead of log hunting, and which scripts are not worth moving.
Re-pointing NiFi flows that wrote to HDFS, Hive or HBase toward S3, Azure Data Lake Storage or Google Cloud Storage and Apache Iceberg tables, since those Hadoop components are gone from NiFi 2.
Growing from one NiFi node to a cluster: coordination through ZooKeeper or Kubernetes, primary-node-only processors, load-balanced connections, repository layout per node, session affinity behind a load balancer and redesigning flows that assumed one node.
Moving a VM-based NiFi cluster onto Kubernetes: persistent volumes for repositories, leader election through Kubernetes Leases instead of ZooKeeper, session affinity at the ingress, secrets for certificates and a cutover plan for queued data.
Switching NiFi cluster coordination and state from ZooKeeper to Kubernetes Leases and ConfigMaps: the leader election implementation property, service account permissions, lease prefixes for several clusters in one namespace and state migration.
Relocating a running NiFi cluster: offloading and decommissioning nodes, draining queues versus moving repositories, Site-to-Site for a staged cutover, certificate and hostname changes, and validating with provenance.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.