ICS-20099 · ICS-10994 · "iar modified outside of integration design editor"

Connect your OIC.
Migrate everything.

Paste your OIC pod URL and a Designer credential. ERPHive lists every integration in your instance and migrates the ones you pick to runnable flow.yaml files — versionable, diffable, deployable to Cloudflare. We use your creds once, then forget them. (Self-host customers keep this entirely on their infra.)

Connect to your OIC instance

Paste your OIC pod URL + Designer credentials. We list every integration, you pick which to migrate. Creds are used once, never stored. Self-host customers run this on their own infra.

01

Connect

Paste your OIC pod URL + Designer credentials. ERPHive calls the OIC lifecycle REST API to enumerate every project and integration in your instance.

02

Pick + migrate

Choose any integration. ERPHive pulls the IAR via GET /integrations/{id}/archive, parses the project XML and XSL mappings, and emits a typed flow.yaml.

03

Run

Deploy the result to a sandbox env on us. From there: connect a real Oracle pod, promote to dev/test/prod via config, never re-import IARs again. ERPHive is the runner; OIC becomes the legacy.


Or drop a single .iar.

No OIC pod handy? Drop an exported archive. Same translator, same output — flow.yaml plus the original XSL mappings preserved alongside, plus a gap list for the build agent.

project.xml (extracted from .iar)
<icsflow>
  <application id="13" type="REST"
    connection="CORE_OIC_REST"
    binding="outbound"/>
  <application id="29" type="SOAP"
    connection="CORE_FIN_SOAP_BIPUB_REPORT"/>
  <processor type="transformer" id="24"/>
  <processor type="transformer" id="69"/>
  <orchestration>
    receive → transformer →
      invoke(SOAP) → transformer → reply
  </orchestration>
</icsflow>
flow.yaml (ERPHive)
// click drop zone above