Migrate from GAIA.law to Salesforce Sales Cloud

Workflow and approval rules do not migrate — must be rebuilt in Salesforce Flow

GAIA.law automates contract review routing, approval chains, escalation thresholds, and renewal reminders as platform-native rules. Salesforce has no equivalent workflow import path — Flow operates on entirely different trigger logic, object models, and action types. FlitStack exports your GAIA.law workflow definitions as a structured rebuild reference (trigger events, conditions, approver assignments, and time delays) so your Salesforce admin can reconstruct them in Flow or Process Builder. Approvals configured in GAIA.law are recorded as audit entries on each agreement record; those audit entries migrate as a custom Agreement_Approval__c object, but the active approval routing must be rebuilt as a Salesforce Approval Process or Flow-triggered sequence.

E-sign integration status does not transfer as a live DocuSign or Adobe Sign envelope

GAIA.law integrates with DocuSign and Adobe Sign to send, track, and record e-signatures on agreements directly within the platform. The e-sign status field (sent, viewed, signed, declined) migrates as a read-only custom field on the Salesforce Opportunity, giving your team visibility into the last known state. However, the active DocuSign or Adobe Sign envelope associated with each GAIA.law agreement does not transfer — that envelope lives in the e-sign platform's own database. For agreements still in-flight at migration cutover, signers will need to receive a new envelope from Salesforce's Adobe Sign or DocuSign for Salesforce integration. FlitStack flags all agreements with e-sign_status not equal to 'signed' before migration so your team can plan the re-send.

Files attached to GAIA.law agreements must be re-uploaded to Salesforce Files

GAIA.law stores contract document attachments (PDFs, Word files, executed versions) associated with each agreement record. Salesforce does not have a native attachment import endpoint for external file references — each file must be downloaded from GAIA.law and uploaded as a Salesforce File (ContentVersion/ContentDocument) linked to the parent Opportunity via ContentDocumentLink. Salesforce enforces a 25MB per-file size limit by default; agreements with attachments exceeding this limit are flagged before migration so your team can split the file or store it externally with a link custom field. Original file names and GAIA.law file IDs are preserved as Salesforce File metadata for traceability.

GAIA.law extracted data fields become Salesforce custom fields — not native Opportunity fields

GAIA.law's AI extraction engine parses contract PDFs and structured forms to populate custom fields on each agreement — governing_law, liability_cap, renewal_term_months, auto_renew_clause, and similar legal-specific data points. Salesforce Opportunity has no native fields for these legal metadata attributes. FlitStack creates a custom field on the Opportunity object for each unique extracted field found across your GAIA.law agreements, applying the __c naming convention. Field types are inferred from GAIA.law data (date fields become Date, numeric fields become Number, text fields become Text). If your Salesforce org already has custom fields with overlapping names, a naming conflict resolution step is required before migration runs.

GAIA.law party-to-agreement links require Salesforce Account pre-creation before Contact insertion

GAIA.law allows parties to be associated with agreements without requiring the party to be linked to a company record first. Salesforce enforces referential integrity — Contact.AccountId is a required lookup for most Contact-to-Account relationships, and OpportunityContactRole requires a valid ContactId. FlitStack sequences the migration so organization-type parties are migrated to Accounts first, then individual parties are migrated as Contacts with AccountId populated from the matched Account record. Agreements are migrated last so their OpportunityContactRole links resolve correctly. Circular or missing organization references in GAIA.law (a party with a company name that has no standalone Account record) are flagged in the pre-migration audit.