Need Help with ping to okta migration

I got a job and need help with suggestion and guidance WS2 – Inbound and Outbound SSO (SiteMinder → Okta). The real technical migration of up to 155 SSO connections belonging to the "Sydney" application. "Connection" here is defined precisely in the SOW as any inbound or outbound federated SSO integration using SAML or OIDC. Two directions matter: Inbound SSO — a third-party identity provider authenticates users and Okta consumes that assertion (Okta as Service Provider, configuring inbound SAML IdP). Outbound SSO — Okta authenticates and asserts identity to a downstream application (Okta as the IdP, the app is the SP). The scope covers two environments (one non-prod, one prod) and is limited to SSO integration only — Okta API integrations are explicitly out of scope. WS3 – Apigee (Ping → Okta). Migrating up to 1,000 Apigee API integrations from Ping APIs to Okta, via two tracks: