How we move enterprise sales teams to Lightfield

We've moved teams off Salesforce, HubSpot, and other systems of record hundreds of times, and on average an enterprise migration takes 28 days from kickoff to launch.
Along the way, we've distilled our approach into a playbook. It runs over four weeks: design, migrate, build, and launch. The data model is locked by Day 7. Data is migrated and reconciled by Day 14, with a pilot group working in Lightfield. The full team is live by Day 30, when we review results against success criteria agreed before kickoff.
Most CRM migrations take quarters, but we move fast for three key reasons. First, our migration agent reads your export, proposes a data model, and handles the import and reconciliation, so mapping work that used to take weeks takes days. Second, Lightfield's data model can represent how your business actually works, from custom objects to account hierarchies. And third, our Deployment Strategists and forward-deployed engineers have run this playbook hundreds of times, so they know where migrations stall before kickoff.
Here's the playbook, from the first plan through your data, setup, and integrations to what happens after Day 30.
The 30-day plan
The plan follows four guiding principles:
- Cutover is planned backward from the date your current CRM contract ends. When time is short, we migrate the data first and finish configuration after the switch.
- Every input has an owner and a date. Waiting on people for exports, API access, and decisions is usually the bottleneck. We agree each input, its owner, and its date at kickoff.
- Workstreams run in parallel. The data model, data migration, configuration, and integrations move forward at the same time.
- We onboard in waves starting week 2. A pilot group of users goes first starting week 2, and their feedback shapes the setup before the rest of the team joins.
Most of what we need from you comes in the first two phases: exports, data model decisions, user groups, and access. After that, your team mainly uses Lightfield and gives us feedback.
| When | What we do | What you do | Outcome |
|---|---|---|---|
Before signature | Map your current CRM, integrations, reports, and team structure. Draft the 30-day plan with success criteria. | Walk us through how your teams work. Share a sample export. Name a day-to-day owner. | A written plan and agreed success criteria. |
Day 0: kickoff | Agree the plan, the tools in scope, and owners on both sides. Get your admin logged in. Book the weekly working session. | Name workstream owners and pilot users. Confirm when your current CRM contract ends. | Workspace, shared tracker, and shared Slack channel set up. |
Days 1–7: Design | Set up admins, SSO, user groups, and roles. Design the data model with you and lock it by Day 7. Connect mail and calendar for the first users. Validate the export and record counts. Map every integration and report. | Send the full export. Review the data model, stages, and fields. Confirm user groups, the first wave, and the cutover date. Share SSO details. | Admin and access set up; data model locked. |
Days 8–14: Migrate | Import objects, relationships, owners, files, and notes, and reconcile each to the source. Configure pipelines, fields, and reports. Load your knowledge base. Train the pilot group. | Approve dedupe recommendations. Send playbooks, ICP, pricing, and messaging. Spot-check sample accounts. | Data migrated and reconciled; pilot group working in Lightfield. |
Days 15–21: Build | Build, test, and refine agents and automations with your team on live deals. Finish dashboards and integrations. Adjust based on pilot feedback. | Review agent, automation, and report drafts against how the business runs today. | Agents and automations tested; reports match your existing ones. |
Days 22–30: Launch | Train the remaining teams in waves. Freeze the old CRM, import what changed since the first export, run a final check, and repoint forms and integrations. | Attend training. Run a full export from the old CRM as an archive. Approve cutover. | Full team working in Lightfield; old CRM read-only. |
Day 30: review | Review results against each success criterion and agree the next 60 days. | Confirm results and priorities. | Deployment signed off; your Customer Success Manager takes over |
Larger organizations can move one team at a time, with the first team live within 30 days.
Data migration
Even CRMs with hundreds of thousands of records and years of files move in days. Here's how we make sure nothing is lost:
- Before import. We log record counts for every object and validate the export against them.
- During import. Accounts, contacts, and opportunities come over with their source IDs and relationships intact. Owners are mapped explicitly, including people who have left.
- After import. We reconcile every object and relationship back to the source. You sign off on a sample before we go further.
- Files and notes. Files, attachments, and notes are transferred within Salesforce's or HubSpot's API limits.
- Activity history. New email, meetings, and calls are captured automatically from Day 1. Logged history is imported as far back as you choose.
- Archive. You run a full export from your old CRM as an archive. Anything not brought over stays there.
You don't need to clean your data first. Send it as is. We flag duplicates, empty fields, and fields nobody uses, and you approve what happens to each before anything is imported. You also choose how much history comes over, object by object.
At cutover, we freeze the old CRM, import anything that changed since the first export, and run a final check. The old CRM stays read-only until you switch it off. If you have concerns with a full cutover, we support bidirectional syncs to run both CRMs in parallel.
Workspace configuration
Migrating a CRM also means migrating how your team works: the automations, rules, permissions, and pipelines built up over years. Most CRMs have years of workarounds, so we don't want to copy the old setup as is.
We decide with you what to keep, where it goes, and what we build newly in Lightfield.
| In Salesforce or HubSpot | In Lightfield | How we move it |
|---|---|---|
Custom objects | Custom objects and relationships | Rebuilt on the data model locked in week 1; carried over or archived by agreement |
Parent accounts / parent-child companies | Account hierarchies | Rebuilt across parents, subsidiaries, and divisions, with revenue at the right level |
Record types, sales processes, multiple deal pipelines | Multiple pipelines with stage requirements | Each legacy stage mapped; the original value kept in its own field if needed, so historical reports still work |
Profiles, roles, permission sets, sharing rules / teams and permissions | Roles and groups per object and per record | Mapped to how each team needs access today |
Validation rules, required fields, formula and roll-up fields | Validation rules, stage requirements, formula fields | Rebuilt where they are still used |
Flows, workflow rules, process automation / HubSpot workflows | Workflows (triggers, webhooks, APIs) and agents | Rebuilt for what they do, and some become agents |
Reports and dashboards | Dashboards with drill-down to the underlying records | Rebuilt and reconciled against your numbers |
Sequences and cadences | Email and LinkedIn sequences with human review | Rebuilt from your messaging; new sending domains need 3–4 weeks to warm |
Access is set up in week 1: SAML or OIDC SSO required by domain, SCIM provisioning, and enforced MFA. Agents, automations, and API keys follow the same permission rules as people. Admins can make emails and meetings private by default.
The design of your CRM keeps evolving
A migration is the best chance to drop the workarounds your old CRM forced on you: objects that duplicate each other, fields nobody fills in, stages that exist only to trigger a flow. Redesign starts in week 1 with the data model. It continues as the pilot group works on live deals, and their feedback reshapes stages, automations, and agents before the rest of the team joins. It doesn’t stop at Day 30. As more teams come on and usage shows what works, we keep refining with you.
We can work this way because changing Lightfield is easy. Our team uses Lightfield’s agent to learn the structure of your data, modify the data model, update records in bulk, backfill fields from past calls, emails, and notes, and dedupe and merge records. In older CRMs, that work takes an admin weeks. It’s the same agent your RevOps team uses after launch, so the CRM keeps improving after we hand it over.
Integrations are brought over, and new ones are built
In week 1, we list everything that reads from or writes to your CRM: communication channels, website forms, marketing email, billing, ERP, and data warehouse. Each one gets a replacement path before cutover. Your IT and RevOps teams work with our Deployment Strategists and FDEs directly.
- Native connectors, webhooks, and API integrations cover most use cases.
- Custom builds are done by a forward-deployed engineer (FDE) from Lightfield. Average build time is less than two weeks.
- Lightfield's REST API and MCP server cover the rest.
If you already use notetakers, call recorders, or enrichment tools, Lightfield captures calls and meetings natively and can ingest your existing transcript history. You decide at cutover which tools to retire and which to connect.
Our team leads the migration, working closely with yours
Each migration has one accountable owner on each side. Others join for the workstreams they own.
| Role | Side | Responsible for |
|---|---|---|
Deployment Strategist | Lightfield | Leads the end-to-end deployment, including data modeling, migration, configuration, agent and workflow setup, training, and the Day 30 review. Serves as your primary point of contact throughout deployment. |
Forward-deployed engineer | Lightfield | Leads technical implementation, including custom integrations, complex migrations, APIs, and advanced automations. Partners with the Deployment Strategist to deliver solutions tailored to your business needs. |
Customer Success Manager | Lightfield | Engaged from Day 1 to ensure continuity throughout deployment and beyond. Serves as your long-term partner after launch, supporting user adoption, ongoing optimization, issue resolution, and expansion into new use cases. |
Executive sponsor | Customer | Sets priorities, resolves trade-offs, attends kickoff and the Day 30 review |
Day-to-day owner | Customer | Usually the RevOps or sales operations lead. Approves each workstream and gathers inputs. |
Systems contact | Customer | Grants admin and API access, runs exports, sets up SSO |
Workstream owners | Customer | Sales, marketing, or CS leads who define what their team needs |
Pilot users | Customer | A small group who use Lightfield first and give feedback on the build |
The day-to-day owner's busiest week is the first one: the export, the data model, and the stage decisions. After that, all we seek from them is a weekly working session. Other users attend one live training for their wave and connect mail and calendar during it. Your teams keep working throughout and don't re-enter data.
How we keep momentum high on the migration
- Success criteria, owners, and dates are confirmed at kickoff.
- A shared tracker lists every task with a definition of done, an owner, and dependencies. Both teams update it before each session.
- The weekly working session covers open decisions and blockers only. We send a written summary of decisions, owners, and dates afterward.
- A shared Slack channel covers everything between sessions. We reply the same working day.
- When a milestone is at risk, we flag it right away with the issue, the interim process, the owner, and a revised date.
Agents and automations
During scoping, we agree which recurring work to automate first, based on where your team spends the most manual time. Those agents and automations run on live deals by Day 30. During the Migrate phase, we load your ICP, personas, pricing, playbook, battlecards, and messaging so agents and drafts follow your rules.
Signal agent | Watches ICP accounts for hiring, funding, leadership changes, site visits, and product usage, and routes each signal to the account owner |
Prospecting agent | Builds and enriches target account and contact lists against your ICP and personas |
Outbound agent | Writes email and LinkedIn sequences from account context and sends drafts to a named reviewer before anything goes out |
Sales agent | Prepares reps before meetings, drafts follow-ups, and fills qualification and stage fields from calls and emails |
RevOps agent | Flags stalled and at-risk deals, keeps records clean, checks the forecast against call and email evidence, and sends leadership a weekly summary |
Enablement agent | Scores calls against your rubric and briefs new reps on the deals they inherit |
Customer success agent | Hands won deals to the account team with an implementation plan and flags renewal and health signals |
Every agent follows the same permissions as the person it acts for. Customer-facing drafts go to a named reviewer before they're sent. AI-filled fields can be set to suggest first, and every number links back to the call or email behind it.
After Day 30
At the Day 30 review, we'll align on priorities for the next 60 days and beyond. Your Customer Success Manager, engaged from Day 1, will continue partnering with our deployment team to support ongoing adoption, optimization, and expansion. This typically includes:
- Additional agents and automations identified during scoping or the review
- Workflow refinements and enhancements based on initial usage
- Rollout to additional teams, such as customer success, marketing, or finance
- Outbound activation once new sending domains are warmed up
- Ongoing reviews of usage, adoption, and success criteria
From Day 1, every call, email, and meeting your team has adds to Lightfield's world model of your business.

