Merging two orgs, splitting one, or starting over in a clean org? Record IDs do not travel: the new org gives every record a new ID. So the work is in rebuilding the links between records. Here is how we migrate data from one Salesforce org to another, in full or in part.
900+ integrations completed · Salesforce partner · We sign BAAs
How an org-to-org move runs
Fields, objects and picklists deployed to the new org first
Exported from the old org with their IDs, loaded in parent-to-child order
Activities and files last, then both orgs compared
Two things move, and they move separately. Metadata, meaning fields, objects, flows and layouts, goes by deployment. Records go by export and load. A deployment does not carry records, and a data load does not create fields.
Every record the new org receives gets a new 18-character ID. To keep a contact on its account, the old account ID is stored in an External ID field in the new org, and each child row points to its parent by that value. The same goes for every custom lookup.
Users are mapped by person, not by ID. People who left can be created as inactive users so their records stay with them. Files are exported with their content and relinked to the new records, and activities load last, once everything they point to exists.
What's included
Every object and record moved to a new org, in load order, with counts compared object by object.
Only one business unit, one region, open records or a date range. The export is filtered, and every related record the subset needs comes with it.
Old Salesforce IDs kept in External ID fields, used to rebuild lookups, master-detail links and record ownership.
Users matched across orgs, inactive owners kept where history needs them, and owner rules written down.
Original created dates and created by set on insert where the new org allows it, or held in their own field.
Files exported with their content and linked to the right new records, counted against file storage.
Tasks, events and custom activity records loaded last, linked to the new parent records with their original dates.
Deployments move the build from sandbox to production; records go by Data Loader, with the same files and mapping proven in the sandbox first.
Partial copy sandboxes take a sample of production through a sandbox template; where a developer sandbox needs data, we load a filtered set.
Flows, triggers and connected apps in the new org held off during the load, so old records do not send emails or create tasks.
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 both orgs, what has to move and what can stay, and tell you how the links will be rebuilt. 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
Both orgs, the objects involved, and whether you need everything or a subset.
Priced by project, not by the hour. You approve before we start.
Structure deployed to the new org, then a test load in a sandbox that you check.
Records, files and activities moved, then counts and sample records compared across both orgs.
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.
No. Salesforce assigns new IDs on insert. We keep the old IDs in External ID fields and use them to rebuild every relationship.
Yes. Exports can be filtered by any field, like region, record type, status or date. We make sure every record the subset depends on comes too.
Files are exported separately, with their content, and linked to the new records after those records exist.
Records do not move with deployments. Once the sandbox load is right, the same files and mapping are loaded into production with Data Loader.
They can be created as inactive users so their records and history stay with them, or their records can move to a current owner with the original name kept.
By project, not by the hour. The first call is free, and you get a project quote after it.
