Field Pulse is a smaller-but-loved field-service platform. Conduit pulls 6 data types: customers, jobs, invoices, estimates, pricebook items, and team. Authentication is via API key, copied from your Field Pulse account settings.
This guide walks the full migration: getting your API key, connecting, what transfers, gotchas, and what to verify after.
01Get your Field Pulse API key
The API key lives in Field Pulse’s settings.
- Open Field Pulse in a separate browser tab from Conduit.
- Navigate to Settings → Integrations (or Settings → API, depending on your version).
- Generate a new API key if one doesn’t exist. Copy it.
SCREENSHOT · migration/field-pulse/01-api-key.png
02Connect to Conduit
- Switch back to Conduit. Open Settings → Import Data → Import from Another Tool.
- Click the FieldPulse tile.
- Paste your API key in the form.
- Click Connect. The wizard validates the key and advances to Pull Data.
SCREENSHOT · migration/field-pulse/02-connect.png
If validation fails, double-check that you copied the full key (no leading or trailing whitespace) and that it’s an active key in Field Pulse.
03What transfers
Conduit pulls 6 data types from Field Pulse:
- Customers. Names, emails, phones, addresses, tags, notes.
- Jobs. Title, scheduled date and time, technician assignment, status, line items.
- Invoices. Line items, totals, payment status, customer link, dates.
- Estimates. Imported as Conduit bids.
- Pricebook items. Name, description, unit, price, cost (when exposed by the Field Pulse API).
- Team. Technician names and emails. Team members still need to accept Conduit invites individually; only the email and name pre-populate.
Each record gets a field_pulse_external_id.
04What doesn’t transfer
- Photos. Job and customer photos don’t bulk-import.
- Custom fields. Per-account custom fields don’t map to Conduit’s models. Capture in notes or tags if the data is critical.
- Time entries. Time tracking starts fresh in Conduit.
- Equipment / asset records. Field Pulse’s equipment tracking doesn’t have a 1:1 Conduit equivalent.
- Communication logs (calls, texts, emails through Field Pulse). History stays in Field Pulse; future communications start in Conduit.
05After import
- Spot-check 5-10 customers. Confirm contact info and address are correct.
- Verify invoice totals for one or two larger customers.
- Connect Stripe in Settings → Payments.
- Send team invites. The team list pre-populated emails; each technician still needs to accept and set a password.
- Re-attach important photos manually.
Field Pulse runs alongside Conduit untouched. Verify everything before deactivating the Field Pulse subscription.