Solution Engineering18 tasks
Document Migration Planning Guides
Users get written migration and sandbox planning guides: phased migration plans, DevOps and release planning documents, and sandbox refresh checklists they can hand to a team or a customer. Nothing is configured in an org.
Method
How MeshMesh does it
- Starts from the user's situation. This can be a long-running org worked on by several SI teams, or the user's own summary of a sandbox refresh.
- Structures the plan in phases or tracks. Examples are an optimization track for existing release tooling and governance with a conditional transition track, and an assessment, phased plan, use cases per phase, license landscape and open questions for a move to B2B Commerce.
- Fact-checks the user's material and adds what it misses. In one case these were post-refresh configuration areas such as Data 360, CPQ, Field Service, Salesforce Maps, Marketing Cloud Connect, Marketing Cloud Account Engagement, SSO and certificates.
- Delivers in the format the user wants. Examples are a branded master document, a checklist artifact, and a plan marked ready for stakeholder review.
For broader implementation write-ups, see Document Implementation Guides.
Products
Products and features it works with
Bars show how many of this capability's tasks touched each product.