Skip to main content

Migrating Data from Legacy Clickwrap to CLM Workflows

Difficulty: Intermediate

Time: ~60 Minutes (Varies based on number of records)

This Recipes program is currently in pilot, and we'd love to hear your feedback! Once you've finished this recipe, please consider taking a moment to complete this short survey to help us improve our current and future recipes.

Overview

Overview.png

This recipe walks you through migrating executed Ironclad Clickwrap (formerly known as PactSafe) records into Ironclad using Import to upload documents and Metadata Import to apply PactSafe metadata. You’ll end up with records that are full‑text searchable and enriched with the same key data you relied on in that iteration of Clickwrap workflows.

The goals of this recipe are to:

  • Consolidate Ironclad Clickwrap (fka PactSafe) clickwrap agreements in Ironclad

  • Preserve and enrich contract metadata from Clickwrap exports

  • Make migrated records searchable and reportable in the Repository View in Ironclad CLM

Use Case

Untitled (41).png

Your organization previously used Ironclad Clickwrap (formerly PactSafe) for clickwrap agreements, and Ironclad is now deprecating that product in favor of CLM‑based clickwrap workflows in Ironclad CLM. As part of the deprecation process, you can export historical clickwrap activity that includes:

  • A ZIP file of executed agreement PDFs

  • A CSV of associated activity/metadata

You want to:

  • Import the PDFs into Ironclad as Repository records using Standard Import

  • Use the PactSafe CSV to enrich those records with accurate metadata using Metadata Import

What You'll Need

Ingredients.png

Features

Repository, Dashboard, Imports tab, Metadata Import (via Imports page)

Permissions

Upload / Imports permissions to Import

Metadata Import tool permissions (group‑level admin setting), plus create/edit access to the relevant record types for the records you are updating

Additional tools

A spreadsheet editor (e.g., Excel, Google Sheets) to prepare your CSVs

Supporting Resources

SupportingResources.png

Disclaimer

Carefully review your imports and metadata mappings before running them in production—imports and metadata updates can affect large numbers of records at once and are difficult to undo at scale.

If possible, start in a demo or test environment and validate the full flow before repeating it in production.

Instructions

Instructions.png

To migrate Ironclad Clickwrap (fka PactSafe) clickwrap records into Ironclad, you’ll:

  1. Export records from Ironclad Clickwrap

  2. Download and unpack the export

  3. Prepare your CSV so file names match your PDFs

  4. Import the PDFs into Ironclad

  5. Enrich the imported records with Ironclad Clickwrap metadata using Metadata Import

Export records from PactSafe

  1. Export records from PactSafe

    export.png

    Export in batches of up to a range of 365 days of data per export. Ensure the export includes:

    1. A PDF for each executed record you plan to migrate

    2. A CSV that contains columns you’ll eventually want to store in Ironclad as metadata (e.g., record identifier, timestamps, status, etc.)

    You’ll use:

    • The PDFs as input to Import (document upload)

    • The CSV as input to Metadata Import (metadata enrichment)

Download and unpack your export

  1. When PactSafe finishes generating the export, download the zip file of record pdfs and csv file of activities from the export email:

    exportDownloadEmail.png
  2. Unzip the PDFs into a local folder on the machine you’ll use for Import.

  3. Store the CSV in a location you can easily open from your spreadsheet editor.

    At this point you should have:

    • A folder of PDFs (one per PactSafe record)

    • A CSV with at least one row per record you intend to migrate

files.png

Prepare your CSV so filenames match PDFs

To use Metadata Import effectively, you need a reliable way to match your CSV rows to specific Ironclad records. One of the most straightforward approaches is to ensure each row has a column whose value matches the PDF’s filename. Be sure to filter only Agreed events.

  1. Open the PactSafe CSV in your spreadsheet editor.

  2. Review the PDF filenames in your export folder and identify the naming convention.

  3. In your CSV:

    • Create a new column (for example, original_filename) that will match the PDF filenames exactly.

    • Use formulas or text functions as needed to construct the filenames (e.g., concatenating IDs, adding extensions).

      spreadsheet.png
  4. Once your formulas are correct, convert formula outputs to values so the import doesn’t depend on spreadsheet formulas:

    • Copy the formula column

    • Use Paste Special → Values (or equivalent) to paste over the same column, removing formulas and leaving only static text values

      pasteValues.png
  5. Save the updated CSV.

You now have a CSV where each row contains a filename that will later be used to match to Ironclad records created by Import. Later, you will map that column to Original Filename and set Match on = Original Filename in Metadata Import.

Import PactSafe files into Ironclad

In this step, you’ll use Import to upload your PactSafe PDFs to the Repository and let Ironclad create a record for each document.

Before you start

  • Confirm your files are in a supported format and size:

    • File types: .pdf, .docx, .doc

    • Max size: 100 MB per file, up to 100 pages per file

  • Group files by contract type (e.g., “Clickwrap – Terms of Use”, “Clickwrap – Privacy Policy”) so you can assign Record Types in bulk later, if desired.

Import Records from the Imports tab

  1. In Ironclad, go to the Imports tab.

  2. Click Upload records, then select Import.

  3. Click Next: Select files.

  4. Choose your file source - Drag‑and‑drop PDFs into the upload area or click to browse and select the folder of PactSafe PDFs

    import.png
  5. (Optional but recommended) In Set record type / Apply record type, choose the appropriate Record Type for this batch (e.g., Clickwrap – Terms of Use). Grouping uploads by contract type lets you assign this in bulk and avoid per‑record corrections later.

  6. Click Upload / Import to start the Import.

i

Note: What Import does:

  • Creates a new record for each uploaded document

  • Makes each document full‑text searchable in the Repository once processing completes

Verify & Organize Import Results

Once Import has finished processing your upload:

  1. Once Import has finished processing your upload:

  2. Go to the Imports tab and open the Import job you just created.

  3. Click into a few sample records and make any edits if necessary.

    • If your Record Type was not set during upload, assign it on each record as part of verification.

Import Metadata from PactSafe Contracts

Next, you’ll use Metadata Import to bring PactSafe metadata into Ironclad and attach it to the Import records you just created.

You’ll:

  1. Export record metadata from Ironclad for the newly imported records

  2. Merge that export with your PactSafe CSV

  3. Re‑import the merged spreadsheet using Metadata Import, matching on Original Filename (or Record ID)

Export Ironclad record metadata

  1. Open the Dashboard in Ironclad.

  2. Locate the Import records you just created:

    • Use search, filters, or a saved view to isolate the relevant records (for example, by Record Type or import date).

  3. Select the records you want to enrich by clicking the checkbox next to each record’s Name.

  4. In the More Options menu at the bottom bar, click Export.

  5. Under Export as, choose Spreadsheet (.xlsx) and confirm any additional data you want to export.

  6. Click Export to download the spreadsheet locally.

This spreadsheet will contain one row per record, plus columns for core metadata (e.g., Record ID, Name, Original Filename, etc.).

Merge PactSafe data into the Ironclad export

✔

Best Practice: We recommend creating a backup copy of the original spreadsheet files before you modify them in case you need to refer back to this data.

  1. Open the Ironclad export in your spreadsheet editor.

  2. Open your downloaded PactSafe CSV in another tab or window.

  3. Decide which PactSafe fields you want to carry over into Ironclad (for example: acceptance timestamp, clickwrap experience name, user identifier, or any other valuable attributes).

  4. In the Ironclad export:

    • Add new columns for each PactSafe metadata field you plan to import into Ironclad.

    • Use lookups, joins, or copy‑and‑paste to populate these new columns from your PactSafe CSV, using a consistent key (for example, the original_filename column you prepared in Step 3 or a shared ID).

  5. As you update the spreadsheet, follow the data quality best practices from the Use Metadata Import article:

    • Ensure consistent formatting for dates, numbers, and text values.

    • Remove duplicates and invalid entries before import.

  6. Once you’re done, save the merged spreadsheet. This is the file you’ll import back into Ironclad.

Import updated metadata via Dashboard

Use the Metadata Import tool to apply your updated spreadsheet to the existing Import records.

  1. In the Dashboard, click the More Options icon (three stacked dots) in the top‑right corner.

  2. Select Import metadata.

    Screenshot 2026-03-25 at 1.55.28 PM.png
  3. On the Record Metadata Import page, click New Import.

    Screenshot 2026-03-25 at 1.56.24 PM.png
  4. Drag‑and‑drop, paste, or browse to upload your merged spreadsheet (.csv, .xlsx, or .jsonl, under 25 MB).

  5. Click Upload.

You’ll now configure how Ironclad maps and applies the data.

Map columns and configure matching

On the Record Metadata Import configuration screen:

  1. Under Map to Property, use the dropdown in each row to map your spreadsheet columns to the correct Ironclad Record Properties:

    • Map the column containing PactSafe filenames (e.g., original_filename) to Original Filename.

    • Map new PactSafe fields to existing properties or create new properties where needed.

      maptoprop.png
  2. Under Match on, choose how Ironclad matches rows in your spreadsheet to existing records:

    • If you are matching based on filenames, set Match on = Original Filename.

    • Alternatively, if you are using Record ID, map that column to Record ID and set Match on = Record ID.

  3. Configure advanced options based on your use case:

    • For a migration that only updates existing Import records (recommended here), use Only update records (with or without ignoring unmatched rows, depending on whether you want the import to fail on missing matches).

  4. When you’re done mapping and configuring, click Next: Preview to generate a preview report.

  5. Review the preview for errors (such as missing Record Types, duplicate filenames, or formatting issues) and fix them if needed, following the Resolve Common Import Errors guidance.

  6. When everything looks correct, click Start Import.

Ironclad will process the import and apply the new metadata values to the matching records.

Validate migrated data

After the metadata import completes:

  1. Return to the Dashboard and open a sample set of records from this migration.

  2. Confirm that:

    • The PactSafe‑derived properties appear in the metadata panel.

    • Values match what you expect from the PactSafe CSV.

  3. Use filters and views to confirm the data behaves as expected (e.g., filtering on a new PactSafe property should return the expected subset of records).

  4. If necessary, iterate:

    • Adjust your spreadsheet.

    • Rerun a targeted metadata import to correct or augment data (for example, by using different advanced options or updating property mappings).

Result

Result.png

When you’ve completed this recipe:

  • All in‑scope Ironclad Clickwrap agreements have been uploaded into Ironclad CLM as Repository records via Import.

  • Each record is full‑text searchable in the Dashboard.

  • Metadata has been mapped and imported into Ironclad using Metadata Import, giving you a consistent, reportable data model across your migrated records.

Your team can now use Ironclad views, filters, and dashboards to search, segment, and report on migrated Ironclad Clickwrap (fka PactSafe) data alongside records created directly in Ironclad.

Tips & Variations

TipsVariations.png
  • For larger migration projects that combine document upload and data migration, review Migrating Your Repository to Ironclad, which outlines when to rely on Import versus Metadata Import and how to structure multi‑step imports.

  • Consider piloting this recipe with a small subset of Ironclad Clickwrap records first (for example, one month of data) to validate your mappings and data quality before scaling to the full dataset.

Did this answer your question?