Switching CRMs is a major decision, and the biggest hurdle is often the data. Myra’s Migration Engine is designed to make the transition from platforms like GoHighLevel, Salesforce, HubSpot, or Pipedrive as painless as possible.
Supported Migration Paths
1. Direct API Migrations (Recommended)
We offer "one-click" imports for major CRM platforms.
- GoHighLevel: We can import your entire "Location," including custom fields, pipelines, snapshots, and even your existing automation logic.
- HubSpot/Salesforce: Direct API connection to pull in Contacts, Companies, and Deals while maintaining their relationships.
- How it works: You provide an API Key or log in via OAuth. Myra scans the source and provides a "Mapping Table" where you match old fields to new ones.
2. CSV / Spreadsheet Import
If you are moving from a legacy system or a custom spreadsheet:
- Flexible Mapping: Our importer allows you to map any CSV column to a Myra field.
- Tagging: Automatically add a tag (e.g., "Import_July_2024") to every record in a specific file.
- Conflict Resolution: Choose what happens if a contact already exists: "Skip," "Overwrite," or "Merge."
What Can Be Migrated?
We don't just move names and emails; we move your entire business context:
- Core Entities: Contacts, Companies, and Leads.
- Sales Data: Pipelines, Stages, and individual Deal history.
- Communication History: Historical notes and, in some cases, previous email/SMS logs.
- Operational Assets: Email templates, SMS templates, and Form structures.
- Automation: While complex logic might need a manual "tweak," we can often recreate the triggers and actions from your previous tool.
The Migration Workflow
- Preparation: Clean your data in your old CRM. Delete "Dead" leads and fix formatting errors (like missing country codes on phone numbers).
- Connection: Navigate to Settings → Migrations and select your source.
- Mapping: Match your old "Stages" to your new Myra "Pipeline Stages."
- The "Dry Run": The system will process the first 10 records and show you the result. This allows you to catch mapping errors before importing 10,000 records.
- Full Execution: The migration runs in the background. You can close your browser; we will email you once it’s complete.
- Verification: Review the "Migration Report," which lists any records that failed (usually due to invalid email formats) so you can fix them manually.
Handling Common Issues
- Duplicates: The system uses Email Address and Phone Number as unique identifiers. If the same person exists twice in your CSV, we will merge them into one record.
- Custom Fields: If you have a field in your old CRM that doesn't exist in Myra, the migration wizard will offer to "Create New Field" for you on the fly.
- Timezone Shifts: Ensure your source data is in UTC or that you specify the source timezone during import to avoid "Meeting Time" errors.
Post-Migration Checklist
- Reconnect Integrations: You will need to re-link your Google/Outlook calendars and your Stripe account.
- Verify Automations: Open your imported workflows and ensure the "Sender" identity is set correctly.
- Team Training: Invite your team and show them where their "Old" data now lives in the Myra interface.
Best Practices
- Batch Imports: If you have 100,000+ records, try importing them in batches of 20,000 to make verification easier.
- Back Up First: Always export a full CSV backup from your old system before starting a migration.
- Quiet Period: Try to run your migration during a "low activity" period (like a weekend) so your team isn't trying to use two systems at once.
FAQs
How much does a migration cost? Standard migrations (CSV and direct API) are included for free in all plans. For massive, complex enterprise migrations, our professional services team can provide a bespoke quote.
How long does it take? An API migration for 5,000 contacts usually takes less than 15 minutes. Large CSV files may take up to an hour to process.
Can I undo a migration? Yes. Within 48 hours of an import, you can use the "Rollback" button in the Migration Report to remove all records created by that specific session.