What was needed
A visible operating system and a safe path away from Airtable dependencies for a 12-person team.
Back to portfolio
Technical project management · Migration
Internal CRM migration
I led the move from an Airtable-shaped operating model to a custom internal CRM and dashboard for a 12-person team.
Process mapping · data-model decisions · migration planning · validation · rollout · handoff.
12-personteam supported
46automations documented
16 / 16selected scenarios rebuilt
Dailyadoption after rollout
What I did
Mapped workflows, made schema decisions, planned coexistence, validated scenarios, and documented the handoff.
What was achieved
46 automations documented; 16 of 16 selected scenarios rebuilt; the CRM was adopted in daily use.
Project documentation
Review the project evidence.
Each artifact opens as a responsive HTML document with the project decisions, controls, and outcomes. No external repository or download is required.
Project brief
Problem, scope, constraints, and success measures.
Read documentDelivery plan
Workflow mapping, target schema, coexistence, and rollout.
Read documentRisk and decision register
Controls for data quality, adoption, and handoff.
Read documentStatus report
Progress, scenarios validated, issues, and ownership.
Read documentClose-out and lessons
Results, adoption, boundaries, and recommendations.
Read documentSanitized for public review
Client names, private records, internal URLs, production IDs, and sensitive business rules have been removed or generalized. The public case preserves the delivery thinking, controls, and measurable outcomes.