Migration plugins
Switch to Anvil without the rewrite
Anvil publishes open-source Claude plugins that migrate your existing e-signature integration to Anvil Etch E-Sign – mapping the APIs, moving your templates, and rewriting your code.
Add the marketplace
/plugin marketplace add anvilco/anvil-pluginsType this into Claude Code. It registers Anvil's plugin catalog so Claude knows where to find our plugins – it doesn't install one on its own. Pick a provider below for the install command.
Pick where you are coming from
Each plugin is purpose-built for one provider – it knows that provider's SDK, its template model, and exactly where it differs from Anvil.
Docusign
Converts Docusign templates directly into Anvil templates – field geometry, field types, and signer roles intact – then rewrites the integration.
docusign-esign
PandaDoc
Maps PandaDoc’s roles, fields, and tokens model to Anvil, collapses the create-poll-send flow into one call, and migrates block-based templates.
pandadoc-node-client
Dropbox Sign
Replaces the split SignatureRequest, Template, and Embedded API classes with one Anvil client, and moves your templates across as PDFs.
@dropbox/sign · hellosign-sdk
SignNow
Drops the two-step OAuth token exchange and collapses the copy, prefill, and invite calls into a single Anvil send.
@signnow/api-client
Xodo Sign
Handles the eversign API your Xodo Sign integration actually calls, and moves its flat-PDF templates across with Document AI.
eversign
How the migration runs
Whichever provider you are leaving, the plugin works through the same six steps, showing you what it found and what it plans to change before it edits anything.
Step 1 of 6
Discovery
Scans your codebase for every integration point – SDK imports, API calls, environment variables, webhook handlers, and database columns holding provider IDs.
Install a plugin
All nine Anvil plugins live in one GitHub marketplace. Add it once, then install whichever plugins you need.
Claude Code
Add the marketplace, then install the plugin for the provider you are leaving.
/plugin marketplace add anvilco/anvil-plugins
/plugin install <plugin-name>@anvil-pluginsClaude Cowork
Add the marketplace from the plugin browser.
Open Claude Cowork and go to Customize in the left sidebar
Click Browse plugins, then open the Personal tab
Click +, then Add marketplace from GitHub
Use anvilco/anvil-plugins as the source
Install the migration plugin for your provider
anvil-document-templates
Worth installing alongside a migration. Your provider's templates come across as part of the move; this one handles the rest of the library. Bulk-uploads a folder of PDFs with Document AI field detection, applies your own field names from a CSV, and opens each new template for review. Install it from the same marketplace with .View anvil-document-templates on GitHubUse Anvil's MCP
Anvil's MCP server connects your assistant directly to your Anvil account, so you can ask for what you need instead of writing a script for it.
Connect once
Run , pick the server, and sign in through your browser. It runs at and supports OAuth, so there is no API key or environment variable to set up. If you installed a migration plugin, this is the same connection it already uses.
Then ask for what you need
List the Casts in your account and inspect a template's fields
Check where an Etch packet is and who still has to sign
Fill a template with data and get a download URL back
Generate a one-off PDF from HTML or Markdown
Get a demo
(from a real person)
Schedule some time on our calendar to talk through your specific use case and see which Anvil products can help.
Want to try Anvil first?
Want to try Anvil first?