Aquiva blog
Salesforce ISVs: Why Migrate from 1GP to 2GP Now
Manual packaging in 1GP is a tax on every release. With External Client Apps blocked on 1GP, the migration to 2GP is no longer optional — only the timing is.
AppExchange Independent Software Vendors (ISVs) running on First-Generation Packaging (1GP) face mounting pressure to migrate to Second-Generation Packaging (2GP). Here is the business case, the technical constraint that makes it mandatory, and the practical path.
Speed and revenue impact
Every feature sitting in your backlog is delayed revenue. Manual packaging in 1GP extends release timelines unnecessarily. With 2GP and CI/CD automation, teams compress release cycles substantially by eliminating org-dependent bottlenecks.
Cost reduction and risk mitigation
Manual 1GP processes create what we call the "1GP tax" — operational overhead that shows up as:
- Elevated release coordination costs requiring experienced engineers
- Increased incident probability from human error
- Key-person risk concentrated in whoever holds the packaging knowledge
- Higher support burden and customer satisfaction impact
External Client Apps requirement
A critical architectural constraint forces the issue: External Client Apps cannot be added to 1GP-managed packages. This is an architectural constraint, not a temporary limitation, making migration mandatory for ISVs adopting modern authentication patterns and integrating with external systems.
Technical context
1GP model. Packaging organization is the source of truth; releases involve manual, org-dependent steps that are prone to brittleness.
2GP model. Repository is the source of truth; package versions build programmatically, enabling repeatability, auditability, and automation.
Audience-specific considerations
Early-stage ISVs. Migration requires adopting foundational SDLC practices — version control, scratch orgs, release discipline. The upfront investment eliminates tribal knowledge dependency and reduces incident risk over time.
Mature ISVs. Direct ROI comes from removing the final org-dependent pipeline steps, accelerating releases, and simplifying feature tier operations.
Migration engagement services
Aquiva Labs offers structured migration support:
- 2GP Package Migration with continuity and upgrade safety
- Partner Business Org configuration with Package Visualizer
- SDLC Modernization Advisory tailored to ISV capabilities
- Optional CI/CD pipeline modernization and Connected App-to-ECA migration extensions
Why now
The optimal migration timing is now, before technical debt accumulates further and circumstances force a reactive migration under operational pressure.