Migration
Salesforce
migration services
Moving to Salesforce, or moving within it, is mostly a data, design and adoption project. These guides explain how each move works, what the source system lets you export, and what has to be rebuilt.
- Last reviewed
Choose a guide
Salesforce migration services we deliver
Moving to Salesforce
Data migration
What our Salesforce data migration services include
- Assessment: a data inventory with record counts per object, duplicates and stale data, and a decision on what is migrated, archived or left behind.
- Data mapping: a field-by-field mapping with transformation rules, signed off before any data moves.
- Cleansing and dedupe: standardized values, merged duplicates and resolved relationships, with the source record ID kept in an External ID field on every record.
- Tooling: the Data Import Wizard for small loads (up to 50,000 records at a time), and Data Loader or an integration tool for larger or repeatable loads.
- Test loads: trial loads in a sandbox, in dependency order (accounts before contacts, deals and activities), repeated until the results reconcile.
- Cutover: the final load in an agreed window, with a rollback plan on record.
- Validation: record counts and sample values reconciled with the source, and checked by the people who use the data.
- Post-go-live support: fixes and user questions after go-live, with the old system retired only after sign-off.
Our guide to Salesforce data migration covers the strategy, load order and tools in more detail.
For Locobuzz, a technology and software company, Techila moved lead management fully from HubSpot to Salesforce Sales Cloud, with lead deduplication, round-robin assignment and automated follow-ups. Read the Locobuzz case study.
Case studies
Migration and integration work we have delivered
- Financial servicesLeading BankSales Cloud and Service Cloud connected to Oracle Fusion Financials, core banking and third-party banking applications through MuleSoft Anypoint Platform.
- Wealth managementSt. James's PlaceA MuleSoft sync between Sales Cloud and Marketing Cloud for the UK's largest wealth manager and its 4,700+ Partner advisers.
Approach
Our migration process
Techila is a Salesforce Summit Partner. Every migration runs in the same seven phases: discover and audit, design the Salesforce model and mapping, prepare Salesforce, clean and transform the data, trial loads and reconciliation, cutover, and hypercare.
- Audit the source: objects, fields, automation, integrations and record counts.
- Design the Salesforce model and sign off the field-by-field mapping.
- Configure objects, fields, page layouts, validation and automation in a sandbox.
- Deduplicate and standardize values, and resolve relationships between records before loading.
- Run trial loads in a sandbox and reconcile counts and sample values.
- Cut over in an agreed window with a rollback plan.
- Support users after go-live and retire the old system only after sign-off.
FAQ
Frequently asked questions
Which guide should I read first?
The one for the system you are leaving. For moves between Salesforce orgs, start with the org consolidation page.
Do these guides replace an audit?
No. They explain the process and the documented limits. An audit of the actual setup produces the mapping and the plan.
Does Techila quote a duration or price from these guides?
No. Duration and cost depend on record volumes, automation and integrations, and are set after the audit.
How long does a Salesforce data migration take?
It depends on the volume of records, the number of objects and how they relate, the automation and integrations involved, and how clean the source data is. The timeline is set after the audit, once the mapping, the number of trial loads and the cutover window are agreed.
How do you keep data secure during a migration?
Trial loads run in a Salesforce sandbox before anything reaches production. Access is least-privilege: each person and integration user gets only the access their step needs, and it is removed when the migration ends. Techila is SOC 2 compliant.
What does a Salesforce data migration cost?
The cost is set after the audit. The main drivers are record volumes, the number of objects and fields to map, how much cleansing and deduplication the data needs, attachments and activity history, the automation to rebuild, the integrations to reconnect and the number of trial loads. Our Salesforce implementation cost guide shows how migration fits into a full project budget.
Related
Related
Plan your migration with a Salesforce architect
Tell us what you need. We reply within 1 business day.
Next step
Let's plan your next Salesforce program.
Tell us the systems involved, the number of users and the integrations in place, and we reply within 1 business day.