# Prove your builder lead export works before a vendor handoff

A builder lead data handoff needs a tested export, not only account credentials. Keep contact identifiers, source history, permission records, notes, activities and field definitions in readable files. Reconcile a sample against the working CRM before you change access. Leave the original export untouched and document every transformation the receiving system needs.

## What counts as builder lead data?

Lead data starts before a contact reaches the CRM and continues after a project is accepted or declined. It includes the form payload, the landing page, campaign tags, the call route, the event source, referral context, notes, next actions, lot and plan status, outcome reason and approved communication history.

You also need the definitions behind those records. An export that says "Source C" or "Stage Seven" is useless when only an outside operator knows what the labels mean. Field dictionaries, source rules, pipeline entry conditions and report filters are part of a usable [handoff](/process/handoff/).

The [leads and CRM library](/articles/leads-and-crm/) covers how these records support intake, qualification and follow-up. Keep the export and its field definitions in storage you control, with a named administrator.

## Which accounts should you control?

Hold the primary account, the recovery path and administrative authority wherever practical. Outside specialists get named access for defined work. A shared password in a message thread is not an ownership plan.

| System | Ownership evidence | Handoff test |
| --- | --- | --- |
| Website forms | Builder controls the site account, destination and stored submissions | Submit a test and recover the record without vendor help |
| CRM | Builder controls administration, users, fields and exports | Export contacts, activities and field definitions |
| Tracked calls | Builder controls numbers, routing, access and available records | Verify routing and document number transfer options |
| Email sending | Builder controls sender setup, lists, exclusions and permission records | Export audiences and suppression information |
| Event intake | Builder controls forms, scans or imported sign-in records | Trace an event contact into the CRM with source detail |
| Analytics and reports | Builder controls raw access, tags, definitions and reporting views | Rebuild a report from underlying records |

The [Lead attribution stage](/process/lead-attribution/) connects these builder-controlled paths and tests records from first touch through CRM receipt.

## How do you audit ownership before changing vendors?

Start while the existing systems still work and the current operators are still around. Inventory each account, its owner, its administrators, its recovery method and the data it holds. Do not start by removing access. First find out what would stop working if a user, an integration or a payment relationship changed.

1. **List every lead entry point.** Forms, tracked numbers, event tools, profile links, referral forms and manual imports.

2. **Identify the governing account.** Record who owns it, who administers it and which address controls recovery.

3. **Map each connection.** Show where records go, which fields move and what happens when the connection fails.

4. **Export the underlying data.** Confirm that contacts, activities, source fields, notes and status history are readable.

5. **Preserve definitions.** Save field meanings, stage rules, campaign naming and report filters with the export.

6. **Test a live path.** Send a controlled inquiry through each important route and trace it to the final record.

7. **Write the handoff order.** Document how access, routing and integrations can change without losing new inquiries.

Check ownership, export, transfer and retention terms with each provider before you change an account. Do not assume a tracked number, a call record, an automation or a custom field can move because it shows on a dashboard.

## What makes a lead export usable?

A usable export keeps meaning. It includes stable identifiers, original source, later touches, contact type, permission status, current stage, outcome, owner, next action and relevant activity history. Dates and field formats stay consistent enough to read outside the original interface.

Sample the file. Open several records from different sources: a website form, a call, a Parade contact, a referral. Compare them with the working system. Confirm that notes did not collapse into one unreadable cell and that multi-contact records still make sense.

The field plan in [builder CRM fields](/articles/leads-and-crm/builder-crm-fields/) defines what has to survive. The [builder CRM guide](/guides/builder-crm/) covers permissions, pipeline setup, integrations and exit-path testing.

Use an acceptance sheet for the sample: source record identifier, exported identifier, activity count, last next action, permission value and any missing attachment. Reconcile differences before you accept the transfer. Test field meanings as well as totals. A renamed stage is not equivalent if its entry rule changed.

### What should stay out of a general export?

Limit exports to the documented purpose and the approved recipients. Sensitive documents, private project files, recordings and unnecessary personal details may need different controls. Review your privacy commitments, current tool settings and applicable requirements before you copy data into a new location.

### How should forms, calls and events keep source history?

Keep original source separate from later activity. A buyer first visits a community page, calls through a tracked route and later tours a Parade house. Overwriting the first source with the latest touch destroys the history. Add the event as another touch and keep the known path.

Call ownership deserves extra attention, because the number itself sits on signs, print pieces and saved contacts. The [phone lead tracking guide](/articles/leads-and-crm/tracking-phone-leads/) covers routing and record design for [call tracking](/glossary/call-tracking/). During a handoff, verify each public number, its destination and its continuity before you change any account relationship.

For event imports, keep the event name, the intake method, the permission status and the duplicate-matching decision. Do not create a new person every time the same contact signs in. Do not silently merge two different people because they share an address.

### Where can AI agents help during a data handoff?

We run Claude and Codex agents that inventory field names, compare exports, flag missing values, draft a data dictionary and test report logic against approved samples. They also surface likely duplicates for human review. A person controls access, approves every merge and decides which records may move.

No agent infers permission, deletes source records or rewrites historical outcomes to fit a new pipeline. Keep the original export unchanged, record any transformation and make the transformed copy reproducible. Use that transformation record to investigate later stage-total or source-label differences.

## How do you prove the handoff is complete?

Proof comes from operation. Your administrator can sign in, add and remove a user, recover the account, export records and explain the main fields. New forms and calls reach the right place. Existing numbers route correctly. Reports trace back to underlying records. A written runbook names the owner of each recurring task.

Review the first reporting cycle after a transition for missing sources, duplicate contacts, broken assignments and inactive integrations. The [monthly lead source report](/articles/leads-and-crm/monthly-lead-source-report/) is the practical place to expose those gaps. Reproduce the report totals from the accepted export before you close the handoff.

## What do builders ask before a data handoff?

### Does paying for a system mean we own the data?

Paying for a lead system does not establish usable account control. Check ownership and export provisions with your provider, then test administrator access, export scope and recovery.

### Should an outside operator have administrator access?

Give an outside lead-system operator administrator access only when the work needs it. Use named access and document how permissions will be reviewed and removed.

### Is a contact export enough for handoff?

A contact export alone does not complete a builder lead handoff. Keep the activities, source details, definitions, pipeline rules, permissions and integration notes needed to operate the records.

### Can AI agents clean the database automatically?

AI agents can flag lead database duplicates and formatting issues. A person approves merges, deletions, permission changes and historical corrections before anything enters the working system.