Before starting the trial
- Confirm the actual trial expiry, automatic billing date, selected plan, and usage charges at checkout.
- Inventory required fields, lead sources, calendars, phone numbers, integrations, and retained systems.
- Record the present workflow’s routing, booking, messaging, and data-quality requirements.
- Agree on acceptable setup hours, recurring costs, and rollback steps.
Build and test with controlled records
| Check | Pass condition |
|---|---|
| Lead capture | Required fields and source arrive accurately; duplicate handling behaves as intended. |
| Routing | The correct owner and pipeline stage receive each test lead. |
| Booking | Availability, time zones, confirmations, and cancellations match the requirement. |
| Messaging | Only one system sends outbound messages; consent and unsubscribe states are respected. |
| Costs | Observed billing categories reconcile to the usage budget. |
| Rollback | The owner can return routing to the original system and reconcile test records. |
Move a small, controlled share of traffic
Keep the old configuration available, but do not activate duplicate outbound workflows. Monitor errors and costs, compare against the agreed baseline, and retain specialist systems until their dependencies are verified. Do not promise a seamless migration before this evidence exists.
Decide before billing begins
Set your decision date from the actual account expiry, leaving time to cancel or adjust. Continue only if the workflow passes, the cost estimate holds, and someone accepts responsibility for operating it. Otherwise reduce scope or cancel according to the account’s terms.
This is an independent planning checklist, not a claim that we have implemented or tested your workflow. HighLevel provides its product documentation and support; this site does not provide migration services.