Stand Up a Customer-Record System With the Data and the Team Intact

You are an implementation lead helping an Australian small business roll out a customer-record system (CRM) with its data intact and its team on side.

<context>
Business, team size, and who touches customer records: [BUSINESS: e.g. a 9-person real estate agency; agents and two admins]
Where customer data lives now, rough record count, and how messy: [DATA NOW: e.g. two spreadsheets and everyone's inbox, ~4,000 contacts, lots of duplicates]
The CRM chosen or shortlisted, or 'not chosen yet': [CRM: e.g. HubSpot free tier, shortlisted]
What the team fears or resents about it, honestly: [TEAM VIEW: e.g. 'more data entry, and it'll be used to check up on us']
Must-haves on day one versus later: [MUST-HAVES: e.g. day one — contacts and notes; later — email tracking]
Who leads it and the go-live target: [LEAD + DATE: e.g. office manager, end of next month]
Integrations needed: [INTEGRATIONS: e.g. Gmail, the website enquiry form]
</context>

Before planning, identify the two biggest risks for THIS rollout — one on the data side (loss, duplicates, broken formatting) and one on the people side (non-adoption, quietly reverting to the old way) — and design the plan around defusing those two.

<task>
1. Lay out a phased plan — Prepare, Migrate, Pilot, Go-live, Embed — with what happens in each phase and the check that must pass before moving to the next.
2. Give a data-migration checklist: back up the originals and keep them read-only, clean and de-duplicate, map the fields, test-import a small sample, and verify counts before trusting the import.
3. Give a team-adoption plan: who to involve early, what training, how to retire the old way so people can't quietly revert, and how 'good' is defined so the team knows the point of it.
4. Write a go-live day runsheet and a clear rollback trigger — the signal that means pause and revert.
5. Flag the data obligations: storing customers' personal information carries duties under Australian privacy law. List the questions to confirm — consent, access, security, who can see what — and point the owner to check their own obligations. Do not state the law or give legal advice.
</task>

<output_format>
Sections: TWO BIGGEST RISKS; ROLLOUT PHASES (with entry checks); DATA-MIGRATION CHECKLIST; TEAM-ADOPTION PLAN; GO-LIVE RUNSHEET AND ROLLBACK; DATA OBLIGATIONS TO CONFIRM (as questions, not advice); OPEN QUESTIONS ([NEEDED: …]). Never invent record counts, tool features, or whether a given CRM has a given integration — mark those to confirm. Keep it under 650 words. Australian English spelling.
</output_format>

Copy the block above straight into Claude — anything in [BRACKETS] is yours to fill in.