plan-bulk-migration

plan-bulk-migration is a command for Claude Code from BanibrataChatterjee/AwesomeSalesforceSkills. It costs 0 tokens per session (535 once invoked), scanned A, original, Apache-2.0.

A planning command for choosing how to move data into or out of Salesforce. It uses record volume, speed requirements, data direction, and the connected system to recommend an integration approach.

In plain words
What is it for?
Use it to plan inbound, outbound, or two-way migrations and integrations involving systems such as SAP, Snowflake, Kafka, or Salesforce Marketing Cloud.
Why use it?
It reduces guesswork when several Salesforce interfaces could handle the same data transfer but have different limits and timing.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Use it to plan inbound, outbound, or two-way migrations and integrations involving systems such as SAP, Snowflake, Kafka, or Salesforce Marketing Cloud.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/banibratachatterjee/awesomesalesforceskills/plan-bulk-migration
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for plan-bulk-migration

README.md
[![agentmods](https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/plan-bulk-migration/github.svg)](https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/plan-bulk-migration)
Your own site
<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/plan-bulk-migration"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/plan-bulk-migration/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for plan-bulk-migration

Your own site · 80×15
<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/plan-bulk-migration"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/plan-bulk-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 535 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00535
Opus 5 $0.00000 $0.00267
Sonnet 5 $0.00000 $0.00107
Haiku 4.5 $0.00000 $0.00053

Measured 10d ago against content hash 54e8619ab57e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

plan-bulk-migration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/plan-bulk-migration.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/plan-bulk-migration — Pick the right Salesforce integration pattern

Wraps agents/bulk-migration-planner/AGENT.md. Given a volume + latency + source + direction, returns an implementation plan selecting between Bulk API 2.0, Platform Events, Pub/Sub API, REST Composite, Salesforce Connect, Apex REST, or CDC.


Step 1 — Collect inputs (ask all four upfront)

Ask:

1. Direction? inbound / outbound / bidirectional

2. Volume per run?
   Example: 8M records/week, 50k/day, real-time event stream

3. Latency tolerance?
   T+24h / T+1h / near-real-time (seconds) / sub-second

4. Source or target system?
   Example: SAP S/4HANA, Snowflake, Kafka, SFMC

Optional:
5. Does the integration require idempotency? (yes/no)
6. Expected error rate / PII handling needs?
7. Target-org alias for ground-truth lookups?

If any of the four required inputs is missing, STOP and ask all four.


Step 2 — Load the agent

Read agents/bulk-migration-planner/AGENT.md fully + integration-pattern-selection.md + the integration skills it lists.


Step 3 — Execute

Follow the 5-step plan:

  1. Route via the decision tree → pick one pattern + note alternatives
  2. Sketch the runtime (job/topic/endpoint specs, chunking, auth)
  3. Idempotency + exactly-once strategy
  4. Observability (Application_Log__c, Event Monitoring, alerts)
  5. Rollout plan (dev → prod + feature flags + cutover)

Step 4 — Deliver

  • Executive summary: selected pattern + decision-tree branch
  • Runtime spec (fenced code blocks for job / topic / endpoint definitions)
  • Named Credential + Auth spec
  • Idempotency strategy
  • Observability plan
  • Rollout plan
  • Alternative patterns considered
  • Citations

Step 5 — Recommend follow-ups

  • /gen-tests on any Apex scaffolds the plan produces
  • /scan-security on the Named Credential and inbound endpoint
  • /score-deployment before first production push

What this command does NOT do

  • Does not build the integration client — produces the spec.
  • Does not create Named Credentials in the org.
  • Does not recommend MuleSoft unless the decision tree routes there.

Read the full file on GitHub · 76 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 76 lines · 0 tokens per session scan A 54e8619ab57e

Subscribe to this mod's changes

plan-bulk-migration is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 535 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.