How to Fill Out Data & Integration Scope Fields

Published on October 9, 2026 QuoteX


How to Fill Out Data & Integration Scope Fields

When adding a scope item, the fields you fill out adapt depending on the Category of work you select. Follow this guide to ensure consistency across all scope definitions.

In this guide: what each scope field means, how to complete the fields for each Category, and a one-table cheat sheet you can keep handy.


Field Overview

  1. Migration Id: A unique tracking ID for the deliverable (e.g., INT-001, DM-001, OCM-001, STR-001).
  2. Category: The type of work being scoped (Integration, Data Migration, Change Enablement, or Strategy).
  3. Integration Direction: The direction data or processes flow (Inbound, Outbound, Bi-Directional, or None).
  4. ETL Type: The technical execution method or delivery format.
  5. Functional Area: The core business domain or Salesforce module impacted.
  6. Objective: A concise statement explaining what is being done and why.

How to Fill Out Fields by Category

1. Category = Integration

Use this category when connecting Salesforce with external systems (e.g., ERP, payment gateways, front-end apps).

  1. Integration Direction: Select Inbound (data coming into Salesforce), Outbound (data going out), or Bi-Directional (two-way sync).
  2. ETL Type: Select the timing pattern — Real-Time / Event-Driven, Near Real-Time (Micro-batch), or Streaming API / Ingestion.
  3. Functional Area: Select the connected system or business area (e.g., ERP / Operations, Revenue / CPQ / Billing, E-Commerce, Service / Support).

Objective Example: "Connect Next.js front-end web app with Commerce Cloud Storefront APIs for real-time cart and checkout."

2. Category = Data Migration

Use this category for loading, archiving, or cleaning datasets (e.g., legacy data loads, sandbox seeding, or data archiving).

  1. Integration Direction: Usually Inbound (if loading external data into Salesforce) or None (if archiving or cleaning data within Salesforce).
  2. ETL Type: Select the batch loading style — Batch (Bulk API), One-Time Cutover Load, or Manual File Import.
  3. Functional Area: Select the data domain (e.g., Sales / CRM, Service / Support, DevOps / Operations).

Objective Example: "Archive 50M+ historic Activity records to Big Objects using Async SOQL for LDV management."

3. Category = Change Management

Use this category for user enablement, training, process adoption, and stakeholder communication.

  1. Integration Direction: Select Internal / N/A (or Cross-Functional / Top-Down depending on your process).
  2. ETL Type: Describe the delivery method — Role-Based Training, Asynchronous E-Learning, or Interactive Workshops.
  3. Functional Area: Select End-User Enablement, Sales Operations, or Customer Support Teams.

Objective Example: "Develop and deliver interactive Agentforce training modules to 200 customer support reps prior to go-live."

4. Category = Strategy & Governance

Use this category for architecture blueprints, security policies, multi-org strategy, and release management frameworks.

  1. Integration Direction: Select None (or Enterprise-Wide).
  2. ETL Type: Select the governance mechanism — Architecture Review Board (ARB), Policy & Guideline Definition, or Audit & Assessment.
  3. Functional Area: Select Enterprise Security, DevOps / Operations, or Data Cloud / CDP.

Objective Example: "Architect role hierarchies, Apex Managed Sharing rules, and Salesforce Shield monitoring policies for HIPAA compliance."


Quick Cheat Sheet for End Users

Category SelectedTypical Integration DirectionTypical ETL / Execution TypeExample Objective
IntegrationInbound / Outbound / Bi-DirectionalReal-Time / Event-DrivenQuery ERP order status via Apex APIs to triage service cases.
Data MigrationInbound / OutboundBatch (Bulk API) / One-Time LoadMigrate 5M historical Contact records from legacy CRM into Salesforce.
Change ManagementNoneRole-Based Training / WorkshopsTrain 150 sales reps on new CPQ dynamic discounting workflows.
Strategy & GovernanceNoneARB Review / Policy DefinitionEstablish a Multi-Org governance model and shared deployment pipeline.

Tip: Choose the Category first. The Integration Direction, ETL Type, and Functional Area options you should pick all follow from it.


Knowledge Article Number: KA-00460

View more articles in the knowledge base