The objection was the move
In my February 2021 ConvertKit case, I described Nathan Barry moving from a public building challenge to a more focused sales effort. He narrowed the audience to professional bloggers and offered to migrate customers from their existing email provider for free.
The objection was practical: moving an email operation takes work. Concierge migration put some of that work on the seller. My original account separated early acquisition through the public challenge, later direct sales and word of mouth, and an affiliate program that fit an audience of bloggers. Those are historical stages, not a channel attribution experiment.
Map the work between yes and value
I would start by asking a prospect to walk through everything they believe switching requires. Keep asking until the list gets boring. Exporting contacts might be obvious. Rebuilding forms, checking automations, changing links, briefing a colleague, or deciding what happens to the old account might be the real project.
Then split that list into three columns: work the customer must own, work you can do with their permission, and work the product can eventually remove. That becomes a better onboarding plan than another feature comparison.
The permission boundary matters. The customer should know what will move, what will stay, how the result will be checked, and who approves the final change. Helpful onboarding should reduce uncertainty as well as effort.
Price the assistance honestly
Free migration is still a cost to the business. I would record hands-on time, rework, elapsed time to the first useful result, and what the customer continues doing afterward. That shows whether assistance is removing a temporary learning obstacle or becoming an ongoing service obligation.
The answer can differ by segment. A larger customer with a complicated setup may justify more help. A small account might need a clearer import flow. Treating both as the same average can hide the decision.
Keep the learning when you automate
The early manual process is valuable because it exposes the real sequence of work. Preserve the common questions, failed assumptions, and checks that caught mistakes. They are candidates for product improvements and documentation.
I would automate the stable parts first. A checkbox that says “migration complete” is not enough: the customer should be able to verify that the important workflow still works. That verification is part of delivering the sale.
What I would keep
- List the actual work required to switch.
- Offer assistance around a specific obstacle.
- Define permissions and the customer’s acceptance check.
- Measure the cost of assistance alongside subsequent customer use.
The takeaway
A better product still has to be worth moving to. Sometimes the strongest sales improvement is doing part of the move.
Sources and original research
Adapted from my February 8, 2021 case study. Historical company claims come from that issue; the review questions are editorial guidance. This is not a current product audit or a measured causal growth result.
Updated September 20, 2026. Based on original First 1000 reporting and the sources listed above.