← ClaudeAtlas

migrate-from-docusignlisted

Audit a DocuSign template or envelope export and report exactly what carries over, what changes shape, and what needs rebuilding — then import it. Use when someone has DocuSign template JSON, is evaluating a move off DocuSign, asks what their templates would look like elsewhere, or wants existing envelopes and tabs brought across.
mypropper/skills · ★ 1 · Data & Documents · score 72
Install: claude install-skill mypropper/skills
# Migrate from DocuSign > **PREREQUISITE:** Use the `propper` skill for authentication, tool routing, and the > agreement status model. The audit runs with no Propper account and no Propper tools. Produce the report first; import only once the user has an account and asks for it. ## Part 1 — Audit (no account needed) ### 1. Find the exports DocuSign templates export as JSON, one file per template. Envelope definitions have the same tab vocabulary. Accept a directory, a list of paths, or pasted JSON. Read each file. Do not call any Propper tool during the audit. ### 2. Inventory each template Report per template: | Reading | From | |---|---| | Name and description | `name`, `description` | | Documents | `documents[]`, with name and whether `documentBase64` is embedded | | Roles | `recipients.signers[].roleName`, plus `routingOrder` | | Field count by type | every `tabs` array across all recipients | | Anchors in use | `anchorString` values, with their offsets | | Merge fields | `textTabs` carrying `tabLabel` used as data placeholders | | Conditional logic | `conditionalParentLabel`, `conditionalParentValue` | | Routing | `routingOrder` distinct values — more than one means sequential | ### 3. Classify Sort every element into three buckets, and show the counts. **Carries over** — documents, roles, routing order, and the tab types with a direct Propper equivalent. Most templates are mostly this. **Changes shape** — elements that survive with a different representati