Migrate from Fieldmagic to Salesforce Sales Cloud

Direct map. Fieldmagic Customers become Salesforce Accounts. Primary site address migrates as the Account billing/shipping address, and any secondary addresses are stored as custom address fields or linked Site__c records. Multi‑site customers require additional Site records linked via Account.Address_Linked_Sites__c or a custom junction object, preserving the original customer identifier in Source_System_ID__c for traceability.

Fieldmagic Sites carry location-specific addresses and site managers. Salesforce has no native multi-site-per-account object, so we create a custom Site__c object with an AccountId lookup to the parent Account, a Site_Manager__c field for the manager name, and a Site_Contact__c lookup for the on‑site contact. This structure keeps each physical location separate while remaining related to the Account for reporting.

Direct map. Fieldmagic Contacts become Salesforce Contacts with AccountId set to the parent Customer/Account. Mobile phone and email are preserved as standard fields, and any secondary phone numbers are stored in custom fields. Contacts without a parent Customer land against a default 'Unassigned Accounts' placeholder, ensuring no orphan records remain in the system.

Salesforce has no native Job object. We create a custom Job__c object in Salesforce to mirror Fieldmagic's job structure. Job__c links to Account (the customer), Contact (the site contact), a custom Asset__c record (if applicable), and OwnerId (the assigned technician). Job status maps to a custom pick-list.

Fieldmagic task checklists and checklist items migrate as Task records with ParentId pointing to the custom Job__c, plus a custom Job_Task__c object storing checklist metadata such as item order, required flag, and completed flag. This dual‑record approach maintains full fidelity of the original checklist structure, enabling accurate work‑order tracking in Salesforce.

Fieldmagic job line items (parts, labor, materials) map to Opportunity Products on a Salesforce Opportunity linked to the Job__c. If the job was quoted but not yet converted, the original quote migrates as an Opportunity with Products representing the quoted items.

Fieldmagic quotes carry header fields, line items, terms, and status. We map quote header fields to a custom Quote__c object linked to the Opportunity. Line items become Opportunity Products. Quote status (Draft, Sent, Accepted) maps to a custom pick-list on Quote__c.

Fieldmagic Asset records (serial number, maintenance schedule, install date) map to Salesforce's native Asset object in Service Cloud contexts. In Sales Cloud-only orgs we create a custom Asset__c object with AccountId, Location__c (Site__c lookup), and maintenance fields. Asset Type becomes a custom pick-list on the asset object.

Fieldmagic technicians and office users resolve by email match to Salesforce Users. Unmatched users are flagged before migration so the team can create Salesforce accounts or assign records to a fallback owner. Active/inactive status maps from Fieldmagic user records, and any missing email addresses trigger a review step to prevent data loss.

Fieldmagic files attached to jobs, sites, and assets are downloaded and re‑uploaded to Salesforce as ContentDocuments (Files) linked to the target record. Files that exceed Salesforce's 25 MB limit are split into smaller chunks, or archived with a reference link stored in a custom Notes field on the record, ensuring no attachments are lost during migration.

Every Fieldmagic custom property (fields added per account or job type) requires a corresponding custom field in Salesforce — either on the standard object (Account, Contact, Job__c) or on a custom object. FlitStack AI generates the field creation plan as part of the pre-migration schema setup deliverable.