@ykv05

You can check if the Pega stream service is running by making a simple programmatic health check before starting migration. One way is to call the /stream/health or /prweb/PRRestService/stream/healthcheck REST endpoint if exposed in your environment, which will return the service status. Another way is to use the SystemRuntimeAPI or ClusterManagement API in Pega, where you can query the state of nodes and see if any node is configured with the Stream service role. You can also check the MBeans via JMX, where stream nodes publish their availability. In custom scripts, you may run a lightweight Kafka client connection test since Pega stream internally uses Kafka, and a failed connection means the service is not available. For more automation, you can set up a job scheduler that pings the stream service and logs or alerts the status, so your migration program can check this flag before running. This ensures you do not start migration if the stream service is down.

@ykv05

Pega Stream is backed by Kafka, and there is no OOTB way to to verify Stream availability. 

Would you be able to ping the Kafka client from Pega using a Custom Code and check the connectivity?

you would have to write a custom Java code for this to create an instance 'KafkaProducer' Class using the instance of 'Properties', which will hold the values for 'bootstrap servers', 'key serializers' and 'value serializers.', and chcek if this kafka client is reachable. 

You can set up a Job Scheduler which would query the kafka stream servers periodically and store the result in a DSS which you can refer in your data migration logic before execution.