Getting it live, and keeping it used
The delivery side of CRM implementations: how we run a migration, why CRM data goes bad and what holds, and why adoption is a design problem first.
The service behind these pieces is data migration and integration.
Updated
Pieces on this topic
The CRM migration checklist we use
Moving a CRM is a decision about what to leave behind before it is a technical exercise. The list we run on every migration, in the order decisions get made.
Why CRM data goes bad, and the four fixes that hold
Bad CRM data is not a discipline problem. It is what a system produces when nobody owns a field, a list is a text box and there are four doors in. Four fixes.
CRM adoption is a design problem before it is a training problem
When a new system goes unused, the usual answer is more training. Usually it was designed for the report, not the person’s Tuesday. What we change instead.
Working through this right now?
Everything filed under “getting it live, and keeping it used” is the general case. Bring the specific one: a principal consultant will tell you which of these pieces applies to it, and which does not — usually the more useful answer.