Handoff is critical: poor handoff = months of confusion, bug recurrence, lost knowledge.
Handoff package:
Documentation:
- Architecture diagram (current state).
- Object/field catalog with purpose and owner.
- Automation catalog (flows, triggers, validation rules).
- Integration catalog with troubleshooting steps.
- Security model documentation.
- Decision log (architectural decisions with rationale).
- Operational runbooks (common admin tasks).
- Hypercare lessons learned.
Knowledge transfer sessions:
- Walkthroughs of complex automation/code.
- Q&A with the receiving team.
- Pair-time during early days post-handoff.
- Recorded videos for asynchronous reference.
Access & accounts:
- Receiving team gets necessary admin access.
- Connected Apps, Named Credentials, integration accounts documented and transferred.
- Vendor relationships (AppExchange support contacts) introduced.
Issue runbooks:
- "If X happens, do Y" guides for known issue types.
- Escalation paths (when to call the original consultancy back).
Warranty / support period:
- 30-90 days of "if you find a defect, we fix it" coverage.
- Defined hours / response SLAs.
Common pitfalls:
- Tribal knowledge stays with consultants — receiving team can't replicate fixes.
- No warranty period — receiving team blamed for project-team mistakes.
- Documentation written for consultants, not for the receiving team — wrong audience.
- Handoff happens at deadline, no time for absorption — receiving team caught off-guard.
Senior consultants treat handoff as a deliverable in its own right — planned, scoped, executed deliberately. Client should feel confident, not abandoned.