Migrate from MOGO to Salesforce Sales Cloud

MOGO contacts migrate directly to Salesforce Contacts. The critical difference is that MOGO stores company as a flat contact property, while Salesforce requires an AccountId lookup. FlitStack resolves this by creating the Account record first and linking the Contact to it via the AccountId field.

MOGO companies map to Salesforce Accounts with a direct name-to-name field mapping. MOGO supports parent-company hierarchies that map directly to Salesforce's ParentId field. FlitStack sequences Account creation to handle parent records before child records to prevent circular-reference failures. This sequencing ensures that when a child Account references a ParentId, the parent already exists in Salesforce and the foreign-key constraint is satisfied.

MOGO deals migrate to Salesforce Opportunities with a direct field mapping. The key translation is that MOGO stores pipeline and stage as pick-list properties on the deal, while Salesforce scopes StageName by RecordTypeId and Sales Process. Each MOGO pipeline maps to one Salesforce record type so stage values are scoped correctly.

MOGO's pipeline concept becomes two Salesforce constructs: a Record Type (controlling the available page layouts and pick-list values per business unit) and a Sales Process (controlling the Opportunity Stage values that appear for that record type). FlitStack generates the mapping plan before the migration runs.

Stage names do not copy directly because MOGO stage values rarely match Salesforce's built-in StageName pick-list. FlitStack maps each MOGO stage name to the corresponding Salesforce StageName value value-by-value, re-applies probability and forecast category, and preserves MOGO stage-entered timestamps as a custom datetime field for reporting continuity.

MOGO logged calls and emails map to Salesforce Tasks with Type='Call' or Type='Email'. MOGO meetings map to Salesforce Events with original start/end times, owners, and parent-record links (WhatId) preserved. All activity original timestamps and assigned owners are carried over for activity-history reporting.

MOGO notes migrate as Salesforce Notes on the related Contact or Opportunity record. File attachments are re-uploaded to Salesforce Files (ContentDocument model). MOGO inline images embedded in notes are downloaded and re-hosted in Salesforce's file storage. Each file is uploaded via the ContentVersion API and linked to the target record using ContentDocumentLink to maintain the original association.

MOGO custom fields map to Salesforce custom fields with the __c suffix. Each custom field must be pre-created in Salesforce Setup before data is inserted, as Salesforce enforces the field schema at the org level. FlitStack delivers a pre-migration checklist of required __c fields.

MOGO owner records are resolved by email address against Salesforce User records. Matched owners receive their records automatically. Unmatched owners are flagged before migration so the admin either invites them to Salesforce first or assigns their records to a fallback owner.

The delta-pickup window (24–48 hours) captures any MOGO records created or modified after the full migration snapshot is taken but before the source system is decommissioned. FlitStack applies these delta records to Salesforce in a second pass, ensuring the destination reflects MOGO's final state at go-live.