A migration plan is a list of gates. Each phase ends with things that must be true before the next one starts. Here is the checklist we run, phase by phase, from planning through cutover and the first checks after your team switches over.
900+ integrations completed · Salesforce partner · We sign BAAs
Salesforce data migration plan, phase by phase
Scope, sources, owners and the Salesforce target ready
Sandbox loads repeated until counts and samples pass
Source frozen, production loaded, checked, and the team moved
29 steps from plan to go-live. Tick them off as you go; your ticks stay in this browser.
A test load is not a dry run of the tool. It is a check of the decisions. It proves that every row finds its parent, that dates and owners survive, that picklist values land on the list, and that the records look right to the people who use them.
So the test load goes into a sandbox, and the people who know the data check it: a rep looks at their accounts, a manager runs the reports they live in. Anything wrong goes back into the mapping, and the load is repeated until it passes.
Created dates and past activities are the first things to check, because they are the first things an import loses. So are components that show activity on the record, like pinned or feed views.
What's included
Every source listed. What comes over, what is archived, and what is left behind, agreed in writing.
Owner rules, created date approach, duplicate rules and the External ID field per source, decided before mapping.
Fields, record types, picklist values and custom objects in Salesforce and deployed to production. Storage checked for records and files.
The mapping workbook complete, open questions closed, every tab approved.
A sample loaded into a sandbox. Failed rows explained. Lookups, owners, dates, activities and files checked.
Users review their own records and reports in the sandbox and sign off.
Record counts per object, sample records side by side, and the reports that must match the old system, written down before the production load.
Source frozen or a final delta taken. Flows, triggers, validation rules and connected apps that would fire on old records turned off.
Production loaded in order, counts and samples checked, reports compared.
Automations back on and tested, duplicate rules catching a test duplicate, field change history on key fields, and the old system kept read-only for lookups.
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 go through the checklist with your sources and your org and show you where your plan needs a decision. 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
Your sources, your org and where you are in the plan.
Priced by project, not by the hour. You approve before we start.
Each phase run against the checklist, with your sign-off at each gate.
Production loaded and validated, automations back on, 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.
Scope, sources, the decisions on owners, dates and duplicates, the mapping workbook, test loads, a written validation plan and cutover steps.
Load a sample into a sandbox, check failed rows, lookups, owners, dates, activities and files, then have the people who use the data check their own records and reports. Repeat until it passes.
It depends on the number of sources and objects, the volume, how clean the data is and how fast decisions get made. We scope it on the free call and put it in the project quote.
We recommend keeping it read-only so people can look things up, then archiving it.
The source is frozen, or a final delta of new and changed records is loaded after the main load, matched by External ID.
By project, not by the hour. The first call is free, and you get a project quote after it.
