Salesforce DevOps for nCino

Most nCino configuration lives outside the managed package. Here's what upgrading nCino actually involves.

What's hard to deploy

nCino ships as a namespaced managed package, but most day-to-day configuration, loan types, document templates, workflow rules, lives in custom objects inside the subscriber org rather than the package metadata itself. Package upgrades must stay compatible with whatever version each environment is running, and none of that subscriber-side configuration moves with a standard metadata-only deployment.

Where it gets hard

Most nCino config lives outside the package

Loan types, document templates, and workflow rules are custom objects inside the subscriber org, not package metadata, even though nCino itself ships as a namespaced managed package.

Upgrades have to match each org's package version

Subscriber-side configuration doesn't move with a metadata-only deployment, so an upgrade has to land compatible with whatever version each environment happens to be running.

Namespace references complicate cross-org customization

Custom fields and formulas built on top of nCino's namespace reference package components directly, so a subscriber org customization can silently break if it assumes a package version or field that changed upstream.

In practice

How Serpent helps

Serpent supports native 2GP and managed packages on every plan, with dependency resolution and subscriber org version tracking built in, so nCino upgrades and org-specific customization stay compatible with the package version each environment is running. See DevOps for ISVs on Serpent for how package and subscriber org changes stay in sync.

Metadata and data in one deployment flow in Serpent

Typical release for nCino

Task the subscriber-org change
Loan type, document template, or workflow rule edits get tasked alongside whatever Apex or Flow references the nCino namespace.
Check package version compatibility
Dependency resolution flags when a target org's nCino package version doesn't match what the change assumes.
Deploy the package and the subscriber config together
Native 2GP and managed package support ships the upgrade through the same pipeline as the custom object changes.
Version-track every subscriber org
Serpent keeps a record of which package version each environment runs, so drift shows up before it breaks a release.

Common questions

nCino DevOps, answered

Does Serpent deploy nCino's subscriber-org configuration?

Yes. Loan types, document templates, and workflow rules are custom objects, so they deploy and version through Serpent's standard metadata pipeline.

How does Serpent handle an nCino package upgrade?

Native 2GP and managed package support ships the upgrade with dependency resolution that checks the subscriber org's current version before anything deploys.

Can Serpent track which nCino version each sandbox is running?

Yes. Subscriber org version tracking is built in, so mismatches surface before an upgrade ships, not after.

Start free. No credit card, no install, no commitment.

Set up in under 15 minutes. No DevOps hire needed.

Start free Book a demo