Identify the activity behind the database
An opportunity can contain a request, tasks, correspondence, an offer and a final decision. A flat contact list may preserve none of that sequence. Explain how your organisation used the CRM and whether activities, stages and outcomes remain connected across a defined period.
Salesforce, HubSpot and other platforms are system labels, not a promise of buyer demand or compatibility. Different teams may use the same platform in very different ways. Record significant configuration changes, imports and migrations where they affect the meaning of the records.
Separate historical work from live commitments
Current offers, pricing, negotiations and active customer relationships may need to remain outside a proposed historical scope. Ask whether completed periods or closed opportunities can be distinguished, without creating an export merely to answer the question. A date filter is not itself a rights or confidentiality review.
CRM collections can include personal information, customer-owned material and records received from other sources. Identify these categories and the functions able to review them. A business’s ability to access its platform does not establish permission for every additional use of its contents.
Prepare an activity-and-outcome overview
Describe the types of activities, the approximate history and whether outcomes have a consistent meaning. For example, a lost opportunity may record a reason, or it may be a housekeeping status with little supporting context. Explain that distinction without naming a customer or disclosing commercial details.
Keep quantities clear: contacts, opportunities, tasks and messages are different units. BRIDGERS can discuss the collection at this descriptive level and identify questions before a possible partner introduction. A large CRM is not automatically a licensable asset, and no price per contact is offered.
A practical briefing for this discussion
Use the following prompts to create a short internal overview. Record what is already known, label estimates and leave unresolved points visible. The working document is for your own preparation; it is not a request to send confidential records or evidence through an initial enquiry. A missing detail can become a specific question for a colleague rather than a reason to investigate every system first.
- CRM business purpose and historical period
- Activities connected to opportunities
- Meaning of completion and outcome
- Live commercial work outside the scope
- Origin of contacts and other contributions
| Briefing prompt | Record internally | Next question |
|---|---|---|
| CRM business purpose and historical period | Known, estimated or unclear | Who could clarify this? |
| Activities connected to opportunities | Known, estimated or unclear | Who could clarify this? |
| Meaning of completion and outcome | Known, estimated or unclear | Who could clarify this? |
Questions about this topic
Is the proposal to sell our customer addresses?
No contact-list programme is stated here. The subject is a defined history of business work. Personal information, customer commitments and rights require separate review.
Can we exclude current opportunities?
Record whether historical and live work can be distinguished. Scope and exclusions must be agreed; a technical filter alone does not authorise the remaining collection.
How do we count a CRM archive?
State the unit and subset: opportunities, activities or messages, for example. Avoid a combined total that mixes unlike records or counts the same case repeatedly.