Skip to main content
Group

Data Migration

ETL phone home!! Struggling with imports, exports or migrations? We're here for you. Come on in and post.

How to handle data migration and data transformation tasks when moving data into Salesforce CRM?

3 answers
  1. May 8, 2024, 12:38 AM

    I would recommend XL-Connector or XL-Connector 365 for the export/import operations.

     

    Being able to upload directly from VLOOKUP formulas and having a two-click way of switching between orgs will save you a ton of time. Additionally, you can write Ids from the bulk Insert operation into any column of the existing data having a super quick way of loading related records. The operation results are written right next to the data, so if something's wrong – it takes no time to spot the problem, correct it, and reupload.

     

    Disclaimer: I work for Xappex, the maker of these tools.

0/9000

Our other platforms only support a 1:1 relationship between a contact and an account.

 

Therefore, I need the ability to restrict the selection of a Primary Contact on an Account to be associated with Contacts with the same Account at the contact record level. 

 

I have disabled the multiple accounts to contact option in Account Settings and cleaned up all the indirect relationships. This feature resulted in inadvertently moving contacts around in our our other applications. 

 

However, the sales team can still designate a contact as a Primary Contact on an account the contact is not "setup" under. This causes the underlying GUID/Contact_recID to "move" to a different account ID within our tertiary databases. 

 

What I need to happen is to not allow contact1 to be associated with account1 and also be selected as the primary contact to account2. Instead, the sales rep will need to create a new contact2 and then associate that new contact as the primary contact for account2 (as well as account2 on the contact account field). 

3 answers
0/9000

Hi!  We acquired a company and I am responsible to bring in their CRM data.  The good news is they were a competitor so their model is very similar to ours.  We are going to commingle the data - we are going to be one combined sales team - so I'm not worried about security.  

 

The challenge is that I want a way to logically "partition" or segment the Co 1 vs Co 2 records across all objects to help with reporting, Flows, list views, etc in the near term.  For example a report to give me all Activities performed by Co 1 vs Co 2.   I don't want to use Record Types because we already have too many and I'd have to double them just for reporting (nah!).  

 

Would love some ideas!  I'm hoping I don't have to create a new "segment" field on every object but that's where I'm at now.

 

Thanks!  

7 answers
  1. Jan 17, 2023, 12:04 PM

    @Dan Stachura hope the intention of merger is to perform business together and not still be a competitor even after merger , Rather than rushing put some criteria to identify source of data. I thing you should go for De Dup at account level and merge the transactional data based on business use cases. we can create a custom field (Picklist- Helps you manage when you acquire one more competitor) tag this to User and pre populate it on all  transaction data based on user who  created it on all objects .Drive  sharing rules and reporting based on it

0/9000
2 answers
  1. Nov 8, 2022, 12:47 PM

    Migrate from one customized Salesforce org to another

    Note: Before migrating, prepare the target instance to receive or import your data. Here are some general points or considerations to keep in mind:

    1.     Importing data from one org to another requires matching metadata to be established in the new target org.

    ·       Experienced admins or developers may migrate metadata by Deploying and Retrieving Metadata using a client tool such as the Ant Migration Tool.

    2.     Other customizations for the target instance include record types, page layouts, etc.

    3.     Develop sharing models to accommodate new user groups if necessary: Profiles, Roles and Sharing Rules

    4.     Review ownership rules

    5.     Ensure all required data points and fields form the source org are captured in the target

    6.     Test migration prior to importing data. It's recommended to run through a migration in a sandbox first, see Sandboxes: Staging Environments for Customizing and Testing

    7.     Complete data validation once migration is complete

     

    Migrate or import your data from one org to another

    We recommend you watch the How to Import Data into Salesforce video to become familiar with what will be required to import all your data from a legacy to new org.    Several different tools are available depending on your edition and the number of records being imported. See the Choosing a Method for Importing Data documentation for more details.    To import records from one organization into another, you'll need to import the records in a particular order to establish their relationships to one another. Record relationships are stored in Salesforce or defined by their IDs so you'll need to populate your import files with any newly created record's Salesforce Ids from the target org. The easiest way to do this is using Excel's VLOOKUP function to add the new record Ids to your files for import.   

    If a vlookup isn't something you're comfortable with, consider creating a custom External Id field and map or insert your previous record Ids or other unique identifiers from your source organization into the field. This will allow you to Import related records using an External ID.   

    For example, after importing Accounts in your new org, you'll replace any occurrences of legacy Account Ids in your import files with NEW Account Ids from the target org. To populate your import files with the newly created Account Ids use vlookup as outlined in the Add Salesforce IDs of existing records to your import file article.    How Salesforce objects relate to one another can be graphically viewed in the Data Model | SOAP API Developer Guide documentation to assist in devising a strategy and planning your object's appropriate import order.    You need to define and include the ID of related records during import by replacing occurrences of old legacy record Ids with new related record Ids from the target org within your import file. This ensures that each new record is properly associated with one another.   

    Recommended sample order for importing core objects:

    1.     Accounts

    2.     Campaigns

    3.     Contacts

    4.     Opportunities

    5.     Cases

    6.     Price books

    7.     Products

    8.     Leads

    9.     Contracts

     

    Note: Migrate data from one organization to another (salesforce.com) 

0/9000

When importing data via the NPSP Date Import tool, I am uploading Contacts, Organizations, and Donations. When I have a Contact with an Organization (uploads as Affiliated Contact) how can I also map that contact to the Primary Contact field on the respective Opportunity?

2 answers
0/9000

Are there any issues with manually changing Data Import record status to Imported and back to Failed while troubleshooting?  

 

I have some records in a data import batch that are failing with the same error.  For troubleshooting, I'm trying to shorten the debug log.  I'd like to temporarily change most of the failed records to Imported so I can track just one import record in the log.  Once I've figured it out, I want to change the other records back to Failed so I can finally import them.

 

@Nonprofit Success Pack

1 answer
0/9000

I keep getting the following error when trying to upload a bunch of new donation records: "yc_OpportunityTriggers: execution of AfterInsert

caused by: System.DmlException: Update failed. First exception on row 50 with id 0061A000012ugV3QAI; first error: REQUIRED_FIELD_MISSING, Required fields are missing: [Annual_Report_Name__c]: [Annual_Report_Name__c]

()"

The most frustrating part is that the Data Import worked just fine for the last five rows of the original file, when I do a test of one row at a time, and doesn't flag any errors on the Dry Run.

7 answers
  1. Jun 2, 2021, 3:34 PM

    Correct @Tom Check​ ! I was able to get the data to import once I turned off the required status on the field (the data still imported into that Custom Field though), but ultimately would like to be able to turn that back on.

0/9000

Before importing data into Salesforce, it is sometimes necessary to combine data from different sources in a single spreadsheet. I was surprised that many experienced Salesforce professionals aren't aware that there are alternatives to VLOOKUP, so I wrote up an explainer: Still using VLOOKUP in your spreadsheets? Try INDEX and MATCH

www.linkedin.com

0/9000
Email service, fundraising tools, data duplications
3 answers
0/9000

Hi, I'm a non-profit staff starting to understand Salesforce, and I need to upload all donor information for this year and my goal is to send thank you emails to everyone before the end of the year. My questions are 1) There seems to be a separate object for "Recurring Donations" and what are the pros and cons of using that with Opportunities instead of just including all recurring donations in Opportunities? From what I've found, if the donation is open-ended, you can't use a standard Salesforce Opportunity with multiple payments, because the number of payments on an Opportunity in the NPSP is fixed. You must use the Recurring Donation process. But I wasn't sure how Opportunities and Recurring Donations work together if we'd like to see a list of all donations and one-time donations are all in "Opportunities" and Recurring are in "Recurring Donations". Also if there are donations that were given multiple times but not on a regular basis (for example on the same day of each month), do I have to insert them separately on my opportunities? 2) I wasn't sure how the Opportunities and Contacts work. So if I insert the "Primary Contact" in a new Opportunities entry, and import all information of all donors, will I be able to send mass emails through the Opportunities Object later on? Apologies for the long questions and thank you very much for your help in advance. I'm struggling with all these concepts. Thank you.

5 answers
  1. Jan 5, 2021, 5:41 PM

    Here are my thoughts:

    1) you'll have to see what you need, ask other people here (in its own post, focused on a single topic "For an organization that conducts campaigns with church congregations would you suggest any customizations?". i don't have experience in your space. Posts with multiple questions are hard to answer.

    2) There is only an advantage if you are using salesforce to track multiple payments per donation. I think it is simple to track each payment as a donation.

    3) Zapier is the automation tool to import the payments. You can import payment manually if you like, using the NPSP batch import tool. Free.

    4) Yes, I think the personal touch is better. You can save time by using an email template, and then personalizing it before you send it... Or just create the content from scratch for each email. It is up to you/your brand preference.

0/9000