Should You Wait on Salesforce Until Your ERP Is Stable?

An ERP implementation can make it feel like every other systems project needs to wait. Data is changing. Processes are being reworked. Internal teams are already stretched. The last thing anyone wants is to build something in Salesforce that has to be rebuilt six months later.

But that does not mean Salesforce has to sit on the sidelines until the ERP work is finished.

For manufacturers, the right timing for an ERP Salesforce integration for manufacturing depends on which workflows need ERP data and which can start delivering value without it. Some Salesforce work may be able to move forward while the ERP is still changing, as long as the eventual connections are considered from the start.

That might mean improving pipeline visibility, account management, forecasting, or other customer-facing processes now, while planning ERP-dependent capabilities for the right point in the rollout.

Why Does ERP Timing Feel Like a Salesforce Blocker?

ERP timing can feel like a Salesforce blocker because the ERP often holds operational information that sales and service teams need to do their jobs. Order history, pricing, inventory, contract terms, and customer-specific agreements may all live there.

When that information is changing, building integrations around it can feel risky. No one wants to spend time and budget connecting Salesforce to an ERP structure that may look different by go-live.

Where manufacturers can get stuck is treating that integration risk as a reason to put all Salesforce work on hold.

Not every Salesforce workflow needs live ERP data from day one. A sales team may be able to improve opportunity management and pipeline visibility before order history is connected. Account information can often be organized before every back-office connection is in place.

At the same time, some workflows depend heavily on ERP data. A rep cannot reliably quote from Salesforce if the pricing or customer-specific terms they need still live in a changing ERP environment.

The ERP timeline alone should not make the decision. What matters is how people need to use Salesforce, which information they need to do their jobs, and where that information needs to come from.

What Is an ERP Salesforce Integration for Manufacturing?

An ERP Salesforce integration for manufacturing connects Salesforce with operational data managed in the ERP. Depending on how the manufacturer works, that can include order history, pricing, inventory availability, fulfillment status, or other information sales and service teams need to work effectively in Salesforce.

The purpose is not to move every piece of ERP data into Salesforce. It is to give employees access to the right information in the system where they are doing the work, while maintaining clear ownership between Salesforce and the ERP.

That distinction matters in manufacturing because customer-facing processes often cross system boundaries. A salesperson may manage an opportunity in Salesforce but need pricing from the ERP. A service employee may work from a Salesforce case but need current order or fulfillment information to answer the customer.

The systems need to work together where the business requires them to.

Which Salesforce Functions Depend Most on ERP Data?

Salesforce workflows tend to have stronger ERP dependencies when employees need current operational information to complete the process. Automated quoting may require current ERP pricing or customer-specific terms. Sales and service teams may need inventory availability before making commitments to customers. Account managers may need current order status or purchase history to answer customer questions accurately.

Other Salesforce workflows may have less direct dependency on ERP data. Opportunity and pipeline management, sales activity tracking, account and contact management, lead routing, and territory management may be able to move forward while ERP work continues, depending on how the manufacturer operates.

“The biggest breakdown typically stems from legacy systems never designed to talk to each other—ERPs, spreadsheets, disconnected manufacturing execution systems, various CRMs. Each is optimized for a silo, not the business as a whole.”

Jordan Joltes, CEO and Founder, TruSummit Solutions

That silo problem is exactly what manufacturers should avoid recreating.

Moving some Salesforce work forward does not mean treating Salesforce as an isolated sales system. It means identifying the workflows that can provide value now while still planning for the information Salesforce will eventually need from the ERP and other systems.

If a workflow cannot provide value without ERP data, it may make sense to wait until that data is ready. If it can solve a real problem today without creating another workaround, there may be no reason to hold it back.

The point is to sequence the connection, not avoid it.

What Can Manufacturers Build in Salesforce Before the ERP Stabilizes?

Manufacturers may be able to move forward with Salesforce workflows that do not require current ERP data to function effectively. The exact scope depends on how employees work today and which systems hold the information they need.

For example, a manufacturer may be able to improve opportunity management and pipeline visibility without a live ERP connection. Sales activity tracking, account management, lead routing, territory management, and some forecasting workflows may also be able to move forward if employees can use them without relying on current ERP information.

The situation changes when the workflow crosses into operational data.

Take quoting. Salesforce can support a quoting process, but if reps need current ERP pricing, inventory availability, or customer-specific terms every time they build a quote, leaving that information disconnected may simply replace one workaround with another.

The same reasoning applies to customer service. A service workflow may be able to move forward without an ERP connection if employees already have what they need in Salesforce. If answering a customer requires current order or fulfillment information from the ERP, that dependency needs to be part of the design.

Just because something can be built without the ERP does not mean it should be.

Before moving a workflow forward, manufacturers need to understand what the employee is trying to accomplish, what information the process requires, where that information lives, and how current it needs to be.

When that sequencing is done well, ERP go-live does not have to mark the starting line for the entire Salesforce implementation. Teams may be able to start working in Salesforce while the right ERP connections are added as the underlying data and processes become ready.

How Should You Plan a Salesforce ERP Integration Before the ERP Settles?

Manufacturers can plan how Salesforce and the ERP need to work together before every technical detail of the ERP is finalized. The level of detail should reflect how settled the ERP environment actually is.

You do not want to lock yourself into field mappings and technical decisions while the ERP team is still changing the underlying structure. But waiting to think about integration until every ERP decision has been made can create problems of its own.

There is useful planning that can happen between those two extremes.

During the Trail Mapping phase of TruSummit Solutions’ implementation methodology, the team looks at where information needs to move between systems, which system should own it, and what employees actually need to see or do in Salesforce.

That might mean knowing Salesforce will eventually need order status from the ERP without defining every field-level mapping on day one. Or it might mean knowing that pricing will remain ERP-owned while determining how reps should access that information during the quoting process.

“We start by anchoring to a specific business outcome—improving on-time delivery or increasing forecast accuracy. Then we identify the minimal connections required to make that outcome possible.”

Jordan Joltes, CEO and Founder, TruSummit Solutions

That approach keeps the integration from becoming a technical exercise disconnected from the reason the systems need to talk in the first place.

If the goal is better forecast accuracy, the conversation should focus on what information Salesforce needs to support a more reliable forecast. If the goal is better visibility into on-time delivery for customer-facing teams, the question becomes what employees need from the ERP to answer customer questions without chasing operations for an update.

Not every piece of ERP data needs to live in Salesforce. The systems need to share the information required to make the workflow work.

What If You Are Replacing the ERP?

If an ERP replacement is already planned or under consideration, Salesforce should be designed with that future change in mind. Otherwise, Salesforce can become unnecessarily tied to an ERP structure the business is preparing to retire.

For example, custom Salesforce objects, fields, or automation built around identifiers that only make sense in the current ERP may need to be revisited when the new system arrives.

That does not automatically mean Salesforce should wait.

Where it makes sense, Salesforce can use standard objects and business-friendly structures rather than recreating ERP-specific structures inside the CRM. Workflows that do not need the ERP may still be able to move forward without being tied unnecessarily to the outgoing system.

The goal is not to eliminate every dependency. Manufacturing systems need to work together, and some Salesforce workflows will legitimately depend on ERP data.

The goal is to make those connections intentional.

“Scalability is about intentional simplicity planned in advance.”

Jordan Joltes, CEO and Founder, TruSummit Solutions

That principle becomes especially important when part of the technology environment may change.

Keeping the Salesforce design as simple as the business allows can make it easier to connect a new ERP later without unraveling unnecessary dependencies across the CRM. It is also why scoping decisions made before configuration starts matter so much.

How Do You Decide What Salesforce Work Moves Now and What Waits?

The decision should be made workflow by workflow, based on what employees need and where the required data lives. An ERP project by itself is not enough information to decide whether Salesforce should move forward.

Start with the process the employee is trying to complete. Identify what needs to become easier or more reliable, what information the employee needs to complete the work, and where that information lives today. If some of it comes from the ERP, determine whether that data is stable enough to use and whether it needs to be available in Salesforce now.

Then consider what happens if the workflow moves forward without that connection.

A manufacturer trying to improve pipeline visibility may be able to make progress in Salesforce while the ERP project continues. The information required to manage opportunities may already be available without a live ERP connection.

A manufacturer trying to give reps accurate inventory and customer-specific pricing during quoting faces a different situation. If those details are managed in the ERP, the Salesforce workflow may depend on more of the ERP foundation being in place first.

Both are Salesforce projects. They simply have different dependencies.

The most useful test is whether moving the workflow forward removes friction or creates another workaround. If employees can use the Salesforce process effectively today, it may make sense to proceed. If they will still need to leave Salesforce, check another system, reconcile conflicting information, or manually bridge a gap every time they complete the process, the sequencing may need to change.

ERP Work Does Not Automatically Put Salesforce on Hold

An ERP implementation does not automatically mean Salesforce should wait. It also does not mean every Salesforce workflow should move forward while the ERP is still changing.

The decision comes down to how your teams need to work and what information they need to do it.

Some workflows can provide value before an ERP connection is ready. Others depend on pricing, inventory, order status, or other operational data and need to be sequenced around the ERP. What matters is identifying those dependencies before configuration starts rather than discovering them after employees are already working around the system.

That is also where the broader Salesforce and ERP roadmap matters. Moving Salesforce forward should not create another silo. The systems should ultimately work together around the way the business actually operates, with each connection serving a clear purpose.

If your manufacturing team is deciding what can move forward now and what should wait, talk with a TruSummit Solutions senior consultant about your current systems, priorities, and where the ERP and Salesforce roadmaps overlap.

Frequently Asked Questions

Can we start a Salesforce implementation while our ERP is still being configured?

In many cases, yes. Pipeline management, activity tracking, account management, CRM-based forecasting, and other capabilities may be able to move forward without a completed ERP integration.

The deciding factor is what information those workflows need. If employees cannot complete the process without current ERP data, that dependency needs to be accounted for in the scope and timing.

Starting Salesforce before the ERP is complete should not mean designing the two systems independently. The eventual connections still need to be considered as Salesforce is scoped.

What is the risk of building Salesforce integrations before the ERP is stable?

One important risk is building around ERP structures that later change. If fields, identifiers, processes, or system ownership are still being worked out, integration decisions made too early may need to be revisited.

Manufacturers can still plan how the systems need to work together before those details are final. The level of technical detail should match how settled the ERP environment actually is.

How does a potential ERP replacement affect Salesforce planning?

A potential ERP replacement makes flexibility more important in the Salesforce design. Salesforce should not be unnecessarily structured around an ERP the manufacturer may soon replace.

Using standard Salesforce objects and containing ERP-specific dependencies where possible can make the eventual transition easier to manage. That does not mean ignoring the ERP. It means connecting the systems where the business needs them connected without unnecessarily recreating the ERP’s structure inside Salesforce.

Which Salesforce functions are most dependent on ERP data in manufacturing?

Strong ERP dependencies often involve pricing, inventory availability, order status, purchase history, and other operational information. These workflows depend on information that may be managed outside Salesforce and may need to be current for employees to complete the process accurately.

Pipeline management, activity tracking, account management, and some forecasting or service workflows may have less direct dependency on the ERP. The exact split varies because manufacturers use their ERP and CRM differently.

What does a manufacturing ERP Salesforce integration typically involve?

A manufacturing ERP Salesforce integration connects Salesforce with the ERP-managed information employees need to complete customer-facing work. Depending on the manufacturer, that may include order history, pricing, inventory availability, product information, fulfillment status, or customer data. Salesforce maintains a resource on what ERP systems are and how they connect to CRM that outlines the general framework.

The goal is not to bring everything from the ERP into Salesforce. It is to make the right information available where employees need it while keeping clear ownership between the two systems.

If an ERP replacement is also being considered, the integration should account for that future change so Salesforce does not become unnecessarily tied to structures that may soon be replaced.