Salesforce Client Org Provisioning and Data Model Mapping (Onboarding)

Salesforce Client Org Provisioning and Data Model Mapping (Onboarding)

1. 01

   Create the client org in Setup > Company Information and confirm the edition against the signed scope.

   Sales Free Suite covers Account, Contact, Lead, and Opportunity Management at $0 per user monthly, but it caps you at basic objects. If the client needs Omni-Channel case routing or Agentforce agents, provision Sales or Service Cloud instead. Record the edition in the client's onboarding doc before any configuration starts, because upgrading mid-build forces a re-map of every custom field.

2. 02

   Map the client's revenue cycle to standard objects in Object Manager before creating a single custom field.

   Walk the client's actual sales motion and assign each stage to Account, Contact, Lead, or Opportunity. Custom objects multiply admin overhead and break Agentforce's out-of-box automations, which are trained on standard schema. For a local service business on the $2,250 Starter CRM Setup, the entire model usually fits in four standard objects plus two custom fields.

3. 03

   Configure user seats and permission sets in Setup > Users, then set the org-wide sharing default.

   Per-user licensing runs $25 to $550 per user monthly depending on tier, so seat count is the line item that decides whether an agency retainer stays profitable. Assign permission sets by role rather than profile, and set sharing to Private for anything touching client PII. Document the seat count in the retainer agreement so scope creep on headcount becomes a change order, not a margin hit.

4. 04

   Connect email and lead capture: Gmail or Outlook integration plus web-to-lead forms.

   Enable Email Integration under Setup > Email, then generate the Web-to-Lead HTML from Setup > Web-to-Lead and hand it to the client's web developer. Add a hidden field for lead source so attribution survives the form submission. Test with a live submission and confirm the record lands in the right queue before declaring the integration done.

5. 05

   Build the two reports and one dashboard specified in the delivery scope.

   Use Report Builder for pipeline-by-stage and follow-up-overdue reports, then pin both to a dashboard the client's team will actually open. The Starter CRM Setup deliverable is two custom reports and one dashboard for pipeline visibility. Resist adding more; every extra report is a support ticket you will field on a fixed retainer.

6. 06

   Wire Slack and Tableau only if the client already pays for them.

   Native Slack integration pushes pipeline alerts into channels the client's team already watches, and Tableau handles the analytics layer. Both add configuration time and neither is included in a basic Sales tier. Confirm the client holds active Slack and Tableau licenses before you spend delivery hours on the connection.

7. 07

   Run a data load test with 50 real records through Data Loader, then delete them.

   Import via Data Loader using the field mapping you built in Object Manager. Check for duplicate Accounts, orphaned Contacts, and picklist values that failed validation. Cleaning this up after go-live costs three times the admin hours, and dirty CRM data poisons every downstream Agentforce automation and report the client relies on.

8. 08

   Hand off with a recorded walkthrough and a named admin on the client side.

   Record the session covering daily lead entry, report refresh, and how to submit a support case. The Services Standard Success Plan includes self-serve Trailhead and Trailblazer Community access plus a 2 day response window for support inquiries, so point the client's admin there for routine questions. An unnamed admin is the single most common reason an agency gets pulled back into unpaid firefighting.