Migrate from Agencyzoom to Salesforce Sales Cloud

AgencyZoom leads map directly to Salesforce Lead records. Email, phone, name, address, lead source, and any custom properties migrate as custom fields on the Salesforce Lead object. Owner assignment resolves by email match against Salesforce users — unmatched owners flag before the migration commits.

AgencyZoom contacts map to Salesforce Contacts with AccountId as the required lookup. Contacts lacking a primary company are linked to a designated fallback Account to satisfy foreign-key constraints. Each Contact also receives a Contact Source and custom fields; during load, FlitStack AI uses the Salesforce Bulk API to batch inserts and resolves owner assignments by email match against Salesforce users.

AgencyZoom companies migrate as Salesforce Accounts. Company name maps to Account.Name, domain to Website, industry to Industry (value-mapping applies for AgencyZoom's insurance-specific industry terms), employee count to NumberOfEmployees, and annual revenue to AnnualRevenue. Parent-child company hierarchies map via the ParentId field on Account.

Each AgencyZoom pipeline container becomes a Salesforce Sales Process named after the pipeline. A corresponding RecordType on the Opportunity object is created so stage pick-list values are scoped per pipeline. This is the most impactful schema decision — multiple pipelines require multiple Record Types and each Record Type needs its own page layout assignment in Salesforce before data lands.

Stage names map value-by-value from AgencyZoom to Salesforce Opportunity StageName per Record Type, ensuring each stage pick-list value is scoped to the correct RecordTypeId. Probability percentages and forecast categories are assigned per Salesforce's stage model, and the original stage-entered timestamps are stored in a custom datetime field (Stage_Entered_Date__c) for pipeline velocity reporting.

AgencyZoom service tickets map to Salesforce Case records. Ticket subject maps to Case.Subject, priority to Case.Priority, status to Case.Status, and the service category to a custom pick-list field (Service_Category__c). Carrier and policy references migrate as custom lookup fields on Case if a Policy__c custom object is created.

AgencyZoom carriers and service categories have no Salesforce standard equivalent. If the agency manages fewer than 20 carriers, these migrate as pick-list values on a Carrier__c custom field on Account and Opportunity. For agencies with complex carrier relationships, a Carrier__c custom object with a lookup from Account is the recommended approach.

Insurance policy details — policy number, line of business, effective date, expiration date, premium — do not exist as standard Salesforce fields. These migrate as custom fields (Policy_Number__c, Line_of_Business__c, Effective_Date__c, Expiration_Date__c, Premium__c) on the Account object, or as a Policy__c custom object with a lookup to Account when the agency tracks multiple policies per account.

AgencyZoom placeholder tasks and follow-up activities migrate as Salesforce Tasks. Original create dates preserve as Original_Create_Date__c since Salesforce's CreatedDate reflects the migration timestamp. Task status (open/completed) maps to Salesforce Task Status; task priority maps to Priority. Owner assignment resolves by email match.

AgencyZoom engagement logs (emails, texts, call recordings) migrate as Salesforce Tasks with Type='Email', Type='Call', or Type='SMS' set per engagement type. Call duration and outcome notes are stored in Task.Description. Original timestamps and owner links are preserved so the Salesforce Activity timeline reflects the full engagement history.

AgencyZoom notes migrate as Salesforce Notes (legacy) or ContentNotes (preferred, rich-text capable). The parent record link (Contact, Account, or Opportunity) is preserved during load so notes appear in the correct related-list on the Salesforce page layout. Inline images in rich-text notes are downloaded and re-hosted in Salesforce Files.

All AgencyZoom custom fields (configured under MyAgency > Manage Custom Fields) map to Salesforce custom fields with the __c suffix on the equivalent Salesforce object. Field data type is translated: AgencyZoom text fields become Text(255) or Text Area; pick-list fields become pick-lists with value-by-value mapping; date fields become Date fields. AgencyZoom's custom field metadata (required/optional, visibility) informs Salesforce field-level security settings.

AgencyZoom lifecycle automations combine email sequences, task creation, text messages, and stage-change triggers per pipeline. These do not migrate to Salesforce — the automation logic is not transferable between platforms. FlitStack AI exports the full automation definition (trigger conditions, actions, sequence order) as a Flow-design reference document your Salesforce admin uses to rebuild in Flow Builder.

AgencyZoom's Content Library stores email templates, text templates, documents, and media files used inside automations. These assets have no Salesforce equivalent that migrates automatically. We export the template content as a structured reference document (HTML for emails, plain text for SMS) so your team can recreate them in Salesforce's Content Builder or third-party tools.