Skip to main content
This guide covers how to migrate an existing CNHI (AFS Connect) integration to CNHI FieldOps. You can migrate at your own pace — both providers run in parallel, and no growers are disrupted until you choose to switch them.

​
What changed

CNHI FieldOps is CNH Industrial’s current API platform. The data you receive through Leaf — field operations, machine files, boundaries — is the same. What changes is how the connection is established. The FieldOps API also supports webhook-based change notifications. Instead of Leaf polling CNH on a schedule, CNH pushes events to Leaf when new data is available. This reduces the delay between when a grower uploads data from their equipment and when Leaf processes it.

​
What you need before migrating

  • A CNH developer account at develop.cnh.com (company-domain email required — Gmail, Hotmail, and other generic domains are not supported).
  • A new FieldOps application registered in the developer portal. This produces a new clientId, clientSecret, and subscriptionKey. Existing CNHI credentials cannot be reused.
  • Each grower must re-authorize through the FieldOps OAuth flow. Existing refresh tokens do not carry over.
  • Growers must have the Farm Manager title in their FieldOps account and must have logged into the FieldOps portal at least once.

​
Migration approach: run both in parallel

Leaf treats CNHI and CNHI FieldOps as separate providers. A single Leaf user can hold both cnhi-credentials and cnhi-field-ops-credentials at the same time. This means you can migrate growers one at a time without disrupting anyone. The recommended approach:
  1. Register your CNHI FieldOps app keys with Leaf:
  1. For each grower you want to migrate:
    • Run the FieldOps OAuth flow (via the Leaf helper or Magic Link)
    • Attach cnhi-field-ops-credentials to the Leaf user
    • Verify data syncs correctly
    • Once confirmed, delete the old cnhi-credentials from the Leaf user
  2. Growers you haven’t migrated yet continue working on the legacy CNHI provider with no disruption.
While both credentials are attached, Leaf syncs from both providers. This may produce duplicate fields or files until you remove the old credential. We recommend verifying the FieldOps connection, then promptly deleting the legacy credential.

​
Identifying FieldOps data in the API

Data from CNHI FieldOps appears in the same Leaf endpoints (fields, files, operations) as legacy CNHI data. The provider field distinguishes the source:
  • Legacy CNHI: "provider": "CNHI"
  • CNHI FieldOps: "provider": "CNHIFieldOps"
You can filter queries by provider (e.g., ?provider=CNHIFieldOps) to see only FieldOps data. During the parallel-run period, the same physical field may appear twice with different provider values.

​
Abbreviated setup steps

For the full walkthrough with code examples in cURL, Python, and JavaScript, see Connect CNHI FieldOps. The key steps:
  1. Get the authorization URL — POST https://cnhi-oauth2-helper.withleaf.io/fieldops/get_url with client_id, client_redirect_url, and production flag.
  2. Redirect the grower — they log in and consent.
  3. Exchange the code for a refresh token — POST https://cnhi-oauth2-helper.withleaf.io/fieldops/get_token with client_id, client_secret, client_redirect_url, and response_url.
  4. Attach credentials to the Leaf user — POST /users/{leafUserId}/cnhi-field-ops-credentials with clientId, clientSecret, subscriptionKey, refreshToken, and clientEnvironment.
  5. Confirm — GET /users/{leafUserId}/cnhi-field-ops-credentials.
If you use Magic Link or Leaf Link widgets to onboard growers:
  1. Register your FieldOps app keys with Leaf:
  1. Add https://widget.withleaf.io as a callback URL in your CNHI FieldOps application on the CNH developer portal.
  2. Update your allowedProviders to include "CNHIFieldOps". During the transition, you can include both "CNHI" and "CNHIFieldOps" so growers can connect through either provider.

​
What to do next

Last modified on April 13, 2026