paulh
/
adobe-to-docusign-migrator
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
5 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 76568672d7 feat: core migration — Adobe Sign to DocuSign field mapping and composition 
compose_docusign_template.py — converts a downloaded template folder into a
DocuSign envelopeTemplate JSON ready for the Templates API. Key behaviours:

- Full field type mapping: TEXT_FIELD, SIGNATURE, CHECKBOX, RADIO, DROP_DOWN,
  BLOCK, FILE_CHOOSER (with warning), INLINE_IMAGE (skipped with warning)
- contentType dispatch: SIGNER_NAME → fullNameTabs, SIGNER_EMAIL →
  emailAddressTabs, SIGNATURE_DATE → dateSignedTabs, COMPANY/SIGNER_COMPANY →
  companyTabs, TITLE/SIGNER_TITLE → titleTabs, DATA+NUMBER → numberTabs,
  DATA+DATE → dateTabs, SIGNER_INITIALS → initialHereTabs
- Multi-location (cloned) fields: emits one tab per location with the same
  tabLabel so DocuSign tab merging replicates Adobe Sign's sync behaviour
- Width/height passed through from Adobe Sign locations; MIN_TEXT_WIDTH=120pt
  ensures text fields render as visible boxes rather than vertical lines
- Coordinate system: both platforms use top-left origin — no inversion needed

test_mapping.py — unit test harness validating tab grouping and field mapping.

field-mapping.md — full Adobe Sign → DocuSign tab type reference table with
edge cases, known gaps, and decision log.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 		2026-04-15 19:45:13 -04:00
docs/agent-harness Initial project scaffold (Cleo) 2026-04-14 19:21:17 -04:00
src feat: core migration — Adobe Sign to DocuSign field mapping and composition 2026-04-15 19:45:13 -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 Initial project scaffold (Cleo) 2026-04-14 19:21:17 -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