paulh
/
adobe-to-docusign-migrator
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
7 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 9c0910f30f feat: end-to-end migration runner and test template utilities 
migrate_template.py — generic end-to-end CLI replacing the earlier
migrate_paul_template.py:
  --list                   list available Adobe Sign templates
  --template "Name"        download → convert → upload a named template
  --template "Name" --skip-upload  convert only, write JSON to migration-output/
  Picks most recently modified when multiple templates share a name.

create_adobe_template.py — utility for creating a test template in Adobe Sign
that exercises all 15+ field types. Uses the David Tag Demo Form PDF as the
base document and positions extra fields (Number, Email, Company, Title) in
the gaps of the original layout.

generate_pdfs.py — generates realistic sample PDFs with labelled form areas
matching the *-formfields.json fixtures in sample-templates/, for use in
offline testing without a live Adobe Sign account.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 		2026-04-15 19:45:31 -04:00
docs/agent-harness Initial project scaffold (Cleo) 2026-04-14 19:21:17 -04:00
src feat: end-to-end migration runner and test template utilities 2026-04-15 19:45:31 -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