Migrate from FRONTU to Salesforce Sales Cloud

Frontu work orders map directly to Salesforce Cases. The Case Status pick-list in Salesforce maps to Frontu's task status values — each status translation is validated value-by-value. Original creation timestamps and last-modified dates are preserved in Salesforce's native CreatedDate and LastModifiedDate fields. Multi-day job flag and duration are stored in custom fields since Salesforce Cases do not have a native multi-day span attribute.

Frontu customer records with a company name map to Salesforce Accounts. The Account Name, website, industry, phone, and billing address fields translate directly. Frontu customer records without a company name are flagged for review — these may map to individual Accounts or to Contacts without an Account association depending on your Salesforce configuration preference.

Named contacts on Frontu customers map to Salesforce Contacts under the corresponding Account. The Contact's name, email, phone, title, and mailing address translate field-for-field. If a Frontu customer has multiple contact persons, each maps to a separate Contact record linked to the same AccountId.

Frontu employees are translated to Salesforce Users so they appear as Case owners and service resources. Email-based matching is the primary resolution key — if a matching Salesforce User exists by email, the Frontu employee record links to it; if not, the record is flagged before migration and your admin either invites the person to Salesforce or reassigns their records to a fallback owner. Salesforce Field Service Lightning licensing is required for mobile technician scheduling beyond basic case ownership.

Frontu site and location records map to a custom Service_Site__c object in Salesforce, linked to the parent Account via a lookup relationship. Address fields, site name, and site-specific notes translate directly. If your Salesforce edition does not support custom objects, site records can be stored as a custom field on Account, though this limits multi-site-per-customer reporting flexibility.

Photos and documents attached to Frontu work orders and customers are downloaded from Frontu's storage, then re-uploaded to Salesforce as Salesforce Files attached to the corresponding Case or Account record. File size limit in Salesforce is 25MB per file — files exceeding this threshold are flagged for splitting or alternative handling before migration.

Frontu custom properties on work orders map to Salesforce custom fields on the Case object using the __c suffix naming convention. Each custom property's data type in Frontu (text, number, pick-list, date, currency) is mapped to the closest Salesforce field type. Pick-list custom properties require value-by-value mapping if the destination pick-list values differ from Frontu's values.

Frontu custom properties on customers translate to Salesforce custom fields on Account or Contact depending on whether the property applies at the company level or the person level. Custom fields are created in Salesforce before migration using the __c suffix, then populated during the load phase. Pick-list values require explicit value mapping against the Salesforce field.

Frontu time tracking records and activity logs map to Salesforce Tasks (for discrete time entries) or Events (for scheduled blocks). Original timestamps, duration, and technician assignment are preserved as custom fields on the Task or Event. If Frontu logs billable hours as a currency field, that maps to a custom Number field on the Task record.

Frontu service types and work order categories map to a custom pick-list field on Case (Service_Type__c). If Frontu's category values differ from your desired Salesforce pick-list values, a value-mapping table is applied during migration. Pick-list values are created in Salesforce before the migration run and validated against source data completeness.

Frontu technician skills and certifications translate to a custom pick-list on Case (Required_Skill__c) so work orders can indicate needed qualifications. If Salesforce Field Service Lightning is active, skills also map to ResourceSkill objects via the FSL data model. Without FSL, a custom pick-list on the User record (Technician_Skills__c) is the practical equivalent.

Frontu's native route-optimization data does not have a direct Salesforce equivalent. Route assignment order and optimization flags are stored as a custom text field (Route_Data__c) on the Case record for reference. Full route planning and optimization must be rebuilt using Salesforce Maps, MapAnything, or a similar geospatial add-on after migration — we flag this in the post-migration handoff plan.

Frontu parts-used records map to a custom text field on Case (Parts_Used__c) storing a comma-separated list for reference. If a structured product catalog exists in Frontu, those items can map to Salesforce Product2 records linked via Opportunity Products or Case Products — we assess this during the discovery phase and configure based on your Parts management needs.