"We assumed the hard part would be getting data out of Icertis. It wasn't. The hard part was figuring out what we were actually losing — and whether we needed it."
Hook
Icertis is an enterprise-grade CLM platform that's genuinely powerful — the AI extraction, obligation management, and SAP integration are best-in-class. But for our use case, we were paying for a platform built for 10,000+ contract portfolios and multi-business-unit governance, and we were a 400-person company with ~800 active contracts. The implementation had taken seven months, the admin overhead was constant, and our legal team kept telling us they just needed templates, approvals, and a place to find signed contracts. DocuSign CLM turned out to be the right weight.
What We Migrated
Here's the scope:
- ~850 signed contracts (2021–2026), mostly MSAs, SOWs, NDAs, and a handful of vendor agreements
- 24 active templates (we kept 19, retired 5)
- 4 integrations to re-wire: SAP Ariba, Salesforce, Coupa, and Slack
- ~300 tracked obligations (renewals, milestones, deliverables) — this was the big one
Step-by-Step Migration
1. Export & Audit Icertis Data
Icertis exposes 200+ APIs out of the box, which sounds great in theory. In practice, we needed to export:
- Contract documents (PDFs)
- Metadata (attributes, master data, contract types)
- Amendment/relationship hierarchies
- Obligation and milestone records
- Audit history
Gotcha: The export format is not a single "download everything" button. We had to make multiple API calls, pull documents separately from metadata, and reconstruct the parent-child amendment relationships ourselves. Icertis's support team was helpful, but budget 2–3 weeks just for the export and validation phase.
"Request an export demonstration before you commit to leaving. Ask specifically about amendment relationships, obligation records, and audit history. A data export that omits relationships preserves files but loses the operational meaning of the repository."
We also had to make a scoping decision early: what moves, what's archived, what's discarded. We decided to migrate all active contracts and the last 24 months of expired ones. Anything older went to a read-only SharePoint archive.
2. Field Mapping: Icertis → DocuSign CLM
This is where it got interesting — and not in a good way. Icertis's data model is significantly richer than DocuSign CLM's.
| Icertis Concept | DocuSign CLM Equivalent | Notes |
|---|---|---|
| Contract Type + Attributes | Template + Attributes | DocuSign CLM attributes are simpler; we consolidated 40+ Icertis attributes into ~15 |
| Clause Library | No direct equivalent | We lost structured clause tracking; clauses now live in the document |
| Playbooks (negotiation positions) | No direct equivalent | We documented fallback positions in a shared Confluence page |
| Obligations & Milestones | No native equivalent | We moved these to a separate tracking system (see Phase 5) |
| Contract Relationships (parent/child) | No native equivalent | We encoded relationships in a custom attribute field |
| Master Data (counterparties) | DocuSign CLM Contacts | Straightforward mapping |
| Workflow/Approval Chains | DocuSign CLM Workflow Builder | Rebuilt from scratch |
What we'd do differently: We should have done the field mapping before the export, not after. We exported everything, then spent two weeks deciding what actually mapped.
3. Import into DocuSign CLM
DocuSign CLM's Upload Center (available via the DocuSign AI Extension for CLM) is the primary bulk import path. It's available for new CLM customers and lets you upload documents in batches, with AI-assisted metadata extraction.
For the structured metadata, we used the API to create contract records and attach documents. We also used SFTP for the bulk document transfer (850 PDFs, ~40 GB total).
Gotcha: The Upload Center has file size limits (default 25 MB per file, extendable via support). Three of our vendor agreements with attached exhibits were over 50 MB. We had to split them and re-attach exhibits as separate documents.
Gotcha #2: Batch your uploads by contract type. We learned this after uploading a mixed batch of NDAs and MSAs and then manually re-classifying 120 documents.
4. Template Rebuild
We went through all 24 Icertis templates and made keep/kill decisions:
- Keep (19): Used more than 5×/quarter, had active integrations, or were required by compliance
- Kill (5): One-off templates, duplicates, or unused for 12+ months
The 19 survivors were rebuilt in DocuSign CLM's template builder. This was actually the fastest phase — DocuSign CLM's template editor is straightforward (merge fields, conditional text, approval routing).
What surprised us: We lost the clause library. In Icertis, we had pre-approved clauses that could be pulled into templates with one click. DocuSign CLM doesn't have a structured clause library. We worked around it by maintaining a shared "approved language" document that template authors reference manually. It's less elegant, but it works for our volume.
5. Workflow Redesign & Obligation Management
This was the most painful phase. Icertis's obligation management (tracking renewals, milestones, deliverables with automated alerts) has no direct equivalent in DocuSign CLM.
We had three options:
| Option | Pros | Cons |
|---|---|---|
| Keep obligations in Icertis (hybrid) | No rebuild, alerts keep working | Two systems, Icertis contract stays live |
| Move to a spreadsheet + calendar | Zero cost, simple | Manual, error-prone, no audit trail |
| Use a dedicated tool (e.g., Airtable, Jira) | Structured, automatable | Another system to maintain |
We went with option 3 — an Airtable base with automated Slack alerts for renewals 90/60/30 days out. It's not as integrated as Icertis's native obligation tracking, but it's transparent and our ops team can maintain it without IT.
For workflows, we rebuilt our intake → legal review → approval → signature → archive flow in DocuSign CLM's Workflow Builder. This was the one area where DocuSign CLM actually felt better — the no-code builder is simpler and our legal ops lead configured it herself in a few days.
6. eSignature Strategy
This one was easy: DocuSign CLM includes native eSignature. No integration needed, no separate signing platform. Contracts flow through the same system from template → approval → signature → repository.
If you're coming from Icertis (which integrates with DocuSign, Adobe Sign, or its own eSign), this is a genuine simplification. One fewer integration to maintain.
7. Integration Re-Wiring
| Integration | Icertis → | DocuSign CLM → | Effort |
|---|---|---|---|
| SAP Ariba | Native adapter (deep) | Native integration (lighter) | 1–2 weeks |
| Salesforce | API/connector | Native integration | 3–5 days |
| Coupa | API | Native integration | 3–5 days |
| Slack | Custom webhook | Custom webhook (rebuilt) | 2–3 days |
Gotcha: The SAP Ariba integration in DocuSign CLM is lighter than Icertis's. Icertis had bi-directional sync of contract status, line items, and amendments. DocuSign CLM's Ariba integration syncs contract metadata (start date, end date, supplier ID) but doesn't handle the full amendment lifecycle. If your procurement team relies on Icertis-level Ariba depth, this is a real gap.
Timeline & Cost
| Phase | Duration | Owner |
|---|---|---|
| Data export + validation (Icertis APIs) | 2–3 weeks | IT + Legal Ops |
| Field mapping + schema design | 1–2 weeks | Legal Ops |
| Bulk import (documents + metadata) | 1–2 weeks | IT |
| Template rebuild | 1–2 weeks | Legal Ops |
| Workflow redesign + obligation tracking | 2–3 weeks | Legal Ops + IT |
| Integration re-wiring | 2–3 weeks | IT |
| UAT + training | 1–2 weeks | Legal Ops |
| Total | 8–14 weeks |
Professional services from DocuSign or a partner runs $30K–$80K depending on scope. (Generally less than Icertis implementation, since you're going to a simpler platform.)
What Surprised Us
- The export was harder than the import. Icertis's 200+ APIs are powerful but not a single "give me everything" endpoint. We spent more time stitching together API responses than we did uploading to DocuSign.
- We lost more than we expected. The clause library, obligation tracking, and playbook system don't have equivalents. We compensated with simpler tools, but it's a real capability reduction.
- DocuSign CLM's template + workflow builder is genuinely good for our use case. Simpler than Icertis, and our team actually adopted it.
- The SAP Ariba gap is the one thing that still bugs us. For procurement-heavy teams, this is the biggest functional loss.
When NOT to Migrate
Be honest. If you're running a 5,000+ contract portfolio across multiple business units, with deep SAP integration, obligation tracking, and AI-driven risk scoring, DocuSign CLM is not the right weight. You'll be rebuilding capabilities in spreadsheets and side tools, and you'll end up paying for complexity you didn't save.
Also, if your Icertis implementation is less than 12 months old and still within your contract term, the migration cost likely won't justify the savings. Wait for renewal.
TL;DR / Checklist
- [ ] Request a full Icertis export demonstration before committing — specifically test amendment relationships, obligations, and audit history
- [ ] Scope what moves vs. what's archived — don't migrate everything
- [ ] Map Icertis attributes to DocuSign CLM fields before exporting — not after
- [ ] Batch Upload Center imports by contract type and watch file size limits
- [ ] Plan for the obligation tracking gap — decide your replacement tool before go-live
- [ ] Rebuild templates in DocuSign CLM — kill anything unused for 12+ months
- [ ] Test the SAP Ariba integration depth — confirm it covers your procurement workflows
- [ ] Budget 8–14 weeks and assign a single named owner for the whole migration
If you're mid-migration off Icertis, drop your war stories in the comments.
#icertis #docusign #clm #migration #devops #contractmanagement
Top comments (0)