Hello Theo,

Yes, the deeplink url is based on the application id / alias and the host of indicium.
Those application id’s are almost never the same between iam / sf.
Also the host in the deeplink url contains the sf alias in sf environment , but in iam environment that would need the iam alias.

So in short, no deeplinks made in a sf environment do not work on iam environment.

To extend the answer of ​@Edo Spijker . His answer is about the communication with metasource Indicium, to get the definition of the application for example.

Deeplinking is about sending the user to a particular subject or to start a processflow in the UI. For these purposes, your URL has to work with application aliases instead of ids to make them SF/IAM independent.

You can configure an alias at your runtime configuration in the SF:
https://docs.thinkwisesoftware.com/docs/sf/runtime_configuration#application-id-and-alias

In IAM use the same alias on the related Application. The alias can be configured in the form.

Your deeplink URL will look like:
https://server/universal/#application=my_alias/subject=xxx/subjectVariant=yyy

or
https://server/universal/#application=my_alias/processflow=xxx

So using aliases, your deeplink URL should work for both.