No DHIS2 connector yet — and often you should keep DHIS2 anyway.
There is no DHIS2 connector in the product. There is also a fair chance you should not want one: if your indicators are national health system indicators reported into a ministry, DHIS2 is where they belong and Karagem is not an argument against that.
Not supportedNo connector. Data moves by CSV or the REST API; see below on whether you need it at all.
Where the two genuinely differ
DHIS2 is a national health information system: aggregate reporting up an administrative hierarchy, on a data model designed for ministries. It is very good at that and has been for fifteen years.
Karagem is programme-level M&E for an implementing organisation — a grant with its own logframe, its own targets, its own funder formats, and field collection that has to work with no signal. Those are different jobs, and organisations frequently do both.
If you do both
The usual shape is that programme data lives in Karagem, and the subset that is a national indicator is reported into DHIS2 on the ministry’s schedule. That transfer is a CSV today.
A connector would automate it, and it is a reasonable thing to build. It is not built. Saying so is more useful to you than a page implying otherwise and a discovery call three weeks later.