Australian Carers Guide (AC Guide) / Project case study
2021Recorded work
Move the sales history
into Pipedrive.
Keep the caller’s context.
Australian Carers Guide needed its sales history in a system the team could use for follow-up. Noah mapped spreadsheet information to linked people, companies, deals and activities, retaining caller notes and handling inconsistent source values.
- Client
- Australian Carers Guide (AC Guide)
- Contribution
- First-person mapping, import and enablement
- Project status
- Sales-data migration and follow-up
Tools & working context
Project scope and implementation.
- Pipedrive
- spreadsheets
- data mapping
- migration
- bulk filters
- CRM enablement
01 / Business context
The problem
to solve.
A legacy spreadsheet can mix contact details, company information, status shorthand and notes in the same working view. Importing those columns without interpreting their meaning risks producing a CRM that contains the data but is difficult to use.
Noah worked through the destination record types and custom fields, then reviewed the imported information with attention to the next person making a call.
Inside the workflow
A closer look
at the handoffs.
Start with the main path and its branches. Select a step for context, or switch to the technical map for implementation detail.
- Legacy spreadsheet records
Mixed person, company, deal and follow-up information comes from the source sheet. - Interpret fields before import
Preserve mixed values and map each column to its intended destination. - People and contact fields
Map names, phone, email and person-related details into contact context. - Organization and address fields
Retain business context and inspect destination address behavior. - Deal and source-status fields
Create relevant deals while preserving ambiguous source status for clarification. - Activities and follow-up notes
Keep useful caller notes and scheduled activity context available. - Inspect imported working context
Check addresses and copy useful notes into the relevant deal and activity. - Clarify uncertain meanings
Ask about unclear statuses and whether declined leads should be excluded. - Filter and label hot leads
Use bulk filters and labels to prioritize follow-up once the meanings are clear.
Read the workflow notes
- 01 / Interpret
Match columns to CRM records
Person, organization, deal and activity information received separate mappings. Required record names were supplied, and mixed phone/text values were preserved rather than forced into an unsuitable numeric field.
- 02 / Import
Check the resulting working records
The walkthrough narrates the import and checks addresses and follow-up activities. Notes were copied to the places where the caller needed the context.
- 03 / Prioritize
Make the follow-up queue usable
Bulk filters and labels identified hot leads. Ambiguous source statuses, pipeline placement and remaining field cleanup were brought back for client clarification.
The import does not prove a complete data-quality audit, final pipeline configuration or resolved historical values.
03 / Implementation detail
How it
was built.
Preserving a source value did not mean deciding what it meant for sales follow-up. An unclear “no” or mixed company history needed client input before it could become a lost-deal decision.
Duplicating a useful note into the relevant CRM context was a usability decision: a person preparing a call should not have to reconstruct the import to find it.
The source contained roughly three hundred rows; that was not a verified count of clean, unique leads.
04 / Outcome & scope
Result
and scope.
Noah mapped the spreadsheet into customer, company, deal and activity records, then checked the imported information and prepared it for follow-up.
Final stage decisions and redundant-field cleanup remained open. No sales-conversion or revenue improvement is attributed to the migration.