Moving a Mogli instance to a new Salesforce organization requires a systematic approach to transferring both data and metadata while maintaining operational continuity. Because certain components, such as Gateways, are unique to their original environment, a successful transition depends on a mix of record migration, manual reconfiguration, and coordination with technical support. Prioritizing the migration of core application settings, user preferences, and historical SMS data ensures that the new environment retains the context and functionality of the original setup.
Migration Checklist
The following items need to be carefully considered and migrated to your new Salesforce org:
Gateway Records: Your configured SMS and WhatsApp gateways.
Gateway User Records: User assignments and settings related to the gateways.
Application Setting Records: Your Mogli application-wide configurations.
User Notification Records: Individual user notification preferences.
Forms and Form Template Records: Your created forms and their underlying templates.
SMS Records: Your historical SMS message data (consider the relevant timeframe for your needs).
Custom Metadata: Mogli-specific custom metadata configurations.
Mogli Integrated Object Records: Configurations for the Salesforce objects Mogli interacts with.
Latest SMS Info Objects: Records tracking the latest SMS interactions.
Fields Referenced as Merge Fields: Any Salesforce fields used as merge fields within Mogli templates or application settings.
Custom Fields Created for Mogli: Any custom fields you created on standard or custom Salesforce objects specifically for Mogli (e.g., on Person Accounts).
Recent User Notification Records: The last three months of User Notification records (SMS User Acknowledgements) for continuity.
Customizations: Any custom Mogli-related configurations you've implemented, such as Flows and Booster Packs.
Mogli Opt-Out Data: Records of users who have opted out of receiving SMS messages.
Before Migration
Keep the following important points in mind:
Gateways are Org-Specific: Mogli Gateways are tied to a single Salesforce organization and cannot be directly migrated. They will need to be re-configured in the new org.
Push Topics: Push Topics, which enable real-time notifications, may need to be manually created in the new org if they are not automatically created during the Mogli installation.
Data Volume: Be mindful of the volume of SMS records, as migrating a large history can take significant time and resources. Determine the necessary historical data for your new org.
Migration
Migrate Checklist Items: Systematically migrate all the data and metadata items listed in the Migration Checklist to your new Salesforce organization using appropriate Salesforce data migration tools (e.g., Data Loader, Change Sets for metadata).
Verify Mogli Configuration: Thoroughly check and confirm that the full Mogli configuration has been successfully migrated to the new org.
Contact Mogli Tech Support for Gateway/Webhook Updates: Once the data migration is complete, contact the Mogli Tech Support team at [insert Mogli Tech Support contact information] to coordinate the setup of your gateways and webhooks in the new environment.
Ensure Merge Fields Exist or are Removed: Verify that all Salesforce fields referenced as merge fields in your Mogli templates and application settings are present in the new org. If any referenced fields are not available, either create them or remove them as merge fields within Mogli.
After Migration
Once your initial data migration is in progress or completed, the Mogli Tech Support team will work closely with you to configure object settings and update your gateways and webhooks to ensure Mogli functions correctly in your new Salesforce org.
Mogli Migration Options
To ensure a smooth and efficient migration, we strongly recommend considering one of the following options:
Leverage Mogli Professional Services: Our experienced Solutions Engineers can handle the entire Mogli migration process for you, minimizing disruption and ensuring all aspects are correctly addressed.
Engage a Qualified Salesforce Solutions Implementation Team: You can also partner with a trusted Salesforce Solutions Implementation team that has experience with data migration projects and can work in coordination with Mogli best practices.
Given the potential complexities involved in data migration and the likelihood of specific questions arising based on your unique Mogli setup, direct involvement from our Mogli team can significantly streamline the process, reduce potential errors, and minimize back-and-forth communication.
Pricing and Time Allocation for Mogli Professional Services
If you choose to utilize Mogli professional services for your migration, please note the following:
No Fixed-Bid Pricing: Due to the unique nature and varying complexity of each data migration project, we do not offer fixed-bid pricing.
Time-Based Billing: Our services are billed based on the actual time spent by our Solutions Engineers on your migration project.
Transparent Communication: We maintain open and regular communication with you regarding the hours utilized throughout the project, providing updates on progress and any potential adjustments needed.
Recommended Initial Allocation: We typically recommend an initial allocation of 10 professional service hours, which can be adjusted based on the specific scope and complexity of your Mogli migration requirements.
Each Mogli data migration project is unique, and the Mogli team is committed to collaborating closely with you throughout the entire process to ensure a successful and efficient transition to your new Salesforce organization.
For further assistance, to discuss your specific migration needs, or to initiate a migration project with our Professional Services team, please contact your Account Manager directly or email us at help@mogli.com.