1. Home
  2. Services
  3. Salesforce implementation

Salesforce implementation: we set up the org, move your data in and train your team

A Salesforce implementation turns a new, empty org into the place your team sells and serves customers. Our team covers it from start to finish: setup, data move and training, on site or remote. This page walks through each step, the Salesforce tool it uses and the limit Salesforce sets for it, as we read Salesforce's guides on 18 November 2026. If you are choosing who implements it, the nine questions near the end come with Salesforce's own numbers.

Checked 18 November 2026

What a Salesforce implementation covers with us

We take a Salesforce implementation from an empty org to a team that works in it every day. Our team sets up the org, moves your records in and trains your people, on site or remote, as you prefer. An org is your company’s own Salesforce account, with its own users and records.

The work runs in seven steps. The edition choice and the data move each have a section of their own; the other five sit under “How we run a Salesforce implementation”.

  1. Choose the edition and plan. The edition decides which tools the build can use.
  2. Map how you sell and serve. Your stages, your records and who approves what.
  3. Build and test away from live data. Changes go to production only once they pass.
  4. Set up roles and sharing. These decide who sees and edits each record.
  5. Move the data in. Sized to the limits in Salesforce’s own load guides.
  6. Deploy to production. As a set, with the tools Salesforce supports today.
  7. Train the team, then go live. In your own org, on your own records.

Agent work can join the same project or follow after go-live. Our Salesforce AI agents page covers Agentforce and custom agents, and lists the sandbox types each edition includes. This page does not repeat that list.

What Salesforce gives you before you hire anyone

Every Salesforce license comes with the Standard Success Plan. Core, Advanced and Max licenses also include the Premier Success Plan. Check what you already pay for before you pay anyone for advice.

Scroll the table sideways to see every column.

Plan Who gets it What Salesforce lists
Standard Included in all licenses, from the first day Self-guided resources around the clock: help articles, documentation and Trailhead
Premier Included with Core, Advanced and Max licenses 1-to-1 sessions with Salesforce experts, health checks with advice, a reply within 1 hour for issues that hurt the business
Signature Through your Salesforce account executive Help 24/7, holidays and weekends too, with 15-minute replies for issues that stop the business; experts who work in your sandbox on your agents

Salesforce says you can hold different Success Plans for different Salesforce products. It also sells Professional Services, which it calls advisory and implementation services, including Agentforce work. Trailhead, its learning site, is free. For the license prices Salesforce publishes, see our Salesforce cost article.

Premier gives advice and fast support, but it does not build your org. The hands-on setup in your own org, the move of your own records and the training on your own process are separate work. Salesforce’s Professional Services sells that work, and so do outside teams like ours.

Your edition decides what the build can use

Check your edition first, because it sets which tools exist in your org. Salesforce has renamed its editions. Its pricing page says Core replaces Enterprise Edition, Advanced replaces Unlimited Edition, and Max replaces Agentforce 1 Edition. It says Agentforce, Slack, Tableau, Data 360 and Premier Success are now included in each of the new editions: Core, Advanced and Max.

Salesforce’s guides still use the old names. So read “Enterprise” in a guide as the edition that Core replaced.

Scroll the table sideways to see every column.

Tool Editions Salesforce lists Why it matters for the build
Apex, Salesforce’s own code language Enterprise, Performance, Unlimited, Developer and Database.com Rules that clicks cannot express need Apex
Data Loader Enterprise, Performance, Unlimited and Developer Loads past the browser wizard’s limit need it
APIs Sales Cloud Core includes APIs Every link to another system calls them
Premier Success Plan Core, Advanced and Max Expert sessions and health checks, included in the license

Every Sales Cloud edition comes with a free 30-day trial, Salesforce says. It says Sales Cloud Core also includes Agentforce with the free Salesforce Foundations add-on.

How we run a Salesforce implementation, step by step

Each step below names the Salesforce tool it uses. Each project’s scope is set with you before work starts.

Map how you sell and serve

The first workshop lists your pipeline stages, the records each team keeps and every approval in the chain. Then each one gets a Salesforce object, the name Salesforce gives a kind of record. Salesforce’s Object Reference defines them. An Opportunity is a sale or a pending deal. A Quote holds the prices you propose. An Order is tied to a contract or an account. Each column in the spreadsheet you use now becomes a field on one of these objects.

Build and test away from live data

We build in a sandbox, a copy of your org that is kept apart from production. Salesforce ships a major release three times a year. During each one, you can test the new release early in sandboxes and scratch orgs, before your live org is upgraded. We test your setup on the new release in that window, before go-live.

Set up roles and sharing

Who may see and edit each record is set by profiles, roles and sharing rules. Order matters here, and Salesforce’s guide for large data volumes, which it writes for experienced application architects, sets one out for a first load. Where it can, load users into their roles first. Then load records with their owners, which sets off the role hierarchy’s calculations. Then set up public groups and queues. Add sharing rules last, one at a time, and let each one finish before the next.

Deploy to production

Changes move from the sandbox to production as a set. Salesforce says change sets can hold up to 10,000 files of metadata, which is the setup itself rather than your records. It says not to use unmanaged packages to move work from a sandbox to production, and to use change sets instead. For scripted deploys, Salesforce CLI replaced the Ant Migration Tool, which Salesforce retired with Spring ’24.

Train the team, then go live

We train each team in your own org, on your own records, on site or remote. Trailhead comes with the Standard Success Plan, so people can learn the screens on their own before a session. Go-live is the day the team stops using the old tool and starts logging every deal in Salesforce.

Moving your data in without slowing the org

Size decides the tool. Pick it by record count, then follow Salesforce’s rules for big loads, so sharing sums and triggers do not run once per record.

Scroll the table sideways to see every column.

Tool Use it when Salesforce’s limit or rule
Data Import Wizard Fewer than 50,000 records, into an object with fewer than 50 fields Can stop duplicates by account name and site, contact email or lead email
Data Loader Larger loads, nightly loads, backups Up to 150 million records with Bulk API 2.0; needs Java 17 or later; command line on Windows only
Bulk API 2.0 from code Jobs over 2,000 records, which Salesforce calls good candidates 15,000 batches in a rolling 24 hours, shared with the older Bulk API

Salesforce’s Data Loader guide, version 68.0, also says to run only the latest Data Loader, because older versions get no support. Each run writes success and error logs as CSV files, which show what moved and what failed.

Salesforce’s rules for a big first load

These come from Salesforce’s guide to deployments with large data volumes. Salesforce counts a deployment as large when it has tens of thousands of users, tens of millions of records, or hundreds of gigabytes of record storage. Salesforce says a smaller org can still learn from them.

  • Open sharing for the first load. Salesforce advises Public Read/Write security during the first load, to skip sharing sums.
  • Defer the sharing sums. An admin can hold sharing calculations with a defer permission until all data is in.
  • Switch off triggers and rules. Turn off Apex triggers, workflow rules and validations during loads. Batch Apex can then process the records once the load is done.
  • Group child records by parent. Records that share a parent go in the same batch, which cuts locking conflicts.
  • Sign in once. A custom load signs in once per load, not once per record.
  • Watch the owners. No user should own more than 10,000 records.
  • Watch the parents. No parent record should have more than 10,000 child records.

Deleting test records before go-live

Test loads leave records to remove. Salesforce keeps deleted items in the Recycle Bin for 15 days, and they can be restored in that time. For one million or more records, Salesforce advises the hard delete option of the Bulk API or Bulk API 2.0. When you copy a large production org into a sandbox, it advises leaving out field history if you do not need it.

Six patterns Salesforce uses to connect other systems

If your ERP, billing system or website must read or write Salesforce records, Salesforce’s Integration Patterns guide names six ways to do it. Picking one is a design choice that comes before any code. Salesforce says its own consulting architects use these patterns in their architecture reviews.

Scroll the table sideways to see every column.

Pattern What happens, in Salesforce’s words A job it fits
Request and Reply Salesforce calls a remote system and waits for the answer A credit check before a quote is saved
Fire and Forget Salesforce calls a remote system and does not wait Sending a won deal on to the ERP
Batch Data Synchronization Updates run in batches, in either direction A nightly load of new prices
Remote Call-In A remote system creates, reads, updates or deletes Salesforce data The ERP writing invoice status back
UI Update Based on Data Changes The screen updates itself when Salesforce data changes An order status panel for reps
Data Virtualization Salesforce reads outside data in real time and does not store it Stock levels that stay in the ERP

A few API facts shape each pattern. Salesforce counts API limits for the whole org, not per user, so every link shares one allowance. A regular composite request bundles up to 25 subrequests into one call. Salesforce keeps Change Data Capture events for three days, which lets a system that went offline read what it missed. It offers Pub/Sub API as a single interface for both platform events and change events.

For the links themselves, see Salesforce integration. Pages for single pairs cover NetSuite and Salesforce, Salesforce and SAP and Salesforce and QuickBooks.

Dated changes to plan a go-live around

Salesforce changes on a fixed beat, and some older parts have end dates. Building on current parts keeps a new org out of rework next year.

  • Three releases a year. You can test each major release early in sandboxes and scratch orgs, before your live org is upgraded.
  • Old API versions. Salesforce retired versions 21.0 through 30.0 as of Summer ’25. Support for versions 31.0 through 40.0 ends in Summer ’27, and they are retired from Summer ’28.
  • SOAP login(). Salesforce is retiring this sign-in call in the Summer ’27 release. Orgs created in Winter ’26 and later have it off by default.
  • Connected apps. Creating new connected apps is restricted as of Spring ’26. Salesforce recommends external client apps instead.
  • Ant Migration Tool. Retired with Spring ’24. Salesforce points users to Salesforce CLI.

These dates matter when you move from an older org or keep old tools. A data tool or link that still signs in with login() needs a new sign-in before Summer ’27. So list every outside tool that signs in to your org before go-live.

Where your Salesforce data lives

Salesforce calls Hyperforce its infrastructure built for the public cloud. Its trust pages say some services run on Hyperforce and others on other infrastructure. It lists Hyperforce regions that include the US, the UK, Germany, India and Japan. Salesforce also warns that a product may have parts that run in different countries, or may link to services not yet on Hyperforce. Check the region. A UK or German buyer should confirm it with Salesforce before signing.

Questions to ask whoever implements your Salesforce

Ask how they will handle the limits on this page. A team that knows Salesforce from the inside answers each one with a Salesforce tool and a number.

  1. Which Success Plan do we already have? Premier comes with Core, Advanced and Max, so you may already have expert sessions.
  2. Where will you build and test? The answer should be a sandbox, with a test on the next release in its preview window.
  3. Which tool moves our data? Fewer than 50,000 records can use the wizard. Bigger loads need Data Loader or Bulk API 2.0.
  4. In what order do users and records load? Salesforce’s guide says users go into their roles first, where possible.
  5. Will triggers and validations be off during the load? Salesforce advises it, then batch Apex afterwards.
  6. Which pattern fits each link to another system? There are six, and the choice comes before code.
  7. Does any tool still sign in with login() or a connected app? Both have dated changes.
  8. How do changes reach production? Change sets or Salesforce CLI, never an unmanaged package.
  9. Who trains our team, and where? Your own org and your own records beat a generic demo.

Our team’s Salesforce work

Our team takes Salesforce implementations from first setup to a trained team: the org set up, the records moved in and every team trained, on site or remote.

Our team has built Salesforce agents in two ways. Some run inside Agentforce, and some are custom agents that call Salesforce’s API.

Data work on Salesforce is part of our team’s record too, including moving a company’s records into a new org during an implementation.

The case studies page shows four of our builds, with the system and the job in each.

Separately, our team has taken nine ERPs live: SAP, Oracle NetSuite, Odoo, Microsoft Dynamics, ERPNext, Xero, QuickBooks, Sage and custom ERPs. So the system is your choice. Our ERP implementation services page covers that work.

The first call is free.

Questions

How long does a Salesforce implementation take?

It depends on your org more than on Salesforce. Four things set the pace: how many records move, how much custom code your rules need, how many sharing rules you have, and how many teams need training. The Salesforce pages we read publish no standard timeline. One fixed beat helps planning. Salesforce ships three major releases a year, and you can test each one early in sandboxes before your live org is upgraded.

What does Salesforce's Premier Success Plan include?

Salesforce lists Premier as included with Core, Advanced and Max licenses. It adds 1-to-1 sessions with Salesforce experts on any topic, health checks with recommendations, and a reply within 1 hour for issues that hurt the business. Standard comes with every license and covers help articles, documentation and Trailhead. So check your plan first. You may already have the advice you were about to buy.

Do we need an official Salesforce partner for the implementation?

Not for this work. A go-live depends on a team that knows Salesforce from the inside and uses the tools Salesforce publishes, such as Data Loader, Bulk API 2.0 and change sets. Our team has taken Salesforce implementations end to end: the org set up, the data moved in and the team trained. You buy licenses from Salesforce or its reseller. We take the consulting, setup, data move and training from there.

Can we move to Salesforce from spreadsheets or another CRM?

Yes. Spreadsheets and exports from an old CRM come in as CSV files. For fewer than 50,000 records, Salesforce's Data Import Wizard works in the browser and can stop duplicates by account name and site, contact email or lead email. Bigger moves run on Data Loader, which Salesforce's guide says takes up to 150 million records with Bulk API 2.0. We test a sample first, then load the rest.

What does a Salesforce implementation cost?

We quote each project on its own, so this page carries no figure of ours. Your bill has two parts. Salesforce charges for licenses, and its Success Plans differ by edition. The implementation work is priced by its size: the objects and records that move, the custom code, and the number of teams to train. Our Salesforce cost article lists the prices Salesforce publishes.

Do you need access to our live Salesforce org?

Not at first. We set things up and test them in a sandbox, a separate copy of your org, so nothing touches live records. Only the final deploy and the data load reach production, and both follow a plan you approve. We sign your NDA before you share any data, if you ask.

Where does Salesforce store our data?

In general, in the country where your org is located, if the services you use run on Hyperforce there. Salesforce says its Hyperforce regions include the US, the UK, Germany, India and Japan. It adds that some products have parts that run in other countries, or link to services not yet on Hyperforce. Ask your Salesforce account executive which region your org sits in before you sign.

Sources

Every source behind a figure or a vendor fact on this page, with the day we read it.

Plan your Salesforce implementation

The first call is free. Bring your edition, a rough count of your records and the teams that will work in Salesforce. We talk through the steps on this page for your org.

Plan your Salesforce rollout