Forge Shift#

Forge Shift is for the complex, high-stakes migrations — CPQ → Revenue Cloud and the like — done reversibly, by operators who have done them at scale.

Why it's different from a load#

A migration isn't one load. It's many dependent loads with relationships to preserve, ids to remap from source to target, and an order that matters. Shift is built on a durable execution foundation (Temporal + object storage) so a migration can run for a long time, survive interruption, and be resumed — not restarted from zero.

Reversible#

The same principle as the rest of the platform: a migration step snapshots before it writes, so the migration is reversible rather than a one-way cutover. That's the core selling argument for large migrations — faster and reversible beats a body-shop's irreversible, hand-tooled approach.

Engagement model#

Shift migrations are scoped, fixed-price projects:

• Small — single-object, clean source (e.g. HubSpot contacts → Salesforce).
• Medium — multi-object with relationships (e.g. Zendesk → Service Cloud).
• Large — CPQ → Revenue Cloud and similar, with optional fully-managed execution.

Note: Shift is foundation-stage today (the durable execution + object-storage base is in place); engagements are scoped directly.