https://community.cloudera.com/t5/Support-Questions/NiFi-Using-existing-controller-service-in-a-custom-processor/m-p/306121#M222698 <P><a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/75126">@ravisro</a>&nbsp; &nbsp;This is a great question.&nbsp; I would love to see some of the NiFi pros here respond.&nbsp; However, you may only find a better response on NiFI Mailing list or ApacheNiFi slack:</P><P>&nbsp;</P><P><A href="http://nifi.apache.org/mailing_lists.html" target="_blank">http://nifi.apache.org/mailing_lists.html</A>(invite link for slack channel here)</P><P>&nbsp;</P><P>In the meantime, one of the ways i have accomplished this in the past, is documenting the root level Controller Service Ids for each environment (DEV,STAGING,PROD) and swapping these into the template before importing the template to the environment.&nbsp; &nbsp;It's a clunky solution, but it works.&nbsp; &nbsp;I have used this since before NiFi Registry.&nbsp; With Registry in the mix,&nbsp; I am forced to use the NiFI API to update the flows to appropriate controller service.&nbsp; Again clunky, which is why I would love to hear more comments from other community members.</P><P>&nbsp;</P><P>If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post.</P><P>&nbsp;</P><P>Thanks,</P><P>Steven</P> Mon, 16 Nov 2020 17:41:58 GMT stevenmatison 2020-11-16T17:41:58Z