Subscribe
Share
Share
Embed
Welcome to our podcast, where we dive into everything Go High Level—from mastering the basics to tackling the most complex tasks. I use GHL daily in my business and rely on Google NotebookLM to stay ahead of the curve, keeping up with all the latest GHL features, tools, and innovations. This podcast is powered by AI, fueled by the research and insights I personally curate to bring you the most valuable and up-to-date content.
Copy this link for a free trial of Go High Level - https://www.gohighlevel.com/highlevel-bootcamp?fp_ref=amplifi-technologies12
Imagine pressing import on your uh your brand new CRM system and instantly, silently, just wiping out like 10 years of client history. Detailed meeting notes, complex deal pipelines, just gone. For a digital marketing agency making the move from Salesforce to Go High Level, that scenario isn't just, you know, a hypothetical nightmare. Yeah. It's actually the most common reality when they don't understand the invisible mechanics of how data actually moves. It happens um far more often than anyone really wants to admit. Business owners try to swap enterprise software systems like they're, I don't know, upgrading a smartphone. Right. You just plug it in, sync it to the cloud and expect it to work. Exactly. Expect your apps to just populate. But a CRM migration is, well, it's a full-scale brain transplant on a living breathing organization. Welcome to today's deep dive. And I specifically want to welcome the digital marketing agency owners listening right now who are actively trying to upgrade uh and consolidate their tech stacks without totally losing their minds in the process. A very relevant demographic today. For sure. But before we get into, you know, performing that brain transplant, I'm actually really thrilled to announce a special listener perk we've got. We have a free 30-day Go High Level trial waiting for you. Which is huge. Yeah, that's double the standard trial length, which gives you really that crucial time you need to test out a system that is this robust. The link to claim that is sitting for you right down in the show notes below. And honestly, having that extended runway is absolutely essential for the kind of validation and uh testing we're going to explore today. I mean, rushing a data migration is just the fastest way to paralyze a sales team. So, let's set our mission for today. We are looking at a very specific high-stakes journey, moving an agency out of the sprawling, highly complex ecosystem of Salesforce and into the streamlined all-in-one environment of Go High Level, or, you know, GHL as everyone calls it. Right. And to understand the mechanics of the migration, we first kind of have to look at the motive. Why do it? Salesforce is an undeniably powerful tool, but uh that power brings enterprise grade complexity and a staggering price tag. Oh, absolutely staggering. Agencies today are just desperate for cost consolidation. In Salesforce, you pay for your base user licenses, but the second you want like advanced quoting, you have to add on CPQ. And for anyone who hasn't suffered through enterprise billing, CPQ stands for configure price quote. It's basically the calculation engine that handles complex pricing logic, discounts, bundles, and it is brutally expensive to maintain. Brutal. And then you add in the desire for marketing automation, and suddenly you're shelling out for Pardot or Salesforce Marketing Cloud just to send, you know, basic automated drip campaigns to your prospects. The tech stack just quickly becomes a financial black hole. Exactly. And Go High Level flips that script with an agency-first architecture. It consolidates those functions natively. Yeah. But really, its true superpower for an agency is SaaS mode. Oh, this is where it gets so fascinating. SaaS mode means an agency can white label the software. So, imagine logging in, and instead of seeing a massive corporate logo in the corner, your client sees, uh, Acme Marketing Hub. The agency rebrands the CRM as their own proprietary software and resells it to their clients under isolated sub-accounts. Which is brilliant, because attempting to build that kind of re-salable architecture natively in Salesforce would require, I mean, massive custom development and just a licensing nightmare. So, the financial and operational incentives to leave Salesforce are a massive draw for these agencies. But the question is, how do you move the brain without damaging the memories? You can't just pour water into a vase if you don't understand the shape of the glass. That structural mismatch is exactly where DIY migrations completely derail. Teams experience this profound architectural culture shock. Right. Because Salesforce uses a deeply relational schema, think of it as a very strict, rigid hierarchy. You have an account, which is the business entity. Okay. Inside that account, you have contacts, the actual humans working there. And those contacts link to opportunities, the deals. So they're distinct. Right. Distinct, heavily linked objects floating in relation to each other, governed by really complex rules. Whereas Go High Level on the other hand, operates on a contact-centric model. The contact is like the absolute center of the universe, and everything else orbits around it. Yeah, it's a fundamentally flatter architecture. Opportunities don't just float in a complex web, they live strictly inside distinct visual pipelines. And companies in Go High Level are treated more like, um, loosely coupled grouping tags rather than the absolute top of the hierarchy that governs everything below it. Which has to create immediate friction for the data. I mean, looking at our sources, Go High Level doesn't even have a separate led object. Nope. In Salesforce, a lead is basically a different species from a contact. To move them over, you literally have to merge your Salesforce leads into your Go High Level contacts. And then use tags or custom field, say, creating a new field called life cycle stage and setting it to lead just to segment them out. You're forcing a complex vertical hierarchy into a flat horizontal plane. And it goes even further than that. Salesforce formula fields. Yeah, those dynamically calculating fields that update when other numbers change. They do not exist in GHL. Okay. If you have a formula in Salesforce calculating, say, a dynamic partner discount, you have to extract the final computed number, not the formula itself, and store it as a static value when you move it over. It really feels like moving from a massive custom-built mansion with endless specialized rooms. Like a a room just for leads, a room just for formulas, a room just for quotes. Yeah, exactly. And you're just dumping everything into a massive modern open concept loft. The space is huge, but there are no walls. That is the perfect analogy. But wait, I have to play devil's advocate for the skeptical agency owners listening right now. Yeah. Those multi-tier permission sets and strict hierarchies in the mansion, they exist for a reason. If I have a massive sales floor with 50 reps, I don't want junior reps accidentally deleting overarching accounts because everything is flat. Isn't losing that hierarchy a genuine operational risk? Well, if you're running a 200-person enterprise sales floor, then yes, that rigid structure is incredibly protective. But for the vast majority of digital marketing agencies who usually operate with leaner teams, that multi-tier permission set is just administrative bloat. Oh, I see. Yeah. It becomes a bottleneck. They need speed, they need their marketing automation tied directly to their sales pipeline without needing, you know, an external consultant to write custom code. The simplification actually forces agility. Okay, the problem is, because of this massive architectural shift from the mansion to the open loft, the first thing everyone tries, the standard export and import method, becomes an absolute trap. Oh, a total trap. Let's talk about the danger of the CSV file. Because the CSV is fundamentally just a flat spreadsheet. Relying on it to move your deeply relational Salesforce data seems like a disaster waiting to happen. And native CSV export and import will silently destroy your relational data. And silently is the terrifying part. You might not even realize it's broken until you're a week into using the new system and notice deals are missing. Exactly, because the CSV only understands rows and columns. When you import via CSV, you snap that delicate account to contact opportunity chain. You are just importing isolated rows of text. Right. And even worse is how CSV files handle historical activity. If you export 10 years of meeting notes, phone logs, and emails from Salesforce, and attempt a CSV import into Go High Level, the system restricts you to one single note per contact. No, one single note with a strict 5,000 character limit. So a client you've been nurturing for five years with hundreds of crucial interaction touch points, contract negotiations, project details, that rich history is just truncated or completely wiped out in a second. The entire historical thread vanishes into thin air. You lose the entire context of the relationship. Okay, so a tech savvy agency owner is going to hear that and immediately think, fine, no spreadsheets, I'll just fire up Zapier or make.com and build a middleware bridge. Right. The API duct tape. Yeah. But our sources explicitly warned against this approach too. Zapier connects to GHL via an app that authenticates to specific sub-accounts. If you're an agency with 50 clients, you can't easily scale a massive historical migration across 50 different sub-accounts at once. You really can't. Zapier is designed to process tasks sequentially, one by one. It is built for live syncs, you know, triggering an action when a new web lead comes in today. It is not built to haul 50,000 historical records from five years ago in bulk. Using Zapier for this is like hiring a courier on a bicycle to move your entire four-bedroom house across town. Like one single fork or pillow at a time, every time the doorbell rings. Yes. It's meant to react to a single live event. If you dump your whole house on that bike, it's going to crash, cost a fortune in task fees, and take six months. That is a perfect visualization of the bandwidth issue. So if CSVs ruin the relationships and Zapier is a bicycle, the only viable vehicle for a mature agency to move this data safely is an API-based ETL approach. And ETL stands for extract, transform, and load, right? Exactly. You write a script, or you hire a specialized service to pull the data out via the Salesforce bulk API. Then you transform it in the middle, molding the data from the mansion's shape to fit the new open-concept loft schema, and finally, you load it into Go High Level's V2 API. And we really need to emphasize the load part of that, because it requires a very specific dependency order. The dependency order is absolutely non-negotiable. You extract and load your accounts, which become companies and GHL first. Okay. Then, you load the contacts and associate them with those newly created companies. Following that, you create the pipelines and their specific stages. Only after all of that architecture is standing, do you load the opportunities, linking them simultaneously to the contact and the pipeline stage. Right, because if you try to push the opportunity over first, the database throws its hands up and says, well, I can't attach this $50,000 deal to John Smith, because John Smith doesn't exist yet. Exactly. The entire script will just fail and return endless error codes. And the secret weapon to making sure that web of relationships survives the trip is a reconciliation key. Oh, this part is brilliant. It's mandatory. Before you move a single record, you must create hidden custom fields in Go High Level to store the original Salesforce IDs. So, I make a custom field called ScannedID. And I just hide it from the user interface, so my sales team doesn't get confused by random strings of letters and numbers. That's exactly the strategy. When your script loads an opportunity, it looks at the Salesforce contact ID attached to it, searches for the matching hidden custom field in Go High Level, and says, ah, tied this deal to this specific person. Wow. That is how you rebuild the mansion's relationships inside the open loft without creating thousands of duplicated contacts. Let me pause here. If you're listening to this and thinking, um, I am a marketer, I'm a visionary, I am not a database engineer writing API scripts, do not panic. Yeah, please don't panic. The takeaway here isn't that you need to go learn Python and start coding. The takeaway is that you cannot hand this project to a summer intern with a CSVG file. You have to bring in an integration specialist. And now you know exactly what to demand from them. Knowledge of the terrain is your absolute best defense against a botched migration. So, let's assume the API script finishes successfully. The data is sitting in Go High Level, the relationships are intact, the histories are preserved. The natural human instinct is to pop a bottle of champagne and immediately cancel the massive Salesforce bill. Naturally. Why is that the absolute worst thing an agency owner could do in that moment? Because the data is just the fuel. You haven't finished rebuilding the engine that runs on it. Right. The agency has to recreate its operational workflows, its landing pages, and its custom objects to fit the hard physical constraints of the new system. High Level imposes a strict ceiling of 10 custom objects per location across all plans. Wait, 10. Okay, if an agency currently relies on 15 or 20 custom objects in Salesforce tracking client ad campaigns, SEO audits, onboarding checklists, partner commissions. What do they do when they smash into that 10 object brick wall? They have to practice architectural compromise. You sit down and you audit your data structure, take your less critical custom objects and flatten them. Flatten them how? Well, if an object in Salesforce is just storing like five data points about a client's website platform and hosting provider, that doesn't need to be a whole distinct relational object in GHL. It can just be a set of simple custom fields on their main contact profile. So, GHL is basically forcing you to stay agile. They're putting a hard cap on your ability to recreate the exact system bloat you're trying to escape. That is the underlying philosophy of the platform. For the overflow data that truly requires relational depth and pushes past that limit, you archive it externally in a data warehouse or even a secure spreadsheet. Makes sense. You also have to navigate API rate limits during this rebuild phase. High Level allows 200,000 requests per day per location with a burst limit of 100 requests per 10 seconds. Which means if your script tries to blast 500 records a second to get the migration done faster, the API will just slam the door in your face and drop the data. The connection will sever entirely. You also face limitations on unique field types. In a Go High Level custom object, you cannot mark a lookup field or a date field as unique to prevent duplicates. Oh, interesting. Only text, number, and phone fields can be unique. You have to write your deduplication logic around those specific rules before you run your data load. And while the data migration is happening in the background, the marketing team is going to be incredibly busy manually rebuilding assets. Because you can't API your way into moving a beautifully designed Salesforce email template into Go High Level. No. The platforms render HTML and code entirely differently. Salesforce email templates, web to lead forms, and landing pages must be manually recreated using Go High Level's drag and drop builders. And the automations too. Salesforce relies on Process Builder and complex flows. You really have to map out the raw business logic of those flows on a whiteboard and rebuild them step by step in Go High Level's automation workflows. It takes time. It does. But here's a massive upside noted in our sources, native document e-signatures. Yes, a huge point of operational consolidation. In Salesforce, managing contracts and getting client signatures usually requires integrating a third-party tool like DocuSign. Which is another expensive subscription. And another fragile API connection that can break during an update. Right. But in GHL, agencies can consolidate their entire contract proposal and signature process directly inside the CRM natively. Which really brings us full circle to why agencies make this painful jump in the first place, stripping away the bloated add-ons and bringing everything under one roof. Absolutely. So, the engine is fully rebuilt. The data is migrating cleanly via the API. The emails, the forms, the automations are all set up. But we still can't just flip the switch at 5:00 p.m. on a Friday and walk away. Mhm. Doing that without a net risks the agency's entire operation on Monday morning. It would be incredibly reckless. You must enter a rigorous validation phase. You never trust that the migration worked simply because the script finished without throwing an error code. So, if I can't trust the script success message, I'm assuming I have to run some sort of side-by-side audit before I let my sales team touch the new system. Yes. You compare the raw record counts. You run a SOQL query, that is Salesforce object query language, to count your total Salesforce contacts. Then, you check the total returned by the Go High Level API. And they need to match exactly. Those numbers need to match perfectly. You also have to aggressively test Go High Level's duplicate handling during this phase. Because Go High Level automatically merges contacts based on phone number or email, depending on how your sub-account settings are configured. Which sounds wonderfully efficient until you apply it to B2B marketing. Oh, right. Agencies frequently have multiple distinct clients, vendors, or franchise owners who share a generic company email address, like info@company.com. Oh. Yeah. If you blindly push your Salesforce data into GHL, the system will see 10 different CEOs sharing that info email and forcefully merge them into a single Frankenstein contact record. Oh, that would be a complete nightmare. A sales rep logs in to call a specific client and sees the phone numbers, deal histories, and private notes of nine other people mashed into their profile. An absolute mess to untangle. The agency must pre-duplicate. You find those shared emails in your database before the API load, and either split them into primary and secondary fields or flag them so the new system knows not to improperly merge them. With all this validation and testing, what does the actual point of no return look like? How does an agency know it is genuinely safe to finally cut the cord and cancel Salesforce? Well, your decommissioning strategy relies on a transition period. You run the systems in parallel. Once the data safely lands in Go High Level, you keep Salesforce active, but you lock it down into a strict read-only mode. Okay, so they can see it, but they can't touch it. Right. Your team isn't updating pipelines or logging calls in Salesforce anymore, but they can search it if they feel, you know, a historical note is missing in Go High Level. It's like a 30-day safety blanket. At least 30 days. And during that initial week, you perform UAT, user acceptance testing. You don't rely on the IT guy to test the sales process. Right. You need the actual users. You have your actual sales reps log into Go High Level. You have them search for a known client, drag an opportunity from the discovery stage to the proposal stage, and verify that the automation fires, the native e-signature document generates, and the SMS alert triggers. You simulate the actual pulse of the business? Exactly. Once the sales reps, the marketing team, and operations managers all sign off that the daily workflows are functioning smoothly, then you do one final, complete backup of your read-only Salesforce data. Better safe than sorry. Store it securely on an encrypted hard drive or cloud vault, and only then do you hit the cancel button on that enterprise subscription. What an incredible journey. We started with an agency drowning in the complexity and add-on costs of Salesforce. We navigated the architectural culture shock of moving from a deeply relational custom-built mansion to a streamlined, contact-centric, open concept loft. Quite the move. We avoided the CSV trap, no bicycle couriers hauling our data. And used an API-based ETL process to preserve relationships using hidden Salesforce ID keys. We flattened our custom objects, rebuilt our automations, and ran a parallel read-only validation phase to ensure the agency didn't miss a single beat. It is a massive, highly technical undertaking, but when executed methodically, the operational agility and cost savings an agency gains on the other side are just transformative for their growth. It really is. And it leaves me with a final, slightly provocative thought for you to mull over. If marketing agencies are so eager to leave deeply customizable enterprise-grade systems like Salesforce for more rigid all-in-one platforms like Go High Level, does this mean the era of the hyper customized CRM is dead? Are we moving toward a future where speed, consolidation, and pre-built workflows always beat ultimate infinite configurability? That's a fascinating question. I think at some point, the friction of maintaining the machine outweighs the benefit of what the machine actually produces for the business. And that is exactly why this migration is happening everywhere. I want to thank you all so much for joining us on this deep dive into CRM architecture and migration strategy. It's been great. And I want to remind you one last time, if you are an agency owner ready to experience this powerful consolidation for yourself, you do not want to miss this. Click the link in the show notes right now to claim your free 30-day Go High Level trial. Double the standard length. Exactly. Take advantage of that double length trial period to get in there. Map out your pipelines and see the open concept loft for yourself. Until next time, keep diving deep.