Home > DemandTools for AppExchange Modules > DemandTools Maintenance Modules > ZipFix - Reverse Engineer Existing Zip Codes
ZipFix - Reverse Engineer Existing Zip Codes
Capabilities & Features:
- Provides recommendations for City & State based on a valid 5 or 9 digit zip/postal code
- Provides recommendations to phone number area codes if they do not match the USPS (United States Postal Service) default area code for that 5 digit zip code
- Applicable to Leads, Accounts and Contacts
- Changes are recorded in a .csv file so that they may be reviewed before implementing into Salesforce data
- Use MassEffect to process the desired changes
Compatible Data Sources (output data):

Step 1. Select the object for ZipFix processing
- Choose the object for ZipFix-ing using the "Base Object Type" drop down on the right of the screen
- Choose either Accounts, Contacts or Leads
Step 2. Specify which records to verify
- Place the radio button on either "All Objects" -or- "Specify Conditions"
- "All objects" will look at all records for the selected base object
- "Specify Conditions" allows the user to create a "where" statement to specify which records to zipfix, ex: "billing state = oh,ny,pa,nj"
- **Tip: User with larger databases will want to utilize the specify condition option so that data is processed in manageable "chunks"


Step 3. Field Mapping
- Using the drop down next to the fields, choose the fields in Salesforce that correspond
- The zip code field mapping is required
- Up to 4 other fields can be chosen to help in the city and state recommendations
- Most of the time phone number fields should not be mapped due to multiple area code changes
- Case Insensitive match when checked, will ignore the case of the text when searching for recommendations
Reminder - the tool assumes that the zip code in your data is correct

Step 4. Select the Output file
- Click the "Pick" button
- Name the .csv file and click Save
- This is where the ZipFix info will be saved for review


Step 5. Review the Data
- Results will contain 3 to 9 fields depending on which fields were mapped in Step 3
- In the example below, only 2 fields were selected so 5 fields are displayed on the resulting CSV file (ID field, Original field values, recommended field values). The results show the ID of the account that had an invalid entry, the original City and State and the recommended City and State. If any of the original values are correct the recommended values are left blank (this will keep them from being processed in MassEffect).
Step 6. Process updates using MassEffect
- Once the results have been reviewed, the updates can be made in Salesforce via the MassEffect module
- Use Update mode in MassEffect and map the record ID field and the other fields from the spreadsheet for processing
See also
MassEffect - ETL for Salesforce
MassChange - Single Table Data Manipulation
Reassign Ownership - Mass Transfer of Objects/Sub Objects
MassImpact - Multi-table and Formula based data Manipulation
MassChange Batch
MassBackup - Backup to local .MDB database
Restore Files