FieldPulse is often chosen by small service teams because it is approachable. Teams usually start looking for a FieldPulse alternative when they want a cleaner path for job management, bids, invoices, payments, and growth without re-entering the same customer list from scratch.
Conduit supports a FieldPulse import using an API key. You connect the source account, pull the supported records, then verify the pieces that affect live work before turning FieldPulse off.
See /vs/field-pulse for the comparison page and /payments for how Conduit handles payment links and ACH.
Get the FieldPulse API Key
Open FieldPulse in a separate tab and go to the account settings area. Depending on your version, the API key may be under Settings -> Integrations or Settings -> API.
- Generate a new API key if one does not already exist.
- Copy the full key.
- Keep the FieldPulse settings tab open until Conduit confirms the key works.
If Conduit rejects the key, check that it is active and that no leading or trailing spaces were copied.
Connect FieldPulse to Conduit
In Conduit, open Settings -> Import Data -> Import from Another Tool and select FieldPulse.
- Paste the API key into the connection form.
- Click Connect.
- Let Conduit validate the key.
- Continue to the data pull once validation succeeds.
The source account is not modified during the import, so you can keep FieldPulse available while you inspect Conduit.
What Conduit Imports
Conduit pulls the FieldPulse records needed for customer management, scheduling, estimates, billing, and pricebook setup:
- Customers: names, email addresses, phone numbers, addresses, tags, and notes.
- Jobs: title, scheduled date and time, status, and line items.
- Invoices: line items, totals, payment status, linked customer, and dates.
- Estimates: imported as Conduit bids.
- Pricebook items: name, description, unit, price, and cost when the FieldPulse API exposes it.
Source IDs are stored in source_external_id so Conduit can avoid recreating the same customer records on a later import.
What Requires Manual Follow-Up
FieldPulse records are not all portable. Plan a short cleanup pass for:
- Photos: job and customer photos should be re-attached manually when important.
- Custom fields: move critical custom-field values into notes or tags.
- Time entries: Conduit time tracking starts after launch.
- Equipment or asset records: FieldPulse equipment tracking does not have a direct import target.
- Communication history: old calls, texts, and emails remain in FieldPulse.
- Team members: invite technicians manually in Conduit.
Launch Checklist
Before the team starts using Conduit for live work:
- Spot-check 5 to 10 customers for addresses and contact info.
- Verify invoice totals for one or two larger customers.
- Connect Stripe in Settings -> Payments.
- Invite technicians and confirm they can log in.
- Re-attach the photos or documents the field team actually needs.
Cost Comparison
Figures below come only from AboutPage.jsx and should be verified before publishing this draft.
| Platform | Listed monthly price | Listed detail | Listed 5-person team cost |
|---|---|---|---|
| FieldPulse | $99-199/mo | $40/extra user. Limited integrations on lower tiers. | $259-359/mo |
| Conduit | $35-250/mo | Every feature included. No per-user fees. No setup costs. No contracts. | $65/mo |
Switch in Minutes, Not Weeks
The API import is the fastest route when FieldPulse has the records you trust. Conduit also supports CSV uploads and AI-assisted extraction from a photo of a handwritten list. That matters for small teams because the system of record is often split across the app, spreadsheets, whiteboards, and notes from the field.
Conduit’s importer reads those sources, identifies the likely fields, and maps them into customers, jobs, bids, invoices, schedules, and pricebook items. You review the mapped data before relying on it.
Payment Fee Savings
On a $10,000 invoice, card processing is about $290 before Conduit’s 1% platform fee. ACH in Conduit uses a $1 platform fee plus Stripe ACH processing at 0.8% capped at $5, so the same invoice costs $6 by ACH.
For FieldPulse teams trying to lower operating costs while improving payment collection, the payment workflow deserves a look alongside the software plan. See /payments.
Ready to Move Off FieldPulse?
Generate the API key, run the import, verify the records above, and move active work once the team is comfortable in Conduit. Use /vs/field-pulse for the broader side-by-side comparison.