paulh
/
adobe-to-docusign-migrator
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
6 Commits 2 Branches 0 Tags 1.5 MiB
Python 62.3%
JavaScript 27.9%
CSS 7.7%
HTML 2.1%
Go to file
Paul Huliganga 93b6ad248a feat: DocuSign JWT auth and pure-Python template upload client 
docusign_auth.py — authentication helper supporting two flows:
- JWT Grant: service-to-service token generation using an RSA private key;
  caches token + expiry in .env to avoid redundant round-trips
- Auth Code Grant (--consent): one-time browser flow to grant the app the
  'impersonation' scope required for JWT; must be run once per user/app before
  JWT will work

upload_docusign_template.py — posts a docusign-template.json to the DocuSign
Templates REST API (v2.1). No Node.js dependency. Retries once on 401.

requirements.txt — adds PyJWT>=2.0 and cryptography for RSA key handling.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 		2026-04-15 19:45:23 -04:00
docs/agent-harness Initial project scaffold (Cleo) 2026-04-14 19:21:17 -04:00
src feat: DocuSign JWT auth and pure-Python template upload client 2026-04-15 19:45:23 -04:00
.gitignore chore: exclude generated outputs and binary assets from git 2026-04-15 19:44:26 -04:00
PRODUCT-SPEC.md Initial project scaffold (Cleo) 2026-04-14 19:21:17 -04:00
PROJECT-SETUP.md Initial project scaffold (Cleo) 2026-04-14 19:21:17 -04:00
README.md Initial project scaffold (Cleo) 2026-04-14 19:21:17 -04:00
api-samples.md Initial project scaffold (Cleo) 2026-04-14 19:21:17 -04:00
field-mapping.md feat: core migration — Adobe Sign to DocuSign field mapping and composition 2026-04-15 19:45:13 -04:00
requirements.txt feat: DocuSign JWT auth and pure-Python template upload client 2026-04-15 19:45:23 -04:00

README.md

adobe-to-docusign-migrator

Project Purpose

A migration toolkit/agent that automates extraction of Adobe Sign library templates (PDFs, fields, roles, workflow), transforms them to DocuSign template model, and creates/imports them into DocuSign.

Background

  • Adobe Sign and DocuSign both expose APIs to manage templates, fields, recipients, logic, and documents.
  • Adobe Sign (Acrobat Sign) uses "library documents" as templates, with data accessible via JSON API calls (but not exportable in a single file). You assemble the template info by calling:
    • /libraryDocuments/{libraryDocumentId} (metadata, PDFs, roles)
    • /libraryDocuments/{libraryDocumentId}/formFields (fields/tags)
    • /libraryDocuments/{libraryDocumentId}/recipients (recipients)
    • /libraryDocuments/{libraryDocumentId}/workflows (if applicable)
    • /libraryDocuments/{libraryDocumentId}/auditTrail (audit log, rarely needed for migration)
  • DocuSign templates are more easily exported as a single payload, but you can also build them incrementally over the API.
  • The most complex part of migration is mapping logic/fields/roles that are not 1:1 matches (conditional fields, complex routing).

API Output Samples

See api-samples.md for category-by-category JSON breakdowns.

Next Steps

  • Add full agent harness scaffold (docs/agent-harness/ structure, project README, spec templates)
  • Collect sample real-world Adobe Sign template JSONs
  • Define mapping/transforms for fields, roles, logic
  • Write initial extraction + mapping scripts
  • Draft Product Spec

Created: 2026-04-14 scaffolded by Cleo