Service 09
Migration: Einstein Copilot → Agentforce
Move what works, retire what never did, and be honest about the difference.
Copilot was assistive; Agentforce is autonomous. A migration is not a lift-and-shift, because the failure modes change: an assistant that suggests a wrong answer is annoying, and an agent that takes a wrong action is a problem. We treat it as a re-scoping exercise with reuse where reuse is safe.
Typically 8–12 weeks depending on the size of the existing action library.
Inventory and triage
Every existing action, prompt template, and Flow assessed for reuse, rework, or retirement. Most estates carry more dead weight than their owners expect.
Autonomy re-scoping
Each capability is re-examined for what happens when it runs unattended. Some get promoted; some get a confirmation step; some stay assistive on purpose.
Parallel run
Old and new run side by side on shadow traffic until the new one is measurably better, not just newer.
Cutover and rollback
A dated cutover with a rollback that has actually been rehearsed.
Also in services
Agentforce Strategy & Readiness Assessment
Three weeks to find out whether you are ready, and which agent to build first.
Read Service 02Agent Builder & Custom Agent Development
Topics, actions, instructions, and the unglamorous work of making an agent behave.
Read Service 03Agentic Workflow & Process Design
Redesigning the work, not just automating the version of it you already have.
ReadStart with the assessment.
Three to four weeks, a fixed fee, and an answer we are willing to say out loud — including if the answer is no.