← All work

Ascendant Financial

Before moving the CRM, I had to understand the business.

Ascendant Financial was moving from Keap to GoHighLevel. The contacts were only one part of it. The harder question was what people expected the system to do around them.

My work

CRM migration planning

The chapter

Planning & discovery

Part of my work at Monarchy

The process was in more than one place.

I worked through meeting transcripts, email threads, and existing documents covering Keap, AppointmentCore, DocuSign, and GHL. The aim was to bring the business rules into one place before the team built around them.

Turning conversations into a build plan.

The resulting plan has 19 core sections and six appendices. It maps fields, tags, forms, reporting, dependencies, and acceptance criteria, with sources attached to the decisions.

How I approached the planning

Follow the process before changing the tool.

  1. 01

    Listen

    Meetings, emails, existing documents.

  2. 02

    Map

    Rules, systems, and dependencies.

  3. 03

    Resolve

    Questions that need a business decision.

  4. 04

    Specify

    Requirements and ways to check them.

This story covers discovery and planning for the migration.

Some answers needed another conversation.

When the source material left something unclear, I kept the question open. A detailed document can make an assumption look settled very quickly. I wanted the team to see where a decision still had to be made.