Migrate from mQuest to Salesforce Sales Cloud

mQuest users map directly to Salesforce Contacts. Email is the match key for owner resolution — FlitStack AI matches mQuest user email against Salesforce usernames. Unmatched users are flagged before migration so your team can either invite them or assign to a fallback Contact.

mQuest stores role and department information on each user record. These two attributes merge into the Contact object: job role maps to the native Contact.Title field, while department maps to Contact.Department. Since Salesforce Contacts lack a native role field, FlitStack surfaces role data as a custom text field called User_Role__c for segmentation and reporting purposes.

mQuest quest definitions — quest name, description, category, and quest type — map to a Salesforce custom object (Quest__c). The standard Salesforce Name field holds the quest name. Category and type migrate as custom pick-list fields (Quest_Category__c, Quest_Type__c) on the custom object.

Quest assignments track which user is assigned to which quest. In Salesforce, these become a custom object named Quest_Assignment__c that serves as a junction between users and quests. It includes a lookup field to Contact (named User__c) and a lookup field to Quest__c (named Quest__c), preserving the N:1 assignment relationship that mQuest supports natively.

mQuest assignment statuses such as Not Started, In Progress, Completed, and Overdue map directly to a custom pick-list field (Status__c) on Quest_Assignment__c. Each status value from mQuest becomes an exact pick-list option in Salesforce, preserving all reporting continuity without any value transformation or renaming.

Individual quest responses or submissions map to a custom object (Quest_Response__c) linked to Quest_Assignment__c. Response text, scores, and file attachments migrate as fields on this object. If mQuest stores response history, FlitStack preserves it as multiple Quest_Response__c records per assignment.

mQuest progress percentage or score maps to a custom number field (Progress_Pct__c) on Quest_Assignment__c. For mQuest systems that track a numeric score rather than a percentage, FlitStack stores the raw value and applies any required normalization based on the source scale.

Email activities tracked in mQuest—those linked to quest assignments or user records—migrate as Salesforce Tasks with Type=Email. Subject, body, timestamp, and owner are all preserved from the source record. Each Task links to the corresponding Contact record so email history surfaces in the Salesforce activity timeline and contact reports.

Call records from mQuest map to Salesforce Tasks using Type=Call, preserving subject and duration. Meeting records migrate as Salesforce Events with original start and end times intact. Both task and event records link to the Contact associated with the original mQuest user.

mQuest notes on quest assignments or responses migrate as Salesforce Notes (not the legacy Note object). File attachments re-upload to Salesforce Files, with the original file name and content type preserved. Inline images in notes are downloaded and re-hosted in Salesforce.

Salesforce automatically sets CreatedDate and LastModifiedDate at migration time, overwriting original timestamps. To preserve audit continuity and historical reporting accuracy, FlitStack AI extracts mQuest's original create and modification timestamps and stores them as custom datetime fields named Original_Create_Date__c and Original_Modified_Date__c on each record.

mQuest workflows, quest routing rules, conditional logic, and automation sequences have no direct Salesforce equivalent. FlitStack AI exports mQuest workflow definitions as a structured document that your Salesforce admin can use to rebuild equivalent logic in Flow and Process Builder.

Any mQuest custom fields added beyond the standard schema become Salesforce custom fields with the __c suffix on the appropriate object. FlitStack AI inventories all custom fields during discovery and preps a Salesforce field creation plan so the custom schema is ready before the migration run.

mQuest third-party integrations (webhooks, API connections, linked tools) do not migrate to Salesforce. Each integration must be reconfigured as a Salesforce Connected App, Outbound Message, Flow integration, or AppExchange app. FlitStack provides an integration audit document listing every active connection for your team to rebuild.

mQuest user roles and permission levels do not have a direct Salesforce equivalent. User access and permissions in Salesforce are managed via Profiles and Permission Sets. FlitStack exports the mQuest role structure as a reference document so your Salesforce admin can assign appropriate Profiles and Permission Sets post-migration.