Moving data into Salesforce from an old CRM, spreadsheets or an EMR export? Or from one Salesforce org to another? We write the mapping sheet, clean and dedupe the data, test the load in a sandbox, then load production with the original created dates, owners, activities and files kept. Then we check it against the source before your team switches over.
900+ integrations completed · Salesforce partner · We sign BAAs
How a Salesforce data migration runs
Every source field and picklist value matched to Salesforce in a mapping sheet you sign off on
Duplicates merged, formats fixed, then a test load in a sandbox that you check
Automations paused, production loaded, counts and records checked, automations back on
Salesforce gives you two tools of its own for loading data. The Data Import Wizard runs inside Setup and handles up to 50,000 records at a time for accounts, contacts, leads, campaign members and custom objects. Data Loader is a separate app that inserts, updates, upserts, deletes and exports records on any object, up to 5 million records at a time. Which one fits depends on the objects, the volume and how the records link to each other, and we pick per project.
The tool is the easy part. The order matters more. Parent records load before child records: accounts before contacts, contacts and accounts before opportunities, and all of them before the activities and files that hang off them. Each record carries its old system ID in an External ID field, so child records find their parents by that ID instead of by name.
Salesforce can be changed in any way, with flows, custom objects, Lightning components and Apex. So data that does not fit a standard object gets its own custom object, built before the load, instead of being squeezed into the nearest field.
What's included
Old CRMs such as HubSpot, spreadsheets, EMR exports from Kipu or Sunwave, phone and texting history, and other Salesforce orgs. We sign BAAs for healthcare work.
One sheet per object: source field, Salesforce field, field type, picklist values and the rule for each. You sign it off before anything loads.
Phones, emails and dates put in one format, duplicates merged before the load, and duplicate rules set up so new ones are caught.
The old system ID kept on every record in an External ID field, so related records link up and a reload updates instead of duplicating.
Original created dates kept, through the Salesforce setting that allows it on insert or an "Original Created Date/Time" field. Records owned by people who have left stay with them as inactive users, or move to an active owner with the original name kept.
Notes, tasks, calls and texts loaded onto the right records with their dates. Long call notes go to a custom activity object. Files go into Salesforce Files, stored so they do not eat into data storage.
Products, price books and price book entries first, then quotes and quote lines tied to the right opportunity, with CPQ calculations checked after the load.
Fields and objects deployed to the new org first, then records moved over with their old Salesforce IDs kept as External IDs to rebuild every lookup.
A sample loaded into a sandbox first. You check dates, owners, related records and reports there before production is touched.
Record counts matched by object, sample records compared side by side with the source, and reports checked against the old system.
Every system we connect to Salesforce, in one list
CallRail and CallTrackingMetrics native integrations, with recordings and AI call summaries on the lead
Gravity Forms, Jotform and Typeform fills create leads with tracking attached
LiveChat, SnapEngage, Tawk.to and Avochato conversations saved to the lead
Kipu and Sunwave: admissions in Salesforce, clinical in the EMR, kept in step
CollaborateMD, AdvancedMD and HiLite, with insurance payments on the patient
Stripe, PayTrace and PayPal payments recorded on the opportunity
Google Ads, Microsoft Ads, Meta and TikTok leads in, offline conversions out
ActiveCampaign lists and automations that follow Salesforce
Open other systems from the Salesforce record with SSO
Salesforce data in Google Sheets, BigQuery and Looker Studio
No app for it? We build the connection with Apex and the APIs
Book a free call. We look at where your data lives today, what has to come over, and how it should land in Salesforce, and give you honest advice on the migration. No obligation.
The JTS team are extremely knowledgeable when it comes to advertising attribution and maximizing the potential of customer and leads. They know software extremely well, and how all the pieces fit together perfectly. I highly recommend his services to anyone looking to streamline their technology and maximize their sales potential.
I have been thoroughly impressed with the results. JTS team expertise in systems and software integration has given me clear and concise reports, they help me also with generating qualified leads, has been instrumental in driving my business forward. Thank you for everything you have done for my business.
For the past five years, Journeys Through Search has been an incredible marketing company to assist in our PPC, web development and support. Quick responses, vast knowledge and marketing creativity made them such a value add to our organization.
How it works
We look at your sources, the objects and volumes involved, and the Salesforce org they are going into.
Priced by project, not by the hour. You approve before we start.
The mapping sheet signed off, the data cleaned, then a test load in a sandbox that you check.
Automations paused, production loaded and checked against the source, automations turned back on, and your team moved over.
Working with us
US and overnight hours
Our teams cover all hours, so work keeps moving after your day ends.
AI agents in the workflow
We use AI agents in development and content creation, on a HIPAA-compliant Claude Enterprise license, so builds move faster.
900+ integrations completed
We have done this before, and it shows in how we plan and test.
Free call first
Honest advice before any work starts, even if you never hire us.
Salesforce's own Data Import Wizard and Data Loader cover a wide range of loads. Where data comes from another system's API, such as documents from a legacy system, we pull it in through that API. We pick the tool per project, based on the objects, the volume and how the records link up.
Yes. Fields, objects and automations go to the new org first. Then records move over in parent-to-child order, with the old Salesforce IDs kept in External ID fields so every lookup is rebuilt.
Change sets and deployments move metadata, like fields, objects and flows, not records. Once a test load passes in the sandbox, the same files and mapping are loaded into production with Data Loader.
An admin can let Salesforce keep records with inactive owners, so history stays with the person who did the work. If you would rather have an active owner, we assign one and keep the original owner's name in its own field.
Yes. Salesforce lets an admin set the created date and created by on insert. Where that is not an option, the original date goes into an "Original Created Date/Time" field your reports use.
No. We pause the flows, triggers, validation rules and connected apps that would fire, load and check the data, then switch them back on.
See the Salesforce implementation cost estimator for a ballpark, then get an exact quote after the free call.
By project, not by the hour. The first call is free, and you get a project quote after it.
