data-migration — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited data-migration (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill enforces structured, evidence-based data migration — preventing the three most common catastrophic failures: migrating without reconciliation, skipping data profiling, and assuming source data is clean.
| Agent Will Try To... | Why It Seems Reasonable | Why It Fails | Counter |
|---|---|---|---|
| Skip data profiling to save time | "We know the source system well" | Knowing the system ≠ knowing its data quality. Legacy data accumulated over years has integrity issues the source team doesn't know about. | Iron Law 2: Profiling is non-negotiable. At minimum: record counts, null rates, format violations, referential integrity checks. |
| Declare migration complete without reconciliation | "Everything loaded without errors" | Error-free load ≠ complete load. Records can be silently skipped, truncated, or misrouted. Only counts prove completeness. | Iron Law 1: Reconciliation report required. Records out = records in, or explain every delta. |
| Use big bang strategy without considering phased option | "It's simpler to do everything at once" | Big bang increases cutover window, risk of failure, and rollback complexity. Phased migration is often safer. Justify the choice with evidence. | Checklist Step 1: Strategy decision documented with justification and risk assessment. |
| Assume vendor/partner master data is correct | "The client maintains this data themselves" | Client-maintained data has format issues, duplicates, and gaps. Profile it the same way as any other source. | Iron Law 3: Profile all sources without exception. |
| Skip trial migration because "dev loads worked" | "We've done partial loads in dev" | Partial dev loads ≠ full trial migration. Trial migration tests volume, performance, error handling, and reconciliation in an integrated environment. | Iron Law 4: Full trial migration mandatory. Dev loads do not satisfy this requirement. |
| Defer cleansing to post-migration | "We'll clean it up once it's in SAP" | SAP has strict validation rules. Dirty data that loads creates more remediation effort in SAP than in the source. Clean before migration. | Checklist Step 3: Cleansing rules and completion criteria defined and executed before load. |
Watch for these phrases in your own reasoning — each signals an Iron Law violation:
<HARD-GATE> Trial migration CANNOT be skipped. Production cutover data load cannot proceed until:
If any condition is unmet, the production load is NOT authorized. Do not proceed. </HARD-GATE>
PROJECT: [Name]
DATE: [Date]
VERSION: [Version]
MIGRATION STRATEGY
------------------
Approach: [Big Bang / Phased — with justification]
Legacy systems: [List source systems]
Cutover window: [Date range, duration]
Rollback trigger: [Conditions that trigger rollback]
OBJECTS IN SCOPE
----------------
| Object | Source System | Tool | Volume (records) | Priority | Owner |
|-----------------|--------------|-------|-----------------|----------|-----------|
| Vendor Master | Legacy ERP | LTMC | ~12,000 | P1 | [Name] |
| Customer Master | Legacy CRM | BODS | ~8,500 | P1 | [Name] |
| Open Items (AP) | Legacy ERP | LTMC | ~45,000 | P1 | [Name] |
| Material Master | Legacy ERP | LTMC | ~30,000 | P1 | [Name] |
MIGRATION TIMELINE
------------------
Data profiling: [Start] → [End]
Data cleansing: [Start] → [End]
Mapping: [Start] → [End]
Trial migration 1: [Date]
Trial migration 2: [Date]
Production load: [Date] [Time window]
RECONCILIATION TOLERANCE
------------------------
Standard objects: 0% variance (exact count match required)
Complex objects: Up to [X]% variance with documented justificationOBJECT: [e.g., Vendor Master]
SOURCE SYSTEM: [e.g., Oracle EBS]
TARGET: SAP LFM1 / LFA1
MAPPING VERSION: [Version]
| Source Field | Source Type | Transformation Rule | Target Table | Target Field | Mandatory | Validation |
|-----------------|------------|---------------------------------------|-------------|-------------|-----------|---------------------|
| VENDOR_CODE | VARCHAR(10) | Prefix with 'V', zero-pad to 10 chars | LFA1 | LIFNR | YES | Unique in LFA1 |
| VENDOR_NAME | VARCHAR(80) | Trim whitespace, UPPER case | LFA1 | NAME1 | YES | Max 35 chars |
| COUNTRY_CODE | VARCHAR(2) | Map legacy to ISO 3166-1 alpha-2 | LFA1 | LAND1 | YES | Valid T005 entry |
| PAYMENT_TERMS | VARCHAR(10) | Map to SAP ZTERM via lookup table | LFB1 | ZTERM | YES | Valid T052 entry |TRIAL MIGRATION: [Trial # and Date]
ENVIRONMENT: [System ID]
| Object | Source Count | Loaded Count | Delta | Delta % | Status | Resolution |
|-----------------|-------------|-------------|-------|---------|-------------|------------------------|
| Vendor Master | 12,043 | 12,043 | 0 | 0.0% | PASS | — |
| Customer Master | 8,521 | 8,517 | 4 | 0.05% | INVESTIGATE | 4 records missing LAND1|
| Open Items (AP) | 45,230 | 45,230 | 0 | 0.0% | PASS | — |
OVERALL STATUS: [PASS / FAIL / CONDITIONAL PASS]
SIGN-OFF REQUIRED FROM: [Data owner names]This skill is complete ONLY when ALL of the following are true:
Evidence required: Data profiling report, cleansing sign-off, mapping document, trial migration execution log, reconciliation report, signed data migration sign-off.
If any item is unchecked, this skill is NOT complete. Do not authorize the production data load.
After completing this skill, invoke: cutover-planning Conditions for handoff: Data migration trial complete and signed off. Cutover planning must sequence the production data load as a critical path task within the cutover runbook.
testing-strategy — Data migration testing (trial run, reconciliation) is part of the overall test strategycutover-planning — Production data load is a key step in the cutover runbookgo-live-readiness — Data migration sign-off is a required input to the go/no-go matrixsap-data-analyst agent — Use for automated data profiling and anomaly detection~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.