lsc-config-migration
Skill10 starsChanged 29 days agoApache-2.0View on GitHub
Guides migrating Life Sciences Cloud (LSC) org configuration (Admin Console settings, DB Schema, trigger handlers, quick/custom actions) between orgs using export → diff → selective import. Use when the user wants to copy, promote, migrate, sync, or replicate LSC configuration from one org (e.g. a sandbox) to another (e.g. UAT or production), compare config drift, or apply a saved config snapshot. This is for CONFIGURATION metadata, not data records — for loading accounts/HCPs/territory data use lsc-data-migration instead.
In this repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- roz-uiSkill
- lsc-account-managementSkill
- lsc-activity-planSkill
- lsc-agentforceSkill
- lsc-app-alertsSkill
- lsc-briefingsSkill
- lsc-calendar-tot-routineSkill
- lsc-consent-managementSkill
- lsc-custom-scriptsSkill
- lsc-data-migrationSkill
- lsc-data-modelSkill
- lsc-db-schemaSkill
- lsc-demo-data-loadingSkill
- lsc-events-managementSkill
- lsc-field-emailSkill
- lsc-health-checkSkill
- lsc-home-page-configurationSkill
- lsc-implementation-reviewSkill
- lsc-implementationSkill
- lsc-integration-patternsSkill
- lsc-intelligent-contentSkill
- lsc-key-account-managementSkill
- lsc-lists-filtersSkill
- lsc-mobile-app-settingsSkill
- lsc-mobile-validationSkill
- lsc-next-bestSkill
- lsc-performance-validationSkill
- lsc-product-managementSkill
- lsc-provider-engagement-complianceSkill
- lsc-quick-actions-configurationSkill
- lsc-reporting-analyticsSkill
- lsc-sample-managementSkill
- lsc-surveysSkill
- lsc-territory-alignmentSkill
- lsc-troubleshootSkill
- lsc-user-managementSkill
- lsc-visit-managementSkill
- salesforce-querySkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 41
Always report before applying: Run mode: "report" and walk the user through what would change.
- Very specific: line 45
Recommend the UI for large or mixed changesets: When there are more than a handful of records, mode: "ui" lets the user review each field …
- Very specific: line 50
Reassure on safety: Every apply backs up the target to exports/backup-*.json first and writes a result log to exports/import-result-*.json.
- Very specific: line 55
Verify after: If DB Schema or actions changed, regenerate the mobile metadata cache (generate_mobile_metadata_cache).
- Distinctive: line 73
When promoting LifeSciConfig + trigger-handler-dependent metadata via a raw metadata deploy (outside this skill's export/import flow), …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
What this skill covers
Promoting configuration (not data) between LSC orgs:
- Admin Console settings (
LifeSciConfigRecordcategories) - DB Schema records (mobile sync configuration)
- Trigger handlers (
LifeScienceTriggerHandleron/off state) - Quick Actions and Custom Actions
The workflow is export → diff → selective import, and import is create + update-only (safe): it never deletes or deactivates records that exist only in the target, and it auto-backs-up the target before writing.
For background on any of these config areas, call
search_lsc_knowledge({ query: "..." }) (e.g. "DB Schema mobile sync",
"trigger handlers", "quick actions configuration") so answers are sourced.
The workflow
| Step | Tool | Notes |
| 1. Snapshot the source | export_config({ targetOrg: "sourceAlias" }) | Writes exports/*.json (format v1.1 — includes per-field DataType + assignments). Follow /lsc:export-config for the file convention. |
| 2. Review the diff | import_config({ source: "exports/<file>.json", mode: "report" }) | Summarizes New / Changed / Identical / Only-in-target and lists record keys. |
| 3a. Apply interactively | import_config({ source: "...", mode: "ui" }) | Opens a local browser UI with checkboxes + live progress. Hand the user the returned URL. |
| 3b. Apply headlessly | import_config({ source: "...", mode: "apply", selection: [...] }) | Applies only the chosen record keys. |
You can also skip the file and diff two live orgs directly by passing
sourceOrg instead of source.
How to help
- Confirm direction. Which org is the source (correct config) and which is the target (receives changes)? Never assume production is the target without asking.
- Always report before applying. Run
mode: "report"and walk the user through what would change. Highlight anything surprising (e.g. many Changed records, or IsActive flips). - Recommend the UI for large or mixed changesets. When there are more than a
handful of records,
mode: "ui"lets the user review each field change and pick precisely what to apply. For a small, well-understood set,mode: "apply"with an explicitselectionis fine. - Reassure on safety. Every apply backs up the target to
exports/backup-*.jsonfirst and writes a result log toexports/import-result-*.json. Only creates and updates happen — nothing is deleted or deactivated, and target-only records/fields/assignments are kept. - Verify after. If DB Schema or actions changed, regenerate the mobile
metadata cache (
generate_mobile_metadata_cache). Then confirm convergence withimport_config(report mode) again ordiff_orgs.
Gotchas
- Trigger handlers can't be created — only existing handlers can be toggled (IsActive). A handler present in the source but absent from the target is reported but not applied.
- DB Schema / action changes require a mobile metadata cache regeneration to take effect on the iPad app.
DeveloperNameis the match key. Records are matched by DeveloperName, so renaming a record between orgs makes it look like a delete + create.- Old v1.0 snapshots (no per-field DataType) still import — types are inferred, reliably for DB Schema and best-effort elsewhere. Prefer re-exporting at v1.1.
Deploy sequencing: inactive first, then activate
When promoting LifeSciConfig + trigger-handler-dependent metadata via a raw
metadata deploy (outside this skill's export/import flow), deploy in two
passes — deploy the config as inactive first, then activate it — so that
triggers/automation don't fire against partially-deployed configuration and
leave the org in an inconsistent state. This is the ordering LSC's own setup
scripts use (a 1_inactive deploy followed by a 2_activate deploy, then the
trigger-handler activation step). It generalizes to any config whose activation
kicks off automation.
Related
/lsc:export-config,/lsc:import-config,/lsc:diff-orgslsc-data-migration— for loading data records (accounts, HCPs, territory assignments), not configuration.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

