Two accounts for one customer
How you'll know: A "Drake Corp" created by the web shop and another created by a rep, each with half the history.
Fix: Match on a stable ID held in an external ID field on both sides, never on the company name.
Most Salesforce integration projects stall on a question nobody asked at the start: should the other system's data be copied into Salesforce, or only shown there? Settle that, then choose between an AppExchange app, an integration platform, or a build against Salesforce's own APIs.
Reps export reports to Excel to line them up against invoices, inventory and shipping data that lives in other systems.
Stuck on Salesforce? Let's solve it →An AppExchange app from the other vendor. Quickest when one exists and its field mapping matches the way you work. Look there first.
An integration platform such as Zapier, Make or MuleSoft. Fine for event handoffs between a few systems, as long as the logic stays simple or someone owns it.
A custom integration against the REST, Bulk and event APIs. Right when the rules are yours: who gets the lead, when an order may sync, what counts as the same customer.
Good builds usually do both. Copy the handful of fields automation needs, such as payment status or last order date, and show the rest live. Copying last order date and contract end date is also what lets Salesforce flag a customer who has stopped ordering, or a renewal coming up, without anyone checking the ERP.
How you'll know: A "Drake Corp" created by the web shop and another created by a rep, each with half the history.
Fix: Match on a stable ID held in an external ID field on both sides, never on the company name.
How you'll know: A phone number or address changes, then changes back an hour later.
Fix: Decide which system owns each field. The other side reads it and never writes it.
How you'll know: The integration stops in the afternoon with REQUEST_LIMIT_EXCEEDED and catches up overnight.
Fix: React to changes instead of polling every few minutes, and move big loads to the Bulk API.
How you'll know: Everything breaks the week that person leaves or resets their password.
Fix: Run it as a dedicated integration user with only the permissions it needs.
How you'll know: Someone notices in a pipeline meeting that orders stopped arriving on Tuesday.
Fix: Log every failed record, retry it, and alert a named person when retries give up.
15 sales reps on Salesforce, with NetSuite for ERP and accounting.
A contractor calls: 200 units of product X to the downtown site by Friday, what's the balance on the account, and did the last shipment arrive?
The rep puts them on hold, checks stock in one NetSuite screen, the balance in another, tracking in the shipping portal, then comes back to Salesforce to log the call. Five minutes for a one-minute conversation.
The account in Salesforce shows a panel with stock and delivery date for product X, the outstanding balance and last payment, and the last shipment signed for on site.
The rep places the order from that screen. It syncs to NetSuite, the invoice is created, the label is made in ShipStation, and the contractor gets a confirmation email.
One tab, about a minute, and nothing left to retype afterwards.
The data that ends up on a Salesforce account is the same data customers phone in to ask about. After the sales side works, the next step is often a portal where they check orders, invoices and tickets themselves. How we build self-service portals →
The same connections can put sales context in front of support agents, and can take orders online without a rep in the middle. Support with the full account picture → · Selling online from the same data →
Specific parts of Salesforce, and the systems most often connected to it.
A connected app is how an outside system signs in to Salesforce through OAuth instead of a shared password. Salesforce now turns off creating new connected apps by default and points new integrations to External Client Apps, which do the same job. Connected apps you already have keep working. Any integration we build authenticates through one of the two, never a person's login.
For a few simple, low-volume triggers, it can be. Once there's real logic, like routing a lead by deal size or holding a sync until an order is approved, it's usually better built against Salesforce's API directly, with logging and retries. That's the kind of Salesforce integration n-frames builds.
Start with the connectors listed on AppExchange and check them against your products and pricing. If every product maps to one item in the books, a connector is often enough. Bundles, custom pricing and partial shipments are where a custom sync earns its keep. See Salesforce and NetSuite for the details on that pair.
Salesforce caps API requests per org in a rolling 24 hours, and the cap depends on your edition and number of licenses. You can see current usage in Setup under Company Information. An integration that polls every minute can burn through it. One that reacts to changes and uses the Bulk API for large loads rarely does.
Yes. HubSpot has its own Salesforce connector that syncs contacts, companies and deals both ways. Most teams running both use it for the marketing-to-sales handoff. If you're picking one over the other instead, see HubSpot vs Salesforce.
n-frames builds Salesforce integrations for sales teams that run on more than a CRM: live stock and balances on the account, closed opportunities that create the order and invoice, and syncs that log and retry instead of failing quietly. If the bottleneck turns out to sit outside Salesforce, we work on that instead.
Put my ERP on the account record →