FieldproxyIntegration guide · SalesforceSalesforce for the customer. Fieldproxy for the visit. Synced both ways.
Keep Salesforce as your CRM and connect it to a field service system for the work after the sale. In Fieldproxy, accounts and contacts are kept matched on the Salesforce record ID, a Closed Won opportunity (or a stage you choose) becomes a job or project, and a case that needs a site visit becomes a work order linked back to the case. Completion, technician notes and a link to the visit report are written back to the opportunity, the case or a custom object. Your field team works in Fieldproxy's app, so it needs no Salesforce Field Service licences.
Fieldproxy is AI-native field service software set up around each company's workflow: dispatch, the Android and iOS technician app, your own forms and checklists, quotes, invoices, stock and service agreements. Set up for you, live within a day, with unlimited users on one price per company.
See your Salesforce opportunities turn into jobs
Tell us which opportunities and cases need a visit. We set it up on your own objects before you commit.
Why teams connect them
Salesforce closes the deal. The handoff to the field is an email.
Salesforce holds accounts, opportunities, cases and the sales team's forecast. What happens after Closed Won, getting a crew to site with the right scope, parts and paperwork, usually lives somewhere else: a spreadsheet, a scheduling app, a shared inbox. The scope is retyped, the site contact is lost, and nobody in sales can see whether the install actually happened.
Salesforce's own answer is Salesforce Field Service, with its own licences and its own implementation project. For many service teams that is more than they need, and contractors and seasonal crews need seats too. The alternative is a field service system that replaces your field tools and connects to Salesforce both ways.
What syncs
Salesforce objects and where they land
A typical setup. Standard and custom fields are mapped one by one when we set you up, and each field gets one owner so the two systems never overwrite each other.
| Object | Direction | When it moves |
|---|---|---|
| Accounts and contacts | Both ways | Kept matched on the Salesforce record ID, so sales and service share one customer. New customers created in the field come back to Salesforce. |
| Opportunities | Salesforce → Fieldproxy | A Closed Won opportunity, or a stage you choose, creates a job or project in Fieldproxy with the account, contact, site and scope. |
| Cases | Salesforce → Fieldproxy | A case that needs a site visit creates a work order, linked back to the case by its ID. |
| Job outcome | Fieldproxy → Salesforce | Completion, notes and report links are written to the opportunity, the case or a custom object as the job progresses. |
| Quotes raised in the field | Set up per account | A quote raised on site can update or create an opportunity. How it maps is set up per account. |
| Assets and custom objects | Set up per account | Salesforce assets can link to Fieldproxy equipment records, and custom objects can be mapped. Set up per account. |
Your Salesforce admin approves a connected app (OAuth) and the objects it may read and write. Syncs are batched to stay inside your org's daily API limits.
See your own opportunity stages mapped to jobs before you commit.
Get DemoThe workflow
From Closed Won to completed job and invoice
For installs, projects and new maintenance contracts. The trigger is yours to choose.
- 1
The opportunity is won
Salesperson, in Salesforce
The opportunity moves to Closed Won, or whichever stage you set. Products and the site address are already on it. - 2
A job or project is created
Fieldproxy
Account, contact, site and scope come across. Small work becomes a job; multi-visit work becomes a project with stages, each with its own checklist. - 3
It is scheduled
Office, with the Dispatch agent
The Dispatch agent suggests who should go by skills, location, free time and van stock. The office confirms before anything is sent, and changes can be undone. - 4
The work is done on the phone
Technician or subcontractor
GPS check-in, your checklist with required photos, parts used from van stock, extra work quoted on site with good, better and best options, and the customer's signature. Works offline. - 5
Salesforce sees the outcome
Fieldproxy to Salesforce
Completion, the technician's notes and a link to the visit report are written back, so the account owner knows the install is done without asking. - 6
Billing goes to finance
Fieldproxy to accounting
The invoice is built from the job and syncs to QuickBooks, Xero, Sage or NetSuite, with a payment link or Tap to Pay for the customer.
Service cases
Cases that need someone on site
For breakdowns, warranty visits and complaints raised in Salesforce Service Cloud.
- 1
The case needs a visit
An agent sets the status or a flag, or a rule picks it up by record type. Cases resolved remotely stay in Salesforce. - 2
A work order is created
Account, contact, site, description and the case ID come across. The job keeps the case ID, so every update finds the right case. - 3
Dispatched by priority
The case priority sets the order. The Watcher agent flags work about to miss its target, so a breach shows before the customer chases. - 4
Updates go back to the case
Assigned, on site, findings, the visit report and completion are written back, so the case owner can close it with the customer. - 5
Follow-up work becomes an opportunity
If the technician finds more work, a quote is raised from the job, and it can create or update an opportunity in Salesforce.
What stays where
What stays in Salesforce, and what moves to Fieldproxy
Salesforce owns the customer relationship and the pipeline; Fieldproxy owns the work. The field tools you use today are replaced, not layered on top, and you do not add Salesforce Field Service to do it.
Stays in Salesforce
- Accounts, contacts, leads and the sales pipeline
- Forecasting and sales reporting
- Service Cloud cases and the customer conversation
- Marketing and anything built on your org today
Moves to Fieldproxy
- Scheduling and dispatch, including subcontractors and contractor crews
- The technician app: checklists, photos, signatures, offline, GPS check-in
- Site surveys, inspections and your own forms
- Quotes changed on site, invoices, payment links and Tap to Pay
- Service agreements and planned maintenance
- Sites, assets with QR codes, warehouse and van stock, purchase orders
- Not-to-exceed amounts on work for your commercial clients
Worked example
A rooftop unit install, from opportunity to invoice
A commercial HVAC contractor runs sales in Salesforce and its books in QuickBooks Online.
Demo data. The company, people and numbers are made up.
- Opportunity: Account manager Leah Okafor closes an opportunity to replace two rooftop units at Brookfield Medical Centre (a fictional client). It moves to Closed Won.
- Project: Fieldproxy creates a project with three stages (removal, install, commissioning), each with its own checklist, under the existing customer and site.
- Schedule: The Dispatch agent suggests a two-person crew with the right certifications for the install week; dispatcher Sam Reyes confirms.
- On site: The crew checks in by GPS, photographs the old units, records model and serial numbers on the new assets and prints QR labels for them.
- Extra work: A damaged curb is found. The lead raises a good/better/best quote on the phone; the facilities manager approves the middle option in the customer portal, within the not-to-exceed amount on the job.
- Back in Salesforce: The opportunity shows the project complete with a link to the commissioning report. The approved extra quote creates a follow-up opportunity for Leah.
- Money: The invoice syncs to QuickBooks Online and the paid status shows in Salesforce.
The account manager never asked "did the install happen?" and nobody retyped the scope into a second system.
See it built around how your team already works.
Get DemoSetup
Connected and live within a day
Your Salesforce admin is needed for the connected app and a review of the mapping. The rest is done by Fieldproxy's team.
- 1
A 30-minute call
Which opportunity stages and case types start field work, which fields matter, and what Salesforce should see afterwards. - 2
Connect Salesforce
Your admin approves the connected app and the objects it may read and write. We map standard and custom fields and agree which system owns each one. - 3
Build the field side
Job types, projects, forms and checklists, price list, quote and invoice templates, stock and your accounting sync. Sites and assets come across with free, assisted migration. - 4
Test on real records
Win a test opportunity, raise a test case, complete the jobs on the phone and check what lands in Salesforce. - 5
Go live
Switch off the old field tools on the date you set. Your team keeps working in Salesforce; the field team works in Fieldproxy.
Fit
Who it's for, and when it isn't the right fit
A good fit if
- Salesforce is your CRM and you want it to stay that way
- Won work or cases need a visit, with forms, photos, quotes and invoices on site
- Subcontractors or seasonal crews do part of the work and should not need Salesforce seats
- You want field work live in days, not a multi-month Field Service implementation
- Finance runs QuickBooks, Xero, Sage or NetSuite rather than Salesforce billing
Probably not the right fit if
- You have already built your field operation on Salesforce Field Service and it works
- Company policy is that every process must live inside one Salesforce org
- You only need a shared calendar for a handful of visits a month
- You are looking for an add-on that sits on top of your current field app: Fieldproxy replaces it
The usual ways to run field work with Salesforce, by kind of tool.
| Approach | Fits when | What you give up |
|---|---|---|
| Salesforce alone: tasks, events and cases for visits | Few visits, no on-site paperwork | No technician app, no checklists or photos on the job, no field invoicing, no stock. |
| Salesforce Field Service | You want everything inside one Salesforce org and have budget for the licences and implementation | Licences per user, including crews, and a longer project to configure. |
| A field service system that replaces your field tools, synced both ways (Fieldproxy) | You want Salesforce to stay the CRM and the field side running quickly | A second system for the field team. Plan the switch-off date for the old tools. |
Straight answers
Salesforce and field service: questions we get asked
Does Fieldproxy integrate with Salesforce?
Do I need Salesforce Field Service licences?
Which opportunity stage creates the job?
Can Salesforce cases become work orders?
What gets written back to Salesforce?
Do Salesforce assets and custom objects sync?
Will it use up our Salesforce API limits?
Where do invoices go?
Can I create jobs from Claude or ChatGPT instead of Salesforce?
How long does it take to set up?
Related
Where to go from here
Fieldproxy MCP server
Book jobs, quote and invoice from Claude, ChatGPT or Copilot, with a confirm step.
Keep Salesforce. Give the field work its own system.
Tell us which opportunities and cases need a visit. We show it running on your own objects and job types.
Get DemoLive within a day. Free, assisted migration. Unlimited users on one price per company.