Migrate from Agentbox to Salesforce Sales Cloud

Agentbox contacts map directly to Salesforce Contacts. The primary company reference in Agentbox becomes Contact.AccountId — the Account must exist in Salesforce first. Contacts with no company association land on a default 'Unassigned Account' record. If a contact has multiple company links, the primary company maps to AccountId, and other links are stored via AccountContactRelation. FlitStack checks for duplicate emails and merges records to prevent Contact rows for the same individual.

Agentbox contacts in early pipeline stages (prospect, enquiry) that have not yet transacted map to Salesforce Lead. Conversion to Contact + Account happens during Salesforce's standard Lead conversion workflow post-migration. During migration, FlitStack sets Lead.Status from the original Agentbox stage and applies Salesforce assignment rules to route leads to the correct owner. Duplicate emails are flagged for manual review.

Agentbox companies map to Salesforce Accounts. The company name becomes Account.Name. Domain, address, and industry fields map to Account Website, BillingAddress fields, and Account.Industry pick-list respectively. Parent-company hierarchies use Account.ParentId. If an Agentbox company has multiple locations, FlitStack creates separate Account records for each address and links them via Account.ParentId. Industry values are mapped using a value map, and unmapped industries are stored in a custom text field.

Agentbox sale-type deals map to Salesforce Opportunities with AccountId required. The deal name becomes Opportunity.Name, amount becomes Opportunity.Amount, close date becomes Opportunity.CloseDate, and stage maps to Opportunity.StageName via per-record-type value mapping. During migration, FlitStack resolves the OwnerId by email matching to Salesforce Users, and any unmapped owners are assigned to a fallback user. If the deal includes a property address, it is stored in a Opportunity field (Property_Address__c) for reference.

Agentbox rental deals route to a separate Salesforce record type keyed to the 'Rental' pipeline. Stage values are mapped separately from sale deals using Salesforce's Sales Process scoped to the rental record type. Rental-specific fields such as lease duration, monthly rent, and bond amount are stored in custom Opportunity fields (Lease_Duration__c, Monthly_Rent__c, Bond_Amount__c). This preserves the detail needed for rental deal tracking.

Agentbox stage names map one-to-one to Salesforce Opportunity StageName values per record type. Stage probability percentages and forecast category (Commit, Best Case, Omitted) re-applied from Salesforce-side stage configuration. Stage-entered timestamps stored as custom datetime fields. During migration, FlitStack maps stage sort order for correct Lightning Sales Path display. If a stage name lacks an exact match, it is placed under a generic 'Other' stage and flagged for later reclassification.

Agentbox's Listing object has no Salesforce standard equivalent. We create a Listing__c custom object with fields for listing price, property type, suburb, listing status, and a lookup to Account (vendor/landlord). The Listing__c object is linked to Opportunity via a junction object when the listing is attached to a deal.

Agentbox listing-to-agent assignments (the agent responsible for a listing) map to Salesforce OpportunityContactRole where Role = 'Listing Agent'. If multiple agents are assigned per listing, a custom junction object is required. FlitStack resolves the agent by email matching to Salesforce Users, creating a Contact record if no User exists. The OpportunityContactRole is created with Role = 'Listing Agent', and additional agents are linked via a custom Agent_Listing_Junction__c object.

Agentbox contact categories and tags (buyer type, investor classification, suburb preference) translate to a combination of standard Contact fields (Salutation, Title) and a custom multi-select pick-list Contact.Tags__c field. Categories requiring reporting visibility become individual custom fields. During migration, FlitStack splits pipe-separated tag strings into individual multi-select values for Contact.Tags__c. If a contact has more than five tags, the excess are stored in a Tags_2__c field to stay within Salesforce limits.

Agentbox buyer and tenant requirements (price range, feature list, preferred suburbs) have no Salesforce standard equivalent. These are stored as a custom Requirement__c object with a lookup to Contact and to Account for corporate buyers. FlitStack creates fields on Requirement__c such as Price_Min__c, Price_Max__c, Features__c, and Suburbs__c to capture requirement details. The Contact lookup ties each requirement to the specific buyer or tenant, and the Account lookup supports corporate clients.

Agentbox notes map to Salesforce Notes (modern Notes object, not legacy Note). Attachments are re-uploaded to Salesforce Files. File size limits of 25MB per file apply. Inline images in rich-text notes are downloaded and rehosted in Salesforce's file storage. During migration, FlitStack preserves titles and bodies, linking each Note to the parent Contact, Account, or Opportunity via ParentId. Attachments over 25MB are split, and files are stored with version control.

Agentbox agent profiles (staff records used for owner assignment) resolve to Salesforce Users by email match. Unmatched agents are flagged before migration. Your team either creates Salesforce User accounts for them or assigns their records to a fallback owner before data lands.