An Ironclad instance holds more than contracts: records carrying Smart Import metadata, workflows built in Workflow Designer, often a Salesforce package, and the reminder rules that keep renewals in view. Leaving it means taking those apart in a sensible order, and the last part of this section says when not to start.
Ironclad lets you export records and their data through the repository, and through its REST endpoints if the API Access add-on is part of your contract. Take the executed PDFs and their metadata in the same run, because a renewal date without its document, or a document without its counterparty, has to be matched by hand later. Compare the count with the repository before anything is switched off. If some workflows signed through a connected DocuSign, Adobe Acrobat Sign or Dropbox Sign account instead of Ironclad Signature, check that provider’s account and export from there as well.
Rebuild the Workflow Designer paths that carry the volume.
Workflow Designer lets legal operations stack launch forms, conditional clauses, approver routing and global conditions, and over the years an instance can collect branches nobody remembers adding. Rebuild the three to five paths that produce most of your contracts first, as fynk templates with approval rules. For every remaining branch, ask its owner whether it still reflects a real rule before you recreate it, because a rebuilt branch that nobody needs is maintenance you carry into the new system.
Switch the Salesforce side over last.
Where sales launches contracts from Salesforce through Ironclad’s AppExchange-approved managed package, the sales team notices a broken integration before anyone else. fynk’s Salesforce connector is available from Essential, and its REST API and webhooks from Business, so test the connector on live opportunities while the Ironclad package still runs, and remove the package only once reps have closed deals through fynk. The same order applies to HubSpot, which needs fynk Business.
Keep renewal reminders running through the cutover.
Ironclad sends email reminders on date rules, such as 90 days before expiry, and those stop with the account. Import your live contracts into fynk first, check the extracted notice periods and renewal dates on a sample, and switch on fynk’s reminders before Ironclad goes dark. Plan the import against fynk’s AI credits: extraction on import draws on each user’s monthly allowance, so a large archive is best spread over several months or covered with a top-up.
Where leaving Ironclad does not pay off.
Stay on Ironclad if your security review requires a SOC 2 report, because fynk has ISO 27001 and no SOC 2 report. Stay as well if sales contracting is built deep into Salesforce through Ironclad’s managed package, or if legal operations maintain multi-department workflows in Workflow Designer that do their job. Moving those means a long rebuild for a gain the business will barely notice, and we would rather say so here than halfway through your migration.